Re: [Flightgear-devel] Default 3d clouds in Local Weather
On Sat, 2011-08-06 at 14:43 +0300, thorsten.i.r...@jyu.fi wrote: Some visual impressions from the 3 cloud types I've converted to the new system so far here: http://www.flightgear.org/forums/viewtopic.php?f=5t=7358start=390#p132335 Stuart - please help: I get anti-shadowing for Stratus clouds, and I don't really understand why... Could this be a normal map problem (I believe it's possible to store the normal map in dds textures) Do we use normal maps for clouds ? Regards, -Fred -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Default 3d clouds in Local Weather
On Sat, Aug 6, 2011 at 3:50 PM, Frederic Bouvier wrote: On Sat, 2011-08-06 at 14:43 +0300, thorsten.i.r...@jyu.fi wrote: Some visual impressions from the 3 cloud types I've converted to the new system so far here: http://www.flightgear.org/forums/viewtopic.php?f=5t=7358start=390#p132335 Stuart - please help: I get anti-shadowing for Stratus clouds, and I don't really understand why... Could this be a normal map problem (I believe it's possible to store the normal map in dds textures) Do we use normal maps for clouds ? No, we don't use the normal maps for the clouds. Instead there are two shadings taking place: 1) Shading based on distance of the sprite to the sun. Effectively we compare a vector from the center of the cloud to the sprite location with the light normal. 2) Shading based on the vertical placement of the sprite in the cloud, so lower sprites are shaded more. This is controlled by the bottom-shade parameter. I suspect that it is the latter that is misbehaving. IIRC the bottom-shader is applied as a factor to the lighting, so using a value of (say) 0.1 should result in a dark cloud bottom. -Stuart -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Future Weather System
2011/8/2 Mathias Fröhlich wrote: So I decoupled these two structures somehow. I have put bv-trees of geometry into the userdata field of the scenegraph. So for the high level operations like tile loading, the scenery paging is used to load and get rid of the bv- trees. The whole intersectable scenery should be there in this form. Using this, you could already speed up ground queries by using these bv-tree leafs for intersection test leaf traversal. I've spent quite a while looking at the scenery code to see where the bv-trees are being generated and saved to the SGSceneUserData, but so far the only place I've found that calls the BoundingVolumeBuildVisitor is the groundcache and ModelRegistry. Furthermore, calling getBVHNode() on the SGSceneUserData associated with a tile nevery returns anything. Am I just missing something completely here, or is there coding required to generate the BVH trees for the scenery tiles themselves (presumably based on the groundcache code?) -Stuart -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Generic Protocol Error -- Error opening serial device COM27 The system cannot find the file specified.
OK, has anyone actually attempted this method, and got it too work, lol bcus I just tried it got the bluescreen of death twice. The syntax definitely does something but it also take the computer down, any suggestions? On Aug 3, 2011 9:11 PM, Derrick Washington ddwas...@gmail.com wrote: Ill try this see if it works, ill get back to u guys later on this week, away on vacation now. But thanks for responding, if anyone else know of sure solution let me know though, but I will be sure to try this out. Oh yes the com port number is correct, not sure y its that high but it is COM27. On Aug 3, 2011 3:20 PM, Csaba Halász csaba.hal...@gmail.com wrote: On Wed, Aug 3, 2011 at 8:53 PM, Gene Buckle ge...@deltasoft.com wrote: COM27 is also a suspicously(sp) high port#. That seems to be quite normal for usb adapters. However you are right that this is the cause of the problem. Quote from msdn: To specify a COM port number greater than 9, use the following syntax: \\.\COM10. This syntax works for all port numbers and hardware that allows COM port numbers to be specified. (source: http://msdn.microsoft.com/en-us/library/aa363858%28v=vs.85%29.aspx) -- Csaba/Jester -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Generic Protocol Error -- Error opening serial device COM27 The system cannot find the file specified.
OK so I found a solution, I think, I changed the COM port number to COM3. That seems to work but now FLIGHTGEAR will not accept inputs for some reason, when I set as shown below, FG just sits there and spins its wheels. If I set it up for output that works just fine. In addition to that I can't setup two generic protocols one for input and one for output, when I do that I just get an error can not open com port. I'm beginning to think that communication through the serial port doesn't work at all. C:\Program Files\FlightGear\bin\Win32\fgfs.exe --fg-root=C:\Program Files\FlightGear\data --fg-scenery=C:\Program Files\FlightGear\data\Scenery;C:\Program Files\FlightGear\scenery;C:\Program Files\FlightGear\terrasync --aircraft=f-14b --control=joystick --enable-random-objects --enable-ai-models --enable-clouds3d --fog-disable --geometry=1280x1024 --bpp=32 --texture-filtering=16 --timeofday=noon --atlas=socket,out,5,localhost,5500,udp --generic=serial,in,3,COM3,115200,FlightGear_GPI On Sat, Aug 6, 2011 at 8:56 PM, Derrick Washington ddwas...@gmail.comwrote: OK, has anyone actually attempted this method, and got it too work, lol bcus I just tried it got the bluescreen of death twice. The syntax definitely does something but it also take the computer down, any suggestions? On Aug 3, 2011 9:11 PM, Derrick Washington ddwas...@gmail.com wrote: Ill try this see if it works, ill get back to u guys later on this week, away on vacation now. But thanks for responding, if anyone else know of sure solution let me know though, but I will be sure to try this out. Oh yes the com port number is correct, not sure y its that high but it is COM27. On Aug 3, 2011 3:20 PM, Csaba Halász csaba.hal...@gmail.com wrote: On Wed, Aug 3, 2011 at 8:53 PM, Gene Buckle ge...@deltasoft.com wrote: COM27 is also a suspicously(sp) high port#. That seems to be quite normal for usb adapters. However you are right that this is the cause of the problem. Quote from msdn: To specify a COM port number greater than 9, use the following syntax: \\.\COM10. This syntax works for all port numbers and hardware that allows COM port numbers to be specified. (source: http://msdn.microsoft.com/en-us/library/aa363858%28v=vs.85%29.aspx) -- Csaba/Jester -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
