I downloaded the b777 but on the command prompt it says: Unknown exception in the main loop. Aborting... the aborts Flightgear. so I cant use the b777 does anyone know what might be wrong?

>I downloaded the b777 but on the command prompt it says:>Unknown exception in the main loop. Aborting... the aborts>Flightgear. so I cant use the b777 does anyone know what might>be wrong?given the lack of details/information, nobody can really KNOW what might be wrong-so, whatever reply we would come up with, would be purely based on lots of guesses and assumptions, which are unlikely to be really helpful. Thus, you may want to check out the troubleshooting section at http://wiki.flightgear.org in order to get an impression about what sort of information should usually be minimally provided in order to enable other people to try to help you.

>>I downloaded the b777 but on the command prompt it says:>>Unknown exception in the main loop. Aborting... the aborts>>Flightgear. so I cant use the b777 does anyone know what>might>>be wrong?>>given the lack of details/information, nobody can really KNOW>what might be wrong-so, whatever reply we would come up with,>would be purely based on lots of guesses and assumptions,>which are unlikely to be really helpful. Thus, you may want to>check out the troubleshooting section at>http://wiki.flightgear.org in order to get an impression about>what sort of information should usually be minimally provided>in order to enable other people to try to help you.>Okay I noticed in the command prompt that there seemed to be a missing file titled C:Program Files/Flightgear/data//models/fgfsdb/localizer.xmlIt said it failed to open that file. Is there somewhere I could find that file so I could put it into the models file?

>Okay I noticed in the command prompt that there seemed to be a>missing file titled C:Program Files/Flightgear/data//models/fgfsdb/localizer.xml>It said it failed to open that file. While I am admittedly not 100% sure whether the following is entirely correct, I'm pretty sure that what you are seeing should normally not be related to the missing file, which in this case would actually seem to be related to the scenery in general and not the aircraft in particular. Thus, IF the file is really missing and is referenced in the corresponding scenery tile for your particular starting position, you should get the same console message regardless of the (type of) aircraft you are using (provided otherwise identical startup settings). >Is there somewhere I could find that file so I could put it into the models file?Usually, the scenery database would be the right place to look for such stuff: http://fgfsdb.stockill.orgHowever, if you are using a pristine FG install without any additional scenery tiles or custom objects (or other customizations), everything should be working out of the box, if it doesn't then you may want to consider re-installing the base package because it may -for whatever reason- be "broken".On the other hand, it is really an excellent idea to try to provide the information as referenced on the corresponding wiki pages, as this would answer several key questions and enable us to get a basic understanding of your setup/platform, startup & runtime settings.Until you've provided this very information, it may turn out very hard or even impossible for us to come up with a proper analysis and diagnosis for your specific problem without relying on lots of assumptions (i.e. what you are seeing may easily occur when non-matching versions of the fgfs executable and base package (or aircraft) are used together).If you have modified anything within the base package, you could also try to exclude these modifications as the potential source of your problem by extracting a fresh copy of the base package to a new directory and use this together with FlightGear in order to see whether the problem still persists or not.