Re: [Flightgear-devel] Cessna 172p cockpit improvement
On Wednesday 21 December 2011 04:09:35 Stuart Buchanan wrote: > On Wed, Dec 21, 2011 at 11:00 AM, Torsten Dreyer wrote: > >> I prefer manually syncing and checking that the changes are valid, > >> rather than blindly over-riding what we've already got. > > > > Hi Stuart, > > > > this > > - > > - aero/alpha-rad > > - > > + aero/alpha-rad > > -1.8000 > > > > reintroduces a bug, IIRC that had something to do with tailwind > > behavior. I think we should keep the function. > > Agreed - that's a mistake in my checkin. I will correct it. > > -Stuart I missed backporting this to the JSBSim side. I've also got an experimental FDM with many more of these wrapped in sine or cosine functions as appropriate. This will make the forces and moments trend in the correct directions, even if the magnitudes aren't quite right. Perhaps a improved stall system for JSBSim will be ready for 2.8 Ron -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 172p cockpit improvement
On Wednesday 21 December 2011 14:50:39 Stuart Buchanan wrote: > On Wed, Dec 21, 2011 at 5:53 PM, Torsten Dreyer wrote: > >> Agreed - that's a mistake in my checkin. I will correct it. > >> > >> -Stuart > > > > OK - one more. > > > > velocity including the propulsion induced > > velocity. > > > > velocities/u-aero-fps > > propulsion/engine/prop-induced-velocity_fps > > propulsion/engine/prop-induced-velocity_fps > > > > > > > > Why is prop-induced-velocity_fps added twice? Is that by intention? > > > >From discussion with AndersG on IRC who checked his aerodynamics text, > > we believe it is intentional. > > "the final increase in slipstream velocity (over the free stream velocity) > is 2* the increase in velocity at the actuator disk. Which is consistent > with the c172p FDM " > > -Stuart Yes, its added twice to avoid the multiplication. Ron -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Announcing Project Rembrandt
Frederic, I'm not a specialist but I try to be well informed about graphics programming. A while ago I was messing around with shadow mapping but didn't know how to port it to FlightGear. In such a huge project it is difficult to find out how the internals work. I would like to test your patches. I can implement PercentageCloserFiltering (PCF) if you haven't done it already. cheers, Robert 2011/12/20 Frederic Bouvier > Hi Robert, > > nothing changed for the GUI and the HUD. > You seem to be a specialist. Do you plan to contribute ? > > Regards, > -Fred > -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Announcing Project Rembrandt
> > http://frbouvi.free.fr/flightsim/project_rembrandt_2.png > > http://frbouvi.free.fr/flightsim/project_rembrandt_3.png > > > > Admittedly, something should be done to increase shadow map > > resolution near the viewer. I have ideas on how to do that, > > but it's for another day ;) > > That looks _really_ nice. It just oozes with potential. :) Now a bit better, with a bigger shadow map and 4 cascades : http://youtu.be/RIetPh8iJXk Regards, -Fred -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 172p cockpit improvement
On Wed, Dec 21, 2011 at 5:53 PM, Torsten Dreyer wrote: >> Agreed - that's a mistake in my checkin. I will correct it. >> >> -Stuart > > OK - one more. > > velocity including the propulsion induced > velocity. > > velocities/u-aero-fps > propulsion/engine/prop-induced-velocity_fps > propulsion/engine/prop-induced-velocity_fps > > > > Why is prop-induced-velocity_fps added twice? Is that by intention? >From discussion with AndersG on IRC who checked his aerodynamics text, we believe it is intentional. "the final increase in slipstream velocity (over the free stream velocity) is 2* the increase in velocity at the actuator disk. Which is consistent with the c172p FDM " -Stuart -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] deteriorating cull performance kills fps
2011/12/21 Mathias Fröhlich : > > Yes, I saw this a few weeks ago on a long flight. > But I did not see a chance to reproduce what I saw. So I did not look > closer... Seems to be gone now :) Any comments for my other question, about background model loading? -- Csaba/Jester -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] deteriorating cull performance kills fps
Hi, On Wednesday, December 21, 2011 00:42:04 Csaba Halász wrote: > Really nobody else seeing this? Any ideas what I could look at to > investigate further? Yes, I saw this a few weeks ago on a long flight. But I did not see a chance to reproduce what I saw. So I did not look closer... Mathias -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 172p cockpit improvement
> Agreed - that's a mistake in my checkin. I will correct it. > > -Stuart OK - one more. velocity including the propulsion induced velocity. velocities/u-aero-fps propulsion/engine/prop-induced-velocity_fps propulsion/engine/prop-induced-velocity_fps Why is prop-induced-velocity_fps added twice? Is that by intention? Torsten -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] c172p cockpit update (3)
On Wed, 2011-12-21 at 16:09 +, Stephan Bourgeois wrote: > [...] [GeForce 7050 PV, 195.36.24 driver, glx ver. 1.4] Can you please try to update your nvidia kernel module? I use 285.05.09 here (but with a 9500 GT). Maybe that will already to the trick. > > [...] I have cloned fgdata on gitorious and sent a merge request. This is > for me to check that I understand the workflow with git. As for me (as a non-developer) it looks the right way I saw it several times before. So it might looks green. > > Last question: the wiki > http://wiki.flightgear.org/Building_FlightGear_-_Linux is not up to date > regarding how to build from git. It talks about running autogen.sh and > configure. These are only to be found in the master branch. I built simgear > and flightgear with ccmake with the method described for compiling OSG. > Should I update the wiki, add a paragraph on ccmake? No need for a paragraph! As I understood the last changes, autogen.sh + complete autoconfigure is history it SG/FG, so only cmake is there. I use out-of-source-tree builds btw. (really easy to archive). > > Thank you. I am waiting for your comments. Welcome. Hope mine help a little. :) > > Stephan. Roland signature.asc Description: This is a digitally signed message part -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] c172p cockpit update (3)
Hi everybody, Heiko, I have built flightgear from git next branch, using OSG stable release 3.0.1. Everything loads correctly from fgdata, the shading looks beautiful. I can now test my changes with an up-to-date release. I have one question: how often should I fetch and recompile, considering that I am only working on the model and the instruments, not the FDM? Unfortunately, my card doesn't support OpenGL 2.0 and I am getting glLinkProgram "" Failed. I don't have this error when running the 2.4.0. I guess this is due to the version change of the OSG libraries. Does it mean that 2.6.0 will never run on my graphics card? [GeForce 7050 PV, 195.36.24 driver, glx ver. 1.4] I have made minor changes to the cockpit geometry. Centered the clock and the EGT instrument in Model/c172p.xml. I have cloned fgdata on gitorious and sent a merge request. This is for me to check that I understand the workflow with git. Last question: the wiki http://wiki.flightgear.org/Building_FlightGear_-_Linux is not up to date regarding how to build from git. It talks about running autogen.sh and configure. These are only to be found in the master branch. I built simgear and flightgear with ccmake with the method described for compiling OSG. Should I update the wiki, add a paragraph on ccmake? Thank you. I am waiting for your comments. Stephan. -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Winter sand textures
I think this is a small bug: The winter texture declarations in materials(-dds).xml reference Terrain.winter/sand1.png to Terrain.winter/sand6.png but the only existing texture sheet seems to be Terrain.winter/sand.png (spotted this by ugly grey spots in the landscape flying with winter textures across Denali). Seems to be fixed just fine by replacing all references in the winter texture declaration to the existing texture sheet. Cheers, * Thorsten -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 172p cockpit improvement
On Wed, Dec 21, 2011 at 11:00 AM, Torsten Dreyer wrote: >> >> I prefer manually syncing and checking that the changes are valid, rather >> than >> blindly over-riding what we've already got. > > Hi Stuart, > > this > - > - aero/alpha-rad > - > + aero/alpha-rad > -1.8000 > > reintroduces a bug, IIRC that had something to do with tailwind > behavior. I think we should keep the function. Agreed - that's a mistake in my checkin. I will correct it. -Stuart -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 172p cockpit improvement
> > I prefer manually syncing and checking that the changes are valid, rather than > blindly over-riding what we've already got. Hi Stuart, this - -aero/alpha-rad - +aero/alpha-rad -1.8000 reintroduces a bug, IIRC that had something to do with tailwind behavior. I think we should keep the function. Torsten -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [Flightgear-commitlogs] TerraGear / Custom
Martin Spott wrote: > I've been using "osm2pgsql" for years for importing The Planet Dump > into PostGIS and so far I'm quite satisfied. After the bare import I'm > using a custom script to separate the various road types into distinct > tables/layers, something like: > > landcover=> SELECT osm_id, access, admin_level, z_order, way_area, > wkb_geometry > landcover-> INTO osm_motorway > landcover-> FROM planet_osm_line > landcover-> WHERE highway LIKE 'motorway%' > landcover-> AND ST_GeometryType(wkb_geometry) LIKE 'ST_LineString'; > > > That way I don't have to query the entire "planet_osm_line" if the user > selects a large scale which doesn't include all the residential roads. > I'd certainly extend this to "SELECT * [...]" if required ;-) Done - works, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 172p cockpit improvement
On Wed, 2011-12-21 at 10:36 +, Stuart Buchanan wrote: > There IS a script that copies FDMs from JSBSim over to FG to keep them > up to date. However, I don't know if it's working. It should work properly but is getting increasingly difficult to use since some models are maintained in JSBSim CVS and others in the flightgear base package. It is often a matter of cherry picking by hand eventually. Erik -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 172p cockpit improvement
On Wed, Dec 21, 2011 at 9:51 AM, Martin Spott wrote: > Stuart Buchanan wrote: >> On Mon, Dec 19, 2011 at 10:07 AM, Martin Spott wrote: >>> Ron Jensen wrote: >>> I just noticed the c172p.xml (FDM) in FGData doesn't match the one in JSBSim. >>> >>> What's your conclusion ? >> >> Conclusion is that the FG c172p FDM is out of date and doesn't include >> the latest changes that Ron made [...] > > I just wonder if it's really the most clever idea to have FG's default > aircraft FDM maintained outside FG without an established procedure to > merge updates into FG this sounds rather obscure, to put it > mildly. There IS a script that copies FDMs from JSBSim over to FG to keep them up to date. However, I don't know if it's working. I'm happy with manually updating the FG c172p FDM when appropriate - though probably more regularly than once per release, and ideally not immediately after feature freeze! I prefer manually syncing and checking that the changes are valid, rather than blindly over-riding what we've already got. -Stuart -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 172p cockpit improvement
Stuart Buchanan wrote: > On Mon, Dec 19, 2011 at 10:07 AM, Martin Spott wrote: >> Ron Jensen wrote: >> >>> I just noticed the c172p.xml (FDM) in FGData doesn't match the one in >>> JSBSim. >> >> What's your conclusion ? > > Conclusion is that the FG c172p FDM is out of date and doesn't include > the latest changes that Ron made [...] I just wonder if it's really the most clever idea to have FG's default aircraft FDM maintained outside FG without an established procedure to merge updates into FG this sounds rather obscure, to put it mildly. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] deteriorating cull performance kills fps
On 21 Dec 2011, at 02:47, Csaba Halász wrote: > Recompiled with fresh OSG/SVN and cull times were now stable at least > for the duration of the 30 minute parked test. > I will re-enable eye candy and do some flights tomorrow, but I hope > the mysterious problem is fixed. Apologies for keeping quiet - it would be good if this fixes your problem! James -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 172p cockpit improvement
On Wed, Dec 21, 2011 at 9:40 AM, Stuart Buchanan wrote: > I've not committed these changes to the FG c172p FDM. Sorry, that should be "I've _now_ committed these changes to the FG c172p FDM" -Stuart -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Cessna 172p cockpit improvement
On Mon, Dec 19, 2011 at 10:07 AM, Martin Spott wrote: > Ron Jensen wrote: > >> I just noticed the c172p.xml (FDM) in FGData doesn't match the one in JSBSim. > > What's your conclusion ? Conclusion is that the FG c172p FDM is out of date and doesn't include the latest changes that Ron made to "Add propellor induced velocity factor to Cmde and Cndr. Enhances ground operations.". I _think_ means additional prop-wash to increase rudder effectiveness and wing airflow at low airspeeds. I've not committed these changes to the FG c172p FDM. -Stuart -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
