Re: [Flightgear-devel] DHC-6 progress
On Fri, Sep 09, 2005 at 10:07:43PM +0200, [EMAIL PROTECTED] wrote: Problems: - blender has problems with flipping normals to the outside of the model automaticaly, so i had to do that by hand. It is likely that I overlooked a surface or two... That's not a problem, but a feature. Really. After mirroring an object you have to 'apply the rotation'. (Some key combination with a, IIRC. Ctrl-A?) I don't know why this isn't done automatically, but it is braindamage 'by design'. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] DHC-6 progress
On Saturday 10 September 2005 08:32, Melchior FRANZ wrote: Problems: - blender has problems with flipping normals to the outside of the model automaticaly, so i had to do that by hand. It is likely that I overlooked a surface or two... That's not a problem, but a feature. Really. After mirroring an object you have to 'apply the rotation'. (Some key combination with a, IIRC. Ctrl-A?) I don't know why this isn't done automatically, but it is braindamage 'by design'. sorry, meant to say, that the recalculate normals outside-fuction doesn't work very well. It works with simpler models but somehow it kind of overlooked some faces so i had to fix those by hand... cheers Thorben ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] DHC-6 progress
[EMAIL PROTECTED] wrote: Erik: I tried to use your jsbsim FDM frist, but I was too stupid to get that to work... It's hard to believe that. Maybe you're too inexperienced. I'll take a look at it today and send you the required updates. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
Dave Martin wrote: On Friday 09 September 2005 18:36, Jon Stockill wrote: I've just finished downloading and processing all the data to get my scenery build system back up and running after a disk crash, it's building tiles for a test of the OSM roads at the moment. I'll grab some screenshots when it's done. I look forward to seeing that. Here's a couple of pics, the first is looking west over the gherkin, and the second is looking out over regents park. Generation time was over an hour for that tile on a 1GHz athlon (the resource limits in fgfs-construct needed a significant increase). Memory usage was ok at around 140MB. http://flightgear.stockill.org.uk/scenery/osmroads1.jpg http://flightgear.stockill.org.uk/scenery/osmroads2.jpg It shows up a few limitations in the source data. The road segments are currently all represented seperately and not tied into a road object, this results in lots of short roads, and visible breaks on the outside of corners. This will improve as the open streetmap system matures (it's still very early days). Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
Hi, Jon Stockill schrieb: [SNIP] Here's a couple of pics, the first is looking west over the gherkin, and the second is looking out over regents park. Generation time was over an hour for that tile on a 1GHz athlon (the resource limits in fgfs-construct needed a significant increase). Memory usage was ok at around 140MB. http://flightgear.stockill.org.uk/scenery/osmroads1.jpg http://flightgear.stockill.org.uk/scenery/osmroads2.jpg This looks quite detailed. I'm not that familiar with the London area so would you say that there is a considerable amount of smaller streets missing in there? Even with not so much detailed streets - i.e., leaving all the back-streets out and having only freeways and mainstreets processed - the generation of scenery takes substantially longer than for the standard data. I have no numbers on this, but having to raise the resource limits in fgfs-construct considerably is quite a good indication. One other problem that'll probably become more serious with more detailed street-data is that the comparatively small streets not only produce lots of small triangles on the streets themselves but also raise the number of triangles on neighbouring polygons by splitting them. (Currently fgsd crashes on loading some of the more full tiles - possibly because of the sheer number of triangles; I will investigate further on that when I get the time) I currently do not have any solution for that and I know that there have been discussions before, but perhaps having more detailed scenery now may be a good reason for the experts here to reconsider this topic. It shows up a few limitations in the source data. The road segments are currently all represented seperately and not tied into a road object, this results in lots of short roads, and visible breaks on the outside of corners. This will improve as the open streetmap system matures (it's still very early days). This may be solvable by automatically snapping endpoints and recombining shorter segments into longer segments. Anyway recombination will only partially solve the problem, as on an intersection only pairs of participating line-segments can be joined. Perhaps we need a better way of making polygons from lines, much like the v.buffer operation of GRASS (http://grass.itc.it/grass61/manuals/html61_user/v.buffer.html). Regards, Ralf ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
Ralf Gerlich wrote: This looks quite detailed. I'm not that familiar with the London area so would you say that there is a considerable amount of smaller streets missing in there? You can see the source data here: http://www.openstreetmap.org/ there are roads missing, simply because the map is not yet complete, nor are they categorised. Once there's some more data, the segments are correctly joined into roads, and the roads are classified then we can be more selective about the roads we include in the scenery. Even with not so much detailed streets - i.e., leaving all the back-streets out and having only freeways and mainstreets processed - the generation of scenery takes substantially longer than for the standard data. I have no numbers on this, but having to raise the resource limits in fgfs-construct considerably is quite a good indication. Yes, the cpu limit was set as 120 seconds - I increased it to an hour and *still* had failures, so it's now set at 4 hours here just to be safe. One other problem that'll probably become more serious with more detailed street-data is that the comparatively small streets not only produce lots of small triangles on the streets themselves but also raise the number of triangles on neighbouring polygons by splitting them. (Currently fgsd crashes on loading some of the more full tiles - possibly because of the sheer number of triangles; I will investigate further on that when I get the time) I've not had that problem yet, but so far the data only covers a relatively small area. I currently do not have any solution for that and I know that there have been discussions before, but perhaps having more detailed scenery now may be a good reason for the experts here to reconsider this topic. We've just been discussing another problem on irc - the green texture isn't really appropriate for a city, but I left out the city areas since the texture it uses contains its own roads. I'm not really sure of a solution to this. This may be solvable by automatically snapping endpoints and recombining shorter segments into longer segments. It will be solved in future versions of the openstreetmap data - at the moment it just exports as lots of short roads with a start and end point, eventually these will be chained together to form longer roads. Anyway recombination will only partially solve the problem, as on an intersection only pairs of participating line-segments can be joined. Perhaps we need a better way of making polygons from lines, much like the v.buffer operation of GRASS (http://grass.itc.it/grass61/manuals/html61_user/v.buffer.html). At the moment I'l just converting the exported openstreetmap data to the tguserdef format, which I suspect is less than ideal. It may be worth having something that will be a bit more intelligent, and resolve some of these problems as it parses the data. Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
On Saturday 10 September 2005 10:25, Jon Stockill wrote: Here's a couple of pics, the first is looking west over the gherkin, and the second is looking out over regents park. Generation time was over an hour for that tile on a 1GHz athlon (the resource limits in fgfs-construct needed a significant increase). Memory usage was ok at around 140MB. http://flightgear.stockill.org.uk/scenery/osmroads1.jpg http://flightgear.stockill.org.uk/scenery/osmroads2.jpg It shows up a few limitations in the source data. The road segments are currently all represented seperately and not tied into a road object, this results in lots of short roads, and visible breaks on the outside of corners. This will improve as the open streetmap system matures (it's still very early days). Jon That's really impressive Jon! I have a feeling as we get more road data, we're going to be seeing slight placement errors at the airports. Currently EGBB is placed over the A45 on the 0.9.8 scenery. If I can get that road mapped by GPS and a few others around it, we can probably move the airport to its correct location. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
Dave Martin writes: I have a feeling as we get more road data, we're going to be seeing slight placement errors at the airports. Currently EGBB is placed over the A45 on the 0.9.8 scenery. If I can get that road mapped by GPS and a few others around it, we can probably move the airport to its correct location. EGBB is spot-on in it's placement - the vmap0 road data is far worse. If you map the road with GPS around the airport it will sort the problem there. Cheers - Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
On Saturday 10 September 2005 13:19, Dave Martin wrote: I have a feeling as we get more road data, we're going to be seeing slight placement errors at the airports. Currently EGBB is placed over the A45 on the 0.9.8 scenery. If I can get that road mapped by GPS and a few others around it, we can probably move the airport to its correct location. I noticed that a lot of airports in the X-Plane DB are quite far out. Even some major airports like Sion were out by ~ 3 km. What I do find interesting is that the quality of the data seems to change for every country. South Eastern France's data was horrid, so was Switzerland's however Italy's data was almost spot on more than 90% of the time. Maybe someone corrected the data for Italy already or maybe it came from a different source. Also it appears that a lot of the data was pure guess work in a lot of cases. I saw plenty of runways that were more than 20 degrees out, runways that were more than 50% too short, wrong runway id's, wrong surface types, etc. Ever seen a military airport with a single 500m long grass runway that they use for F18's, Mirages, etc? :) Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
Paul Surgeon wrote: I noticed that a lot of airports in the X-Plane DB are quite far out. Even some major airports like Sion were out by ~ 3 km. What I do find interesting is that the quality of the data seems to change for every country. South Eastern France's data was horrid, so was Switzerland's however Italy's data was almost spot on more than 90% of the time. Maybe someone corrected the data for Italy already or maybe it came from a different source. Also it appears that a lot of the data was pure guess work in a lot of cases. I saw plenty of runways that were more than 20 degrees out, runways that were more than 50% too short, wrong runway id's, wrong surface types, etc. Ever seen a military airport with a single 500m long grass runway that they use for F18's, Mirages, etc? :) My understanding is that for the USA, the X-Plane data for runways comes primarily from DAFIF. Taxiways are all hand drawn and placed. Outside the USA the runway data is manually generated by anyone who wants to submit new airports, so quality and accuracy is all over the map. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover
Jon Stockill wrote: http://flightgear.stockill.org.uk/scenery/osmroads1.jpg http://flightgear.stockill.org.uk/scenery/osmroads2.jpg Herewith I appoint you to the future maintainer of OSM-data in our kindcover database :-) Do they log the changes in their database, do they offer any 'raw' interface ? This would make it easier for us to track the development of their dataset. Do they differenciate between different sized roads ? To be honest I don't expect importing a bulk of tiny roads into our PostGIS-DB to be our primary goal. They are nice to have for those of us who operate on powerful hardware but the small roads probably won't make it into the default scenery. We should stuff everything into our database that we are able to 'classify' in a reasonable way (small, medium, large, ) and let everyone decide which data (s)he wants to use for his/her scenery. I just read that the current release 0.7 of QGIS is able to render directly into a PostGIS database - this might help a lot. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover
Martin Spott wrote: Herewith I appoint you to the future maintainer of OSM-data in our kindcover database :-) I should have kept my mouth shut :-) Do they log the changes in their database, do they offer any 'raw' interface ? The interface is explained here: http://www.openstreetmap.org/wiki/index.php/REST I used the map command to dump the data, then converted it to the tguserdef format in order to build the scenery, but a shapefile could just as easily be used as the intermediate format. This would make it easier for us to track the development of their dataset. Do they differenciate between different sized roads ? Not yet, although the intention is to have a key/value system which will allow the tagging of road types, names, numbers, etc. So the classifications will be available. Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover
Martin Spott wrote: Herewith I appoint you to the future maintainer of OSM-data in our kindcover database :-) 'landcover' I can't tell how this could happen Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover
Jon Stockill wrote: I used the map command to dump the data, then converted it to the tguserdef format in order to build the scenery, but a shapefile could just as easily be used as the intermediate format. We have to be careful about simply dropping a shapefile into our landcover database. Wenever we add a road, river or some other data to the database we'll have to have a look if the respective object is already represented there. For example if you derive a road course from the OSM collection with the intention to add it to the landcover DB the respective road might already be present there - although likely at the wrong location. Now you have to make sure to remove the 'old' road. I expect this process to be fairly easy with a GIS tool that interfaces cleanly with such a GIS database as PostGIS because with such a tool you can identify a _single_ object and remove it from the layer. For other tools that can't interface directly we are building sort of a batch interface: You could create a shapefile for a specific layer and define a bounding box around your data. Now as you are going to drop this data into the landcover DB we have to expect that your shapefile contains _all_ data that belongs to the area inside the bounding box: Not only your addition but also the data that has already been there before - preferrably together with appropriate junctions between old and new data. I know that this method puts us at risk to cut single roads and/or rivers into pieces and I would not reject clever ideas on how to circumvent this risk ;-) The same applies to corrections of the shoreline, city outlines, lakes or whatever you could think of. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
On Saturday 10 September 2005 15:28, Curtis L. Olson wrote: My understanding is that for the USA, the X-Plane data for runways comes primarily from DAFIF. Taxiways are all hand drawn and placed. Outside the USA the runway data is manually generated by anyone who wants to submit new airports, so quality and accuracy is all over the map. Oh! I never knew that. I thought DAFIF was a global database. That explains it then. Hehe ... I like your pun. (accuracy is all over the map) Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: DHC-6 progress
Hi Thorben, as I like this little island-hopper aircraft very much I immediately flew it in the sim. Very nice, indeed. As it is a work in progress it would be fine if you could have a look at the size of the wheels, especially the front-wheel, and the related steering structure. The model would look a lot more realistic if you could make it much smaller as this is a very important first look element of the original aircraft. Anyway, I thank you very much for developing this wonderful sim-aircraft. Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Simgear-cvslogs] CVS: SimGear/simgear/screen RenderTexture.cpp, 1.9, 1.10
On September 6, 2005 02:33 pm, Mathias Fröhlich wrote: Yay! This brought back 3D-clouds which I've been missing for a long time (using XFree86 4.3 + ATI's proprietary driver for Mobility Radeon 9600) :-) Good to hear ... Thanks Mathias Unfortunately, 3D clouds is still not working over here. I am still getting the RenderTexture Error: Couldn't find a suitable pixel format message everytime I start FlightGear. I am using ATI Radeon 9200 SE PCI version with the opensource driver from XFree. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
On September 10, 2005 09:28 am, Curtis L. Olson wrote: My understanding is that for the USA, the X-Plane data for runways comes primarily from DAFIF. Taxiways are all hand drawn and placed. Outside the USA the runway data is manually generated by anyone who wants to submit new airports, so quality and accuracy is all over the map. Curt. Google has some pretty accurate taxiways for their map. Check out http://pigeond.net/flightgear/fg_server_map.html in map mode. Does anybody where Google got their data from? Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] DHC-6 progress
Melchior FRANZ wrote: That's not a problem, but a feature. Really. After mirroring an object you have to 'apply the rotation'. (Some key combination with a, IIRC. Ctrl-A?) I don't know why this isn't done automatically, but it is braindamage 'by design'. It's hard to fix. When you mirror a mesh, the winding order of all the polygons gets reversed, which means their normals change direction. If the mesh is stored in an optimized format (strips, fans, etc...) then it needs to be broken down and re-optimized. Big mess. It's not something that blender can't or shouldn't handle, but it *does* interact in weird ways with the geometry representation. I sympathize. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
Hi, Ampere K. Hardraade schrieb: Google has some pretty accurate taxiways for their map. Check out http://pigeond.net/flightgear/fg_server_map.html in map mode. Does anybody where Google got their data from? You can get quite detailed aerial photos for most urban areas in the USA from http://www.terraserver-usa.com David Luff's TaxiDraw has support for automatically loading such photos and showing them in the editor. However, I'm still searching for free detailed aerial photos for other areas of the world such as Germany. Here the government wants you to pay twice for the photos: Once via tax and once when you want to use the photos. The license under which you get those photos here is quite limited as well. Regards, Ralf ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover
Ralf Gerlich wrote: However, I'm still searching for free detailed aerial photos for other areas of the world such as Germany. Here the government wants you to pay twice for the photos: Once via tax and once when you want to use the photos. The license under which you get those photos here is quite limited as well. Google maps might be of help in this case as well. The photo is not _that_ accurate but good enough to get the location - EDLN for example: http://maps.google.com/maps?ll=51.230356,6.504496spn=0.042828,0.058627t=h Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] DHC-6 progress
On Saturday 10 September 2005 18:42, Andy Ross wrote: It's hard to fix. When you mirror a mesh, the winding order of all the polygons gets reversed, which means their normals change direction. If the mesh is stored in an optimized format (strips, fans, etc...) then it needs to be broken down and re-optimized. Big mess. It's not something that blender can't or shouldn't handle, but it *does* interact in weird ways with the geometry representation. I sympathize. Isn't that where the flip normals feature comes in handy? I don't remember having any problems when I mirrored meshes in Blender for use in FG but it was a while ago. Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
On Saturday 10 September 2005 19:03, Ralf Gerlich wrote: However, I'm still searching for free detailed aerial photos for other areas of the world such as Germany. Here the government wants you to pay twice for the photos: Once via tax and once when you want to use the photos. The license under which you get those photos here is quite limited as well. That's a normal practice outside of North America. Don't you just love government surveyors. :-\ Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
On September 10, 2005 06:36 am, Jon Stockill wrote: We've just been discussing another problem on irc - the green texture isn't really appropriate for a city, but I left out the city areas since the texture it uses contains its own roads. I'm not really sure of a solution to this. Personally, I think green is fine in the near term. When more models are loaded for a city, the city would not appear to be so green. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
On September 10, 2005 01:03 pm, Ralf Gerlich wrote: You can get quite detailed aerial photos for most urban areas in the USA from http://www.terraserver-usa.com David Luff's TaxiDraw has support for automatically loading such photos and showing them in the editor. However, I'm still searching for free detailed aerial photos for other areas of the world such as Germany. Here the government wants you to pay twice for the photos: Once via tax and once when you want to use the photos. The license under which you get those photos here is quite limited as well. Regards, Ralf I think you misunderstood. I was referring to the taxiways under map mode, not satellite mode. If you go in map mode, you will see that Google got some pretty accurate vector data for taxiways generation. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: DHC-6 progress
Erik: would be glad to add the jsbsim FDM. My own attempts to get it to work got as far as flightgear sucessfully loading the plane but the engines didn't seem to run and I couldn't change that even in the internal property browser... Andy/Paul: well, do I get you right, I should flip the normals outside straight away when mirroring a mesh? On Saturday 10 September 2005 18:12, Georg Vollnhals wrote: As it is a work in progress it would be fine if you could have a look at the size of the wheels, especially the front-wheel, and the related steering structure. The model would look a lot more realistic if you could make it much smaller as this is a very important first look element of the original aircraft. When I made those wheels, i also thought: this 3view must be wrong, those are much to big, but have a look here: http://thorben-mit-th.de/files/comparison.jpg Although, I agree, that the gear still needs some work, also some stuff needs to be tweaked, like the angle of the rudder... Hmm, by the way, DHC-6-300 doesn't look that bad either, perhaps I will have a shot on it when I'm in the right mood. I have adjusted the FDM to have a higher ascend rate, I am too lazy to upload a new FDM but if you want to have more power change 'cruise-speed=200' in BOTH PROPELLER sections to 'cruise-speed=150'. In the next few days I will be quite busy with moving to the city where I will go to university, so don't worry if I don't keep you updated daily ;-) REMINDER: I still need all usefull data you come across on dhc-6 and some hints how to do a proper livery... I won't say No if someone (Gabor perhaps) had the mercy to do this work for me... I am neither that skilled in painting or drawing nor have much fun doing so. Georg EDDW Thorben EDVY (in advanced training for PPL-C) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Lufthansa liveries
On Thursday 08 September 2005 23:03, Gabor Toth wrote: Hi, I've created some new textures for B737, B747, A320. They can be found at http://www.i-net.hu/fgfs Please feel free to use them for your own sake, or if they worth, please put them into CVS. Regards, Gabor No one gave you credit for your great work... I wonder why, because it IS great. I have told you so via IRC, but perhaps this is a better way to do it! I encourage you to keep up that kind of stuff and perhaps have a look at other existing liveries that need improving! (Not necessarily thinking about my Twin Otter here, but wouldn't say No ;-)) I also would like to know exactly how you did that... Thorben ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
Hi, Ampere K. Hardraade schrieb: I think you misunderstood. I was referring to the taxiways under map mode, not satellite mode. If you go in map mode, you will see that Google got some pretty accurate vector data for taxiways generation. Whoop, didn't see that. In that case: Yes, I misunderstood and join your inquiry ;-) Ralf ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Lufthansa liveries
On September 10, 2005 02:42 pm, [EMAIL PROTECTED] wrote: No one gave you credit for your great work... I wonder why, because it IS great. I have told you so via IRC, but perhaps this is a better way to do it! I encourage you to keep up that kind of stuff and perhaps have a look at other existing liveries that need improving! (Not necessarily thinking about my Twin Otter here, but wouldn't say No ;-)) I also would like to know exactly how you did that... Thorben Well, I haven't seen the liveries so I cannot say. However, from the screenshots, the liveries look pretty good. The method that is used to allow multiple livery needs to be done properly though by making use of the texture-path tags. Some modifications to the XML's is suffice to allow multiple livery. Duplicated model is not needed. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover
On Saturday 10 September 2005 15:39, Martin Spott wrote: We have to be careful about simply dropping a shapefile into our landcover database. Wenever we add a road, river or some other data to the database we'll have to have a look if the respective object is already represented there. Is it possibly to remove the existing shapefile for a certain area from the landcover DB? Perhaps the UK landcover generated by Jon via openstreetmap.org could be kept seperately until more or less complete and then used to generate UK scenery. Interestingly, I did a bit of poking around the openstreetmap documentation and it does actually provide for defining areas such as woodland/built-up/lakes etc. Further to this amateur cartography, it might be interesting to try to start a 'community' of people in the UK who can use a GPS to map their local area - maybe 150 or so 'adventurous' cartographers could get the majority of the UK's road layout done in a year or so (being a small island ;) ) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database export
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ampere K. Hardraade schrieb: On September 10, 2005 09:28 am, Curtis L. Olson wrote: My understanding is that for the USA, the X-Plane data for runways comes primarily from DAFIF. Taxiways are all hand drawn and placed. Outside the USA the runway data is manually generated by anyone who wants to submit new airports, so quality and accuracy is all over the map. Curt. Google has some pretty accurate taxiways for their map. Check out http://pigeond.net/flightgear/fg_server_map.html in map mode. Hey, that's a cool application of Google Maps! Does anybody where Google got their data from? Didn't they get the data when they bought keyhole (or so)? (The company Google Earth was original from) CU, Chrisitan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFDI1CmlhWtxOxWNFcRAj41AJ4x6mLE3/xvlpSVgK5ZqXljetwRgQCdFJyh DTpPHcnPeP24FD5ZaYjRMSQ= =Gecy -END PGP SIGNATURE- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
