20,741
edits
No edit summary |
|||
| Line 73: | Line 73: | ||
* '''TheTom''': "I'm currently thinking about how to unify the canvas placement system to allow for easy placements in the different parts (gui, aircraft, scenery) and also seamless interchangeability between them. (Eg. show the contents of a MFD in a window)" | * '''TheTom''': "I'm currently thinking about how to unify the canvas placement system to allow for easy placements in the different parts (gui, aircraft, scenery) and also seamless interchangeability between them. (Eg. show the contents of a MFD in a window)" | ||
* '''Hooray''': "Placement-wise, it would obviously be cool to directly support geographic coordinates for placing textures - placing runway skids would then be pretty simple to accomplish actually, i.e. for each touchdown point (gear locations) continously get the terrain position and place the skid marks on the asphalt. Yes, the VDGS seems like another good candidate here - ideally, these would be 3D models with a canvas texture and some Nasal code loaded from a model.xml file (supported already)." | * '''Hooray''': "Placement-wise, it would obviously be cool to directly support geographic coordinates for placing textures - placing runway skids would then be pretty simple to accomplish actually, i.e. for each touchdown point (gear locations) continously get the terrain position and place the skid marks on the asphalt. Yes, the VDGS seems like another good candidate here - ideally, these would be 3D models with a canvas texture and some Nasal code loaded from a model.xml file (supported already)." | ||
Also see: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15464.html | |||
=== Depth Sorting {{Pending}} === | === Depth Sorting {{Pending}} === | ||