Re: [Flightgear-devel] Lightmap question
Tom, -Original Message- From: Thomas Albrecht [mailto:ra...@web.de] Sent: 30 April 2013 23:48 To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Lightmap question Dear shader experts, Can I have a single-channel lightmap, and still use a vec3d in my model.xml to end up with green or red (or whatever) light rendered? As in (roughly) on_screen_color[0] = lightmap-grey-value * vec3d[0] * texture[0] on_screen_color[1] = lightmap-grey-value * vec3d[1] * texture[1] on_screen_color[2] = lightmap-grey-value * vec3d[2] * texture[2] where texture is the base model texture? Docs/README.model-combined.eff says lightmap-color type=vec3d n=0 1.0 1.0 1.0 /lightmap-color - the color of the light for the red channel in the light-map. etc for green and blue channels, but when I use this line, FG complains Failed to load xml: Unrecognized data type 'vec3d' Failed to load model: Unrecognized data type 'vec3d' I guess this works only for multi-channel lightmaps? I.e. with lightmap-multi type=int1/lightmap-multi My .xml looks like this: effect inherits-fromEffects/model-combined-deferred/inherits-from parameters lightmap-enabled type=int1/lightmap-enabled texture n=3 imagetex/DSCF9503_noroofsec_pow2_LM.png/image wrap-srepeat/wrap-s wrap-trepeat/wrap-t /texture !--lightmap-color type=vec3d n=0 1.0 5.0 0.2 /lightmap-color -- lightmap-factor type=float n=01.0/lightmap-factor /parameters object-nameb606/object-name object-nameb610/object-name /effect The lightmap is working correctly - take a look in the b1900d or the b777. The error: Failed to load model: Unrecognized data type 'vec3d' Indicates that you might be using type=vec3d somewhere inside an animation tag - it's only valid in an effect tag. Hth Vivian -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Lightmap question
Tom -Original Message- From: Vivian Meazza [mailto:vivian.mea...@lineone.net] Sent: 01 May 2013 08:47 To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel] Lightmap question Tom, -Original Message- From: Thomas Albrecht [mailto:ra...@web.de] Sent: 30 April 2013 23:48 To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Lightmap question Dear shader experts, Can I have a single-channel lightmap, and still use a vec3d in my model.xml to end up with green or red (or whatever) light rendered? As in (roughly) on_screen_color[0] = lightmap-grey-value * vec3d[0] * texture[0] on_screen_color[1] = lightmap-grey-value * vec3d[1] * texture[1] on_screen_color[2] = lightmap-grey-value * vec3d[2] * texture[2] where texture is the base model texture? Docs/README.model-combined.eff says lightmap-color type=vec3d n=0 1.0 1.0 1.0 /lightmap-color - the color of the light for the red channel in the light-map. etc for green and blue channels, but when I use this line, FG complains Failed to load xml: Unrecognized data type 'vec3d' Failed to load model: Unrecognized data type 'vec3d' I guess this works only for multi-channel lightmaps? I.e. with lightmap-multi type=int1/lightmap-multi My .xml looks like this: effect inherits-fromEffects/model-combined-deferred/inherits-from parameters lightmap-enabled type=int1/lightmap-enabled texture n=3 imagetex/DSCF9503_noroofsec_pow2_LM.png/image wrap-srepeat/wrap-s wrap-trepeat/wrap-t /texture !--lightmap-color type=vec3d n=0 1.0 5.0 0.2 /lightmap-color -- lightmap-factor type=float n=01.0/lightmap-factor /parameters object-nameb606/object-name object-nameb610/object-name /effect The lightmap is working correctly - take a look in the b1900d or the b777. The error: Failed to load model: Unrecognized data type 'vec3d' Indicates that you might be using type=vec3d somewhere inside an animation tag - it's only valid in an effect tag. Hth My previous answer wasn't all that helpful now that I read it again. You can do what you want, but not inline in the model.xml file - the type=vec3d is not recognized anywhere outside an effect and is causing the error. Do your effect config in a local .eff file, then inherit from that in your model. Hope this is a better explanation Vivian -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Atmospheric Light Scattering
Heiko Sent: 30 April 2013 18:46 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Atmospheric Light Scattering Now, sorry, FG snapshots With ALS and Without Rembrandt https://sites.google.com/site/grtuxhangarctd/other-download/ P-38_demo1.png Who said we don't need a specific version when using ALS ? I have to wonder- because you don't need a specific version for ALS! Use the shader as it is in current FGData and it will work in ALS, Default- renderer and Rembrandt. The only thing is, that lightmaps, as possible in ALS and Default Renderer, doesn't look all to good in Rembrandt in combination (!) with light volumes. But this can be solved. One model, one version- three renderer. FlightGear! That's not quite right: you should be able to use one _effect_ across all rendering schemes, but under the hood different flavours of shaders do the work. Depending on a number of factors - weather mode selected/light implementation, the outcome on the model can look quite different. I would guess that is what we are seeing on the P38 examples shown (and that's quite some model - wow!). We have recently broken that principle with the grain effect - it only works in ALS. But you are quite right to say that we don't need special models for ALS/Default/Rembrandt rendering schemes. You might choose to implement features in Rembrandt, and then you might want to add different features so that those features would still work in the default and ALS schemes, but you don't have to. A good example of that might be landing lights that are implemented on a particular model under Rembrandt, but are simply absent in other schemes. Apart from making sure that transparencies work in Rembrandt, a modeller doesn't have to anything at all to the effects to make them work right across the board. Vivian -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Lightmap question
You can do what you want, but not inline in the model.xml file - the type=vec3d is not recognized anywhere outside an effect and is causing the error. Do your effect config in a local .eff file, then inherit from that in your model. Thanks Vivian, I wasn't aware of that. Works great now. Tom -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Atmospheric Light Scattering
Arnt, I could not answer that question ..yes? I'd like to see the commandlines and menu options you used to create these screenshots so we can try reproduce them. This _may_ e.g. be a driver bug on only your box. Here you will find both files content which answer your request: https://sites.google.com/site/grtuxhangarctd/other-download/.fgfsrc which point to the following https://sites.google.com/site/grtuxhangarctd/other-download/preferences-devel.xml You can notice that last one is situated within the HOME .fgfs directory These two files refer to our community/team mainframe which is being used to develop our FG models. The screenshots are made with it. By the way the multi core systems is not used by FlightGear , since only OSG can use it ( unfortunately wrongly at least within FG ). If you are ONLY running FlightGear with your computer you don't need a multi core, there won't be any profit. Multi core is only useful if you are working on other developments (which explain our equipment). Hope it answer your question. Kind regard Ahmad On 30 April 2013 15:06, Arnt Karlsen a...@iaksess.no wrote: On Tue, 30 Apr 2013 14:24:42 +0200, grtuxhangar wrote in message CAFEVUtBb=gxvwqaak1u7zzssgn26ndx88zbmg8+5sp1kdi-...@mail.gmail.com: Hello everybody Well, let's come to some example, then the users could appreciate There, a lot of snapshots i have just received from David (one of our team's member) Those snapshots were done with FG Git, and France 850 Scenery. Only the vegetation is being an old one , since getting some trouble with the last version. The computer is a mainframe with 2 Nvidia cards SLI Architecture GPU geforce GTX 560 ti CUDA Cores:448 ..mainframe??? Details, please. NV Driver 319.12 ..which NV 319.12 driver? Starting with FG snapshots Without ALS and With Rembrandt ..yes? I'd like to see the commandlines and menu options you used to create these screenshots so we can try reproduce them. This _may_ e.g. be a driver bug on only your box. ..only these 2 screenshots are directly comparable to the 3 test cases you present, so I'd like to see your Without ALS and With Rembrandt version of these 2: Now FG snapshots Without ALS and Without Rembrandt https://sites.google.com/site/grtuxhangarctd/other-download/P-38_demo2.png Now, sorry, FG snapshots With ALS and Without Rembrandt https://sites.google.com/site/grtuxhangarctd/other-download/P-38_demo1.png ..2(?) years back, I was the only one here to see all pitch black aircraft with ATI Radeon cards on X.org radeon drivers. Who said we don't need a specific version when using ALS ? BTW We had to search for a place were we could load Model with ALS You probably notice, it is the P-38L model, to fly with Rembrandt or Without Rembrandt ONLY one model to load :) . Sorry it is not ALS Compliant. ..are there other ALS-non-compliant models? We have not chosen the most beautiful one it is only an example. You may want to take acknowledge of some snapshots done with Rembrandt , part of the grtux_hangar related. there the link https://picasaweb.google.com/117502256492585017152 ..does any of these compare the ALS vs Rembrandt vs default etc test cases? All I've seen there this far, are pretty screenshots. All the best to FG Community Ahmad -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Atmospheric Light Scattering
On Wed, 1 May 2013 14:00:03 +0200, grtuxhangar wrote in message cafevutcj5zknsb+l4_75ea85br-mswbel8zyci08s_n45xr...@mail.gmail.com: Arnt, I could not answer that question ..those are 2 questions on the same thing, #1 ..yes? I'd like to see the commandlines and ..#2: menu options you used to create these screenshots ..#3 is why I wand your answer(s): so we can try reproduce them. ..this is my _guess_: This _may_ e.g. be a driver bug on only your box. Here you will find both files content which answer your request: https://sites.google.com/site/grtuxhangarctd/other-download/.fgfsrc ..so if I enter those command line options and have exactly the same models and exactly the same scenery and exactly the same sim weather, I should see exactly the same thing and be able to make exactly the same screen shots. ..an easier way is, specify everything, e.g. ... --on-ground Start at ground level (default) --in-air Start in air (implied when using --altitude) ...and then your time options and your specific Initial Position and Orientation: options, e.g. --runway=rwy_no Specify starting runway (must also specify an airport) ... or directly with e.g. these: --lon=degreesStarting longitude (west = -) --lat=degreesStarting latitude (south = -) --altitude=value Starting altitude (in feet unless --units-meters specified) --heading=degreesSpecify heading (yaw) angle (Psi) --roll=degrees Specify roll angle (Phi) --pitch=degrees Specify pitch angle (Theta) ..these options can be put in your various screenshot .fgfsrc, you may e.g. want one for each test case. And, I can see a use for a --startup-paused option, to make screenshots. which point to the following https://sites.google.com/site/grtuxhangarctd/other-download/preferences-devel.xml You can notice that last one is situated within the HOME .fgfs directory These two files refer to our community/team mainframe which is being used to develop our FG models. The screenshots are made with it. By the way the multi core systems is not used by FlightGear , since only OSG can use it ( unfortunately wrongly at least within FG ). If you are ONLY running FlightGear with your computer you don't need a multi core, there won't be any profit. ..I disagree, IME I'm still able to recover my boxes when FG hangs or tries frying cpu. Multi core is only useful if you are working on other developments (which explain our equipment). Hope it answer your question. Kind regard Ahmad On 30 April 2013 15:06, Arnt Karlsen a...@iaksess.no wrote: On Tue, 30 Apr 2013 14:24:42 +0200, grtuxhangar wrote in message CAFEVUtBb=gxvwqaak1u7zzssgn26ndx88zbmg8+5sp1kdi-...@mail.gmail.com: Hello everybody Well, let's come to some example, then the users could appreciate There, a lot of snapshots i have just received from David (one of our team's member) Those snapshots were done with FG Git, and France 850 Scenery. Only the vegetation is being an old one , since getting some trouble with the last version. The computer is a mainframe with 2 Nvidia cards SLI Architecture GPU geforce GTX 560 ti CUDA Cores:448 ..mainframe??? Details, please. NV Driver 319.12 ..which NV 319.12 driver? Starting with FG snapshots Without ALS and With Rembrandt ..yes? I'd like to see the commandlines and menu options you used to create these screenshots so we can try reproduce them. This _may_ e.g. be a driver bug on only your box. ..only these 2 screenshots are directly comparable to the 3 test cases you present, so I'd like to see your Without ALS and With Rembrandt version of these 2: Now FG snapshots Without ALS and Without Rembrandt https://sites.google.com/site/grtuxhangarctd/other-download/P-38_demo2.png Now, sorry, FG snapshots With ALS and Without Rembrandt https://sites.google.com/site/grtuxhangarctd/other-download/P-38_demo1.png ..2(?) years back, I was the only one here to see all pitch black aircraft with ATI Radeon cards on X.org radeon drivers. Who said we don't need a specific version when using ALS ? BTW We had to search for a place were we could load Model with ALS You probably notice, it is the P-38L model, to fly with Rembrandt or Without Rembrandt ONLY one model to load :) . Sorry it is not ALS Compliant. ..are there other ALS-non-compliant models? We have not chosen the most beautiful one it is only an example. You may want to take acknowledge of some snapshots done with Rembrandt , part of the grtux_hangar related. there the link https://picasaweb.google.com/117502256492585017152 ..does any of these compare the ALS vs Rembrandt vs default etc test
Re: [Flightgear-devel] Atmospheric Light Scattering
Arnst you wrote menu options you used to create these screenshots ..#3 is why I wand your answer(s): so we can try reproduce them. I am not sure i understand your question : You want to know how does the screenshots were done ? I gave you the answer before Just USE== F3 key===, no menu , not any others tools, that's done. Your Guess about driver is out, since whith an older driver we got the same, wrong result. Then, to be sure before giving our screenshots we made it again with the very last driver ( rebuild nvidia.ko ) You could only Guess the GPU is wrong, which would make that whole family GF110 GPU wrong (there is a lot) The Box ! how could it be ? FG has been built without any specific modifications, we are using generic tools. Like said before, we had only to find a place within our scenery data to avoid any crash with that Charcot's Renderer ( cf Heiko ). .so if I enter those command line options and have exactly the same models and exactly the same scenery and exactly the same sim weather, I should see exactly the same thing and be able to make exactly the same screen shots Which is not useful here since the diff is: FROM == Without Rembrandt and Without Atmospheric.LS which is the most simple, VERSUS == With Rembrandt and With Atmospheric.LS. The snapshots with Rembrandt are not involved here, since the textures remains right, correctly enlightened, and the shadow is there. Any others official snapshots with that model and any other models from our Hangar do not give any odd picture, with Rembrandt. Kind regards. Ahmad On 1 May 2013 15:43, Arnt Karlsen a...@iaksess.no wrote: On Wed, 1 May 2013 14:00:03 +0200, grtuxhangar wrote in message cafevutcj5zknsb+l4_75ea85br-mswbel8zyci08s_n45xr...@mail.gmail.com: Arnt, I could not answer that question ..those are 2 questions on the same thing, #1 ..yes? I'd like to see the commandlines and ..#2: menu options you used to create these screenshots ..#3 is why I wand your answer(s): so we can try reproduce them. ..this is my _guess_: This _may_ e.g. be a driver bug on only your box. Here you will find both files content which answer your request: https://sites.google.com/site/grtuxhangarctd/other-download/.fgfsrc ..so if I enter those command line options and have exactly the same models and exactly the same scenery and exactly the same sim weather, I should see exactly the same thing and be able to make exactly the same screen shots. ..an easier way is, specify everything, e.g. ... --on-ground Start at ground level (default) --in-air Start in air (implied when using --altitude) ...and then your time options and your specific Initial Position and Orientation: options, e.g. --runway=rwy_no Specify starting runway (must also specify an airport) ... or directly with e.g. these: --lon=degreesStarting longitude (west = -) --lat=degreesStarting latitude (south = -) --altitude=value Starting altitude (in feet unless --units-meters specified) --heading=degreesSpecify heading (yaw) angle (Psi) --roll=degrees Specify roll angle (Phi) --pitch=degrees Specify pitch angle (Theta) ..these options can be put in your various screenshot .fgfsrc, you may e.g. want one for each test case. And, I can see a use for a --startup-paused option, to make screenshots. which point to the following https://sites.google.com/site/grtuxhangarctd/other-download/preferences-devel.xml You can notice that last one is situated within the HOME .fgfs directory These two files refer to our community/team mainframe which is being used to develop our FG models. The screenshots are made with it. By the way the multi core systems is not used by FlightGear , since only OSG can use it ( unfortunately wrongly at least within FG ). If you are ONLY running FlightGear with your computer you don't need a multi core, there won't be any profit. ..I disagree, IME I'm still able to recover my boxes when FG hangs or tries frying cpu. Multi core is only useful if you are working on other developments (which explain our equipment). Hope it answer your question. Kind regard Ahmad On 30 April 2013 15:06, Arnt Karlsen a...@iaksess.no wrote: On Tue, 30 Apr 2013 14:24:42 +0200, grtuxhangar wrote in message CAFEVUtBb=gxvwqaak1u7zzssgn26ndx88zbmg8+5sp1kdi-...@mail.gmail.com: Hello everybody Well, let's come to some example, then the users could appreciate There, a lot of snapshots i have just received from David (one of our team's member) Those snapshots were done with FG Git, and France 850 Scenery. Only the vegetation is being an old one , since getting some trouble with
Re: [Flightgear-devel] Atmospheric Light Scattering
sorry, you must read Which is not useful here since the diff is: FROM == Without Rembrandt and Without Atmospheric.LS which is the most simple, VERSUS == Without Rembrandt and With Atmospheric.LS. On 1 May 2013 16:59, grtuxhangar team hohora...@gmail.com wrote: Arnst you wrote menu options you used to create these screenshots ..#3 is why I wand your answer(s): so we can try reproduce them. I am not sure i understand your question : You want to know how does the screenshots were done ? I gave you the answer before Just USE== F3 key===, no menu , not any others tools, that's done. Your Guess about driver is out, since whith an older driver we got the same, wrong result. Then, to be sure before giving our screenshots we made it again with the very last driver ( rebuild nvidia.ko ) You could only Guess the GPU is wrong, which would make that whole family GF110 GPU wrong (there is a lot) The Box ! how could it be ? FG has been built without any specific modifications, we are using generic tools. Like said before, we had only to find a place within our scenery data to avoid any crash with that Charcot's Renderer ( cf Heiko ). .so if I enter those command line options and have exactly the same models and exactly the same scenery and exactly the same sim weather, I should see exactly the same thing and be able to make exactly the same screen shots Which is not useful here since the diff is: FROM == Without Rembrandt and Without Atmospheric.LS which is the most simple, VERSUS == With Rembrandt and With Atmospheric.LS. The snapshots with Rembrandt are not involved here, since the textures remains right, correctly enlightened, and the shadow is there. Any others official snapshots with that model and any other models from our Hangar do not give any odd picture, with Rembrandt. Kind regards. Ahmad On 1 May 2013 15:43, Arnt Karlsen a...@iaksess.no wrote: On Wed, 1 May 2013 14:00:03 +0200, grtuxhangar wrote in message cafevutcj5zknsb+l4_75ea85br-mswbel8zyci08s_n45xr...@mail.gmail.com: Arnt, I could not answer that question ..those are 2 questions on the same thing, #1 ..yes? I'd like to see the commandlines and ..#2: menu options you used to create these screenshots ..#3 is why I wand your answer(s): so we can try reproduce them. ..this is my _guess_: This _may_ e.g. be a driver bug on only your box. Here you will find both files content which answer your request: https://sites.google.com/site/grtuxhangarctd/other-download/.fgfsrc ..so if I enter those command line options and have exactly the same models and exactly the same scenery and exactly the same sim weather, I should see exactly the same thing and be able to make exactly the same screen shots. ..an easier way is, specify everything, e.g. ... --on-ground Start at ground level (default) --in-air Start in air (implied when using --altitude) ...and then your time options and your specific Initial Position and Orientation: options, e.g. --runway=rwy_no Specify starting runway (must also specify an airport) ... or directly with e.g. these: --lon=degreesStarting longitude (west = -) --lat=degreesStarting latitude (south = -) --altitude=value Starting altitude (in feet unless --units-meters specified) --heading=degreesSpecify heading (yaw) angle (Psi) --roll=degrees Specify roll angle (Phi) --pitch=degrees Specify pitch angle (Theta) ..these options can be put in your various screenshot .fgfsrc, you may e.g. want one for each test case. And, I can see a use for a --startup-paused option, to make screenshots. which point to the following https://sites.google.com/site/grtuxhangarctd/other-download/preferences-devel.xml You can notice that last one is situated within the HOME .fgfs directory These two files refer to our community/team mainframe which is being used to develop our FG models. The screenshots are made with it. By the way the multi core systems is not used by FlightGear , since only OSG can use it ( unfortunately wrongly at least within FG ). If you are ONLY running FlightGear with your computer you don't need a multi core, there won't be any profit. ..I disagree, IME I'm still able to recover my boxes when FG hangs or tries frying cpu. Multi core is only useful if you are working on other developments (which explain our equipment). Hope it answer your question. Kind regard Ahmad On 30 April 2013 15:06, Arnt Karlsen a...@iaksess.no wrote: On Tue, 30 Apr 2013 14:24:42 +0200, grtuxhangar wrote in message CAFEVUtBb=gxvwqaak1u7zzssgn26ndx88zbmg8+5sp1kdi-...@mail.gmail.com: Hello everybody Well,
Re: [Flightgear-devel] Tree issues
On Thu, Apr 25, 2013 at 11:50 PM, Vivian Meazza wrote: I'm using a very recent pull of fgdata with no local mods. The hat effect shows up from low angles in all material modes - regional/global/dds. It's most apparent at EGMH, but can also be seen at KSFO. At higher angles or if I zoom in it disappears from the closer trees - but, like you, I can still see it at longer ranges. The angle/range effect would suggest that it's a mipmap thing - perhaps try a bit more space around the trees in the texture? I've just pushed a fix to simgear that reduces the height of the UV mapping by 0.004. Please let me know if this fixes the problem. I expect that some trees will have been slightly trimmed by this. I'll go through the textures and correct them once you and Thorsten confirm the issue is fixed. Thanks for your patience. -Stuart -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Further enhancement to checklists - binding support
Hi All, I've just pushed a further enhancement to the checklist feature. Aircraft authors may now add one or more binding elements to a checklist item. Conceptually, these are the actions that the user should execute to complete the item. The checklist GUI displays items with such binding elements with an additional [] button. Clicking on the button executes the bindings, allowing the user to watch as the computer/co-pilot/instructor executes the checklist item. The binding element is exactly as you would expect - so property-assign, nasal etc. works. Due to the power of Nasal and properties, this feature only required 13 lines of code to write, most of which is displaying the button! I'm planning to extend this function so that checklists with one or more items containing a binding element can have an (optional) button to execute the entire checklist. I'm still thinking of how best to implement this, as I think one would want a gap between each item. I'd highlight the property-interpolate command which provides a very convenient way to interpolate a property to a new value. See Docs/README.commands if (like me) you were unaware of this :). I've updated the c172p checklists to use this feature, including some rather cute interpolations of the throttle, mixture and trim controls. Thanks to Hooray on the forum for suggesting this enhancement ages ago. Feedback welcome as always. -Stuart -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Tree issues
: Stuart Sent: 01 May 2013 22:09 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Tree issues On Thu, Apr 25, 2013 at 11:50 PM, Vivian Meazza wrote: I'm using a very recent pull of fgdata with no local mods. The hat effect shows up from low angles in all material modes - regional/global/dds. It's most apparent at EGMH, but can also be seen at KSFO. At higher angles or if I zoom in it disappears from the closer trees - but, like you, I can still see it at longer ranges. The angle/range effect would suggest that it's a mipmap thing - perhaps try a bit more space around the trees in the texture? I've just pushed a fix to simgear that reduces the height of the UV mapping by 0.004. Please let me know if this fixes the problem. I expect that some trees will have been slightly trimmed by this. I'll go through the textures and correct them once you and Thorsten confirm the issue is fixed. Trying that. Vivian -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Atmospheric Light Scattering
On Wed, 1 May 2013 16:59:41 +0200, grtuxhangar wrote in message CAFEVUtAcO--uEpj+vDHCG4k=q0lktoweqnr2avdx+8gshhz...@mail.gmail.com: Arnst you wrote menu options you used to create these screenshots ..#3 is why I wand your answer(s): so we can try reproduce them. I am not sure i understand your question : You want to know how does the screenshots were done ? I gave you the answer before Just USE== F3 key===, no menu , not any others tools, that's done. ..your F3 key gives me the C172 on the active runway at KSFO. ..so, my question is, how do you set up your FG screenshot scene, _before_ you use the F3 button to take the screenshot? On 1 May 2013 15:43, Arnt Karlsen a...@iaksess.no wrote: On Wed, 1 May 2013 14:00:03 +0200, grtuxhangar wrote in message cafevutcj5zknsb+l4_75ea85br-mswbel8zyci08s_n45xr...@mail.gmail.com: Here you will find both files content which answer your request: https://sites.google.com/site/grtuxhangarctd/other-download/.fgfsrc ..so if I enter those command line options and have exactly the same models and exactly the same scenery and exactly the same sim weather, I should see exactly the same thing and be able to make exactly the same screen shots. ..an easier way is, specify everything, e.g. ... --on-ground Start at ground level (default) --in-air Start in air (implied when using --altitude) ...and then your time options and your specific Initial Position and Orientation: options, e.g. --runway=rwy_no Specify starting runway (must also specify an airport) ... or directly with e.g. these: --lon=degreesStarting longitude (west = -) --lat=degreesStarting latitude (south = -) --altitude=value Starting altitude (in feet unless --units-meters specified) --heading=degreesSpecify heading (yaw) angle (Psi) --roll=degrees Specify roll angle (Phi) --pitch=degrees Specify pitch angle (Theta) ..these options can be put in your various screenshot .fgfsrc, you may e.g. want one for each test case. And, I can see a use for a --startup-paused option, to make screenshots. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Atmospheric Light Scattering
Arnt Oh sorry , i thought you were using FG for years. I know at the beginning we could have some problem. NO it is not MY F3 KEY it is an FG feature Key. Just look at the fgdata/keyboard.xml content. you will notice at the line 1134 the key key n=259 nameF3/name descCapture screen/desc That file is very useful to understand what are the specific keys within FG. That is. Ahmad On 2 May 2013 00:39, Arnt Karlsen a...@iaksess.no wrote: On Wed, 1 May 2013 16:59:41 +0200, grtuxhangar wrote in message CAFEVUtAcO--uEpj+vDHCG4k=q0lktoweqnr2avdx+8gshhz...@mail.gmail.com: Arnst you wrote menu options you used to create these screenshots ..#3 is why I wand your answer(s): so we can try reproduce them. I am not sure i understand your question : You want to know how does the screenshots were done ? I gave you the answer before Just USE== F3 key===, no menu , not any others tools, that's done. ..your F3 key gives me the C172 on the active runway at KSFO. ..so, my question is, how do you set up your FG screenshot scene, _before_ you use the F3 button to take the screenshot? On 1 May 2013 15:43, Arnt Karlsen a...@iaksess.no wrote: On Wed, 1 May 2013 14:00:03 +0200, grtuxhangar wrote in message cafevutcj5zknsb+l4_75ea85br-mswbel8zyci08s_n45xr...@mail.gmail.com: Here you will find both files content which answer your request: https://sites.google.com/site/grtuxhangarctd/other-download/.fgfsrc ..so if I enter those command line options and have exactly the same models and exactly the same scenery and exactly the same sim weather, I should see exactly the same thing and be able to make exactly the same screen shots. ..an easier way is, specify everything, e.g. ... --on-ground Start at ground level (default) --in-air Start in air (implied when using --altitude) ...and then your time options and your specific Initial Position and Orientation: options, e.g. --runway=rwy_no Specify starting runway (must also specify an airport) ... or directly with e.g. these: --lon=degreesStarting longitude (west = -) --lat=degreesStarting latitude (south = -) --altitude=value Starting altitude (in feet unless --units-meters specified) --heading=degreesSpecify heading (yaw) angle (Psi) --roll=degrees Specify roll angle (Phi) --pitch=degrees Specify pitch angle (Theta) ..these options can be put in your various screenshot .fgfsrc, you may e.g. want one for each test case. And, I can see a use for a --startup-paused option, to make screenshots. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
