|
From: Dirk D. <dir...@gm...> - 2015-07-25 16:31:06
|
Am Samstag, 25. Juli 2015, 13:49:53 schrieb Rebecca N. Palmer: > > I had a look at it, is it possible to get the path into FG via a command > > line option ~ "--fg-AllowedPath=" > > --fg-aircraft=/home/dirk/.fgfs/Custom/Aircraft/enabled:/home/dirk/.fgfs/Cust > om/Aircraft/available:<your Nasal script directory> will do that, but I > don't know which folder name the aircraft will get loaded from (it > *doesn't* appear to be determined by the order they are given in). thanks for your help it works. --fg-aircraft=<your Nasal script directory> for every directory and the scripts as a link into ./fgfs/Nasal for every aircraft the same --fg-aircraft=<link to aircraft> I will do a loop into my start-script to create that for all my linked aircrafts. > > > If i cloned TheOmegaHangar A330-300 the folder is called > > "/home/dirk/.fgfs/Custom/Aircraft/avialable/airbus-a330-300-main/" > > this folder name doesn't work. https://gitorious.org/fg-airbus-a333/airbus-a330-300-main.git seams closed :-( > > That looks like a bug: what error message (if any) do you get? Where > can I find this aircraft to test for myself? > > > Other example custom scenery. > > > > Motorcycle-fg-CustomScenery it has an Nasal folder and the files have to > > go > > into .fgfs/Nasal https://github.com/D-MKF1/Motorcycle-fg-CustomScenery > > Nasal reading fg-scenery was disabled because it was the easiest way to > fix the "Nasal can read any file by changing /sim/terrasync-dir" > security hole (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780716) > and we thought nobody was using it. I linked the scripts into ./fgfs/Nasal so in my userspace to make it work. with this option it works now --fg-aircraft=/home/dirk/.fgfs/Custom/Scenery/Motorcycle-fg- CustomScenery/Nasal/ Thanks again for your help Best Regards Dirk |