On 23 October 2004 21:22 Roy Vegard Ovesen wrote: > On Saturday 23 October 2004 21:14, Vivian Meazza wrote: > > I've finally found time to revisit this problem. > > > > The FGFS is working fine with updates up to 15th Oct. Paths, etc. are > good. > > > > I've updated and recompiled Simgear and Flightgear. Nothing else has > been > > changed. Should work, right? > > > > Wrong: I get the following errors using the default aircraft: > > > > Object PanelInstruments not found > > Object ControlsGroup not found > > I also get these now and then. > > > No instrumentation model specified for this model! > > > > I also get this: > > > > General Initialization > > ======= ============== > > FG_ROOT = "/FlightGear-cvs/data" > > > > Which is correct. > > > > The menu bar has also disappeared, so it would seem likely that the > correct > > path is not being found. > >
Problem solved, well not solved, more understood. Despite showing the path as: General Initialization ======= ============== FG_ROOT = "/FlightGear-cvs/data" In fact, fgfs is reading the old preferences.xml file in the path specified in fgfs.exe. That looks like a bug in the initialization process to me. This does not happen using fgrun under windows, which reads the correct preferences.xml. That led me down the wrong path yesterday. The menu bar re-appeared this morning, without my having done anything. I suppose recycling the power supply (aka switching off) did the trick. However, it enabled me to identify the problem very quickly. The fix is simple - put the new preferences.xml file in the 'wrong' path. A nuisance though, since it means that it is not trivial to go back before 15th Oct cvs for testing purposes. I don't know if it's worth any effort on tracing and fixing the bug, or just living with it. As usual, thank you for your help. Regards, Vivian _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
