Re: [Flightgear-devel] In-sim selection of materials.xml file - what to call DDS?
The reason I didn't just label it material definitions was that I don't think that a new user is going to understand what that means, while the concept of different textures should be familiar to people who have some background in graphics, or gaming. I'd go for something like 'terrain texture scheme'. For anything else, you really have to understand what the role of materials.xml in Flightgear is. The people who do understand can overlook an incomplete label, the people who don't will primarily notice changed textures. Why not use 'Global alternative scheme (dds format)' or something like that - I think the info that this is based on dds is relevant for those who can't actually display dds properly, but it doesn't need to be overemphasized. * Thorsten -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New materials.xml elements to control object/tree density depending on slope angle
Hi Stuart, played around with this a bit yesterday... *very* nice feature! The default values look about right to me from a typical temperate latitudes viewpoint, and using much smaller values gives a quite nice effect possibly suitable for more northerly latitudes. I agree that the defaults 45/60 seem quite realistic as far as real vegetation cover goes, but the problem is our terrain: Due to the coarse resolution in default terrain, we systematically underestimate steep slopes. I've noticed for instance that any snow veto on steep slopes which looks realistic in the French Alps custom scenery doesn't do anything in the Rocky Mountains default scenery. I guess same with trees - in order to get the visual comparison of Canaima or Yosemite with photographs right, I had to go to 30/45 instead. The wateralls have the same issue - since the slope is always underestimated, one has to throw them really far into the air to make them fall all the way down... So, I would maybe suggest to think about changing the defaults to 30/45, study a few more test cases and if someone wants to have different values in custom scenery he can use a regional definition to do that. I know it's technically not correct, but I think correcting for some systematic flaws in our scenery is a valid goal. * Thorsten -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Postgres/Postgis import apt.dat
Hi all I already wrote a small baby python script which converts apt.dat into flightgear readable xml. Now I started a new project for importing the same data to Postgres/PostGIS tables for my map development. Currently I can create runway polygons with all associated data this way with (flightgear future version) apt.dat 1000. But it will work with apt.dat 850 too I guess, only 810 is out of scope now. I decided to write an own import script using geographiclib and psycopg2. My current dev map is based on postgres 9.1.5/PostGIS 2.0.1/mapnik 2.1 and tilecache 2.11, and still under development. We plan to use it as base for a new multiplayer map proposal, and a new FGx inline map of course. If someone can give me the database structure needed for official flightgear scenery map meantime, or better, help to improve the script to fit flightgear database needs I guess this scripts could replace the former ogr2ogr driver import (which I guess is not followed anymore, but just a guess). If you’re familiar with python, sql and PostGIS you’re welcomed anytime to help to improve the scripts. First tests of the runways geometry created looks very good, albeit you will discover issues of apt.dat immediately on a current map, or maybe also issues of OSM or google maps, yes ;-) -Yves -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: Request for file removal: Dassault Rafale B
From: Fabrice Kauffmann Sent: Wednesday, October 10, 2012 2:30 PM To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Fwd: Request for file removal: Dassault Rafale B Dear Dev Team, Dassault Aviation has recently forbidden the diffusion of some freeware and commercial addons for various flight simulators. The Rafale logo and the shape of the Rafale fighter are copyrighted from Dassault Aviation and cannot be diffused without the authorization of their owner. Therefore, in order to avoid any potential legal issue, I kindly ask you to remove my Rafale from your repositories. The files to be removed are the following: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Aircraft-2.8/RafaleB_20101025.zip ftp://ftp.kingmont.com/flightsims/flightgear/Aircraft-2.8/RafaleB_20101025.zip ftp://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Aircraft-2.8/RafaleB_20101025.zip Thanks in advance for your support, F. Kauffmann Is this relevant (from http://www.mirage4fs.com/news_12.html ) to this issue ? 25 March 2012 - To avoid any trouble from Dassault Aviation related to copyright Bruno Mérelle and the Force Aerienne Virtuelle France website had removed his Rafale for FSX from their download pages earlier this year. The file has now been made available again. Alan -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New materials.xml elements to control object/tree density depending on slope angle
On Wed, Oct 10, 2012 at 7:28 AM, Renk Thorsten wrote: played around with this a bit yesterday... *very* nice feature! Glad you like it. In retrospect it seems and obvious function to have, and it works particularly well with some of the angle-dependent rock shaders. So, I would maybe suggest to think about changing the defaults to 30/45, study a few more test cases and if someone wants to have different values in custom scenery he can use a regional definition to do that. I know it's technically not correct, but I think correcting for some systematic flaws in our scenery is a valid goal. I've made this change for the moment. We can change it at any point up to the release without backwards-compatibility issues. -Stuart -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Patch: FOV automatic compensation for wider screens
On Tue, Oct 9, 2012 at 3:28 PM, Stuart Buchanan wrote: The proposal is to merge the Display Options and View Options dialog, leaving the Rendering Options dialog alone. This has now been done. Comments welcome as always. -Stuart -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] In-sim selection of materials.xml file - what to call DDS?
On Wed, Oct 10, 2012 at 7:20 AM, Renk Thorsten wrote: The reason I didn't just label it material definitions was that I don't think that a new user is going to understand what that means, while the concept of different textures should be familiar to people who have some background in graphics, or gaming. I'd go for something like 'terrain texture scheme'. For anything else, you really have to understand what the role of materials.xml in Flightgear is. The people who do understand can overlook an incomplete label, the people who don't will primarily notice changed textures. Why not use 'Global alternative scheme (dds format)' or something like that - I think the info that this is based on dds is relevant for those who can't actually display dds properly, but it doesn't need to be overemphasized. I've gone with Terrain texture scheme for the label, and Global alternative (DDS format) for the name of the dds/materials.xml. Thanks for the suggestion. -Stuart -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
