|
From: Rebecca N. P. <reb...@zo...> - 2015-07-25 12:52:03
|
> 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/Custom/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). > 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. 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 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. An alternative fix for this problem would be to replace /sim/terrasync-dir with something stored outside the property tree (i.e. out of Nasal's reach). |