Can anyone tell me why this works:/home/jkoppe/fgfs-aircraft/Wright-ex/Models/Wright-EX-1911.xmlYet this always produces "Incorrect path specified in configuration file":true/home/jkoppe/fgfs-aircraft/Wright-ex/Sounds/Wright-EX-1911-sound.xmlThe directory structure is there, everything is spelled correctly. Permission on folders are rwxr-xr-x. Permissions on the files are rw-r--r--I'm stumped.Thanks,--jeffhttp://www.static-lift.net/aero-club/main/home.html

> > /home/jkoppe/fgfs-aircraft/Wright-ex/Models/Wright-EX-1911.xml> This doesn't work, because "absolute" paths in fgfs are always relative to $FG_ROOT. Something like this, however, works: ../../../../home/jkoppe/foo.xmlOf course, you may have to use more or less instances of "../", depending on where your $FG_ROOT is.

Thanks for the response.I'd believe it except for the fact that the path for the model DOES work. But the path for the sound does not. So I'm kinda thinkin' that fgfs understands a starting "/" for the model path as an absolute path. Yet it always tries to navigate the sound path as relative to FG_ROOT. At least that's the only explanation I can come up with without delving into the code. I was hoping someone had already looked at that but it doesn't appear that they have. (Well, none of us poor lonely forumites, anyway.) Hi Ho, Hi Ho, it's off to code I go...--jeff

Whoops ... well, then let me rephrase: It *should* not work. ;-) So this is then only true for some paths!? Anyway, the best way to do it, is probably, to create a link from $FG_ROOT/Aircraft/your_aircraft to whereever you want to develop your aircraft in $HOME.

Thanks for the link suggestion. That is indeed a better way to handle it. Not only does it circumvent the inconsistent path handling, but perhaps more importantly, the -set.xml file won't need to be edited when I release this plane to the general public.BTW, I've added a couple of tidbits to my FGFS website and given you the credit for them. ;-)--jeffhttp://www.static-lift.net/aero-club/main/home.html