Hi,
> On 16 Jan 2011, at 13:41, Martin Spott wrote: > > > I know we've already been talking about this topic but > I don't remember > > all the details. To me it looks like either a) > the animation are > > depending a little bit too much on textual path names > or b) FlighGear > > doesn't provide a reasonable variable as a substitute > for the > > respective directory path which you're > referencing. Or both. > > I've done work in this area to support multiple aircraft > dirs, if one of you could give a clear description of what's > going wrong, I might be able to help. > > Regards, > James Grab: http://www.hoerbird.net/LOWI.zip install it as it is and try. The pads are working. Now save the Objects-folder from the package in terrasync, and delete e010n40-folder in data/Scenery. Use now the terrasync-folder as scenery. It won't work. Problem: to use the pads inside the Objects/e010n40/e011n47-folder I defined a line in the nasal-script like that: setprop ("models/LOWI/model/path", "Scenery/Objects/e010n40/e011n47/LOJO_helipad_libelle.xml"); This path seems to be absolute. If you want to make this working in TerraSync you have to change the line to ..","terrasync/Objects/..."); That's prevents me from uploading my wok on the moveable helipads (currently a FlightGear-only feature!) to GIT. The other way to get it working is to use a set of standard pads lying in Models, but that would mean of course less freedom to heli-scenery-designer. Any ideas? Heiko ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
