![flightgear scenery not loading flightgear scenery not loading](https://wiki.flightgear.org/w/images/9/92/Worldscenery-text.jpg)
Also, most modern multi-user operating systems feature support for file permissions, so that files and paths need to have the proper permissions set in order to be accessible.On most modern operating systems, filenames and paths are indeed case sensitive, so make sure to watch out for this, as well.watch out for whitespaces, separators and case: When referencing file names or paths, make sure that they're used properly i.e.When referencing file names or paths, always make sure that files and paths actually do exist.However, once you do modify the base package, it is important to keep track of your changes and to make sure that files are modified properly. Many interesting modifications can be done by editing base package resources, such as for example aircraft files, instrumentation files, GUI files, Nasal scripts etc. Possible pitfalls when modifying base package filesĪt some point, most users will probably want to modify FlightGear in some way or another. Try Requesting Technical Help, but only after trying the other suggestions above! If you have control device issues (keyboard, joystick.) see Troubleshooting input devices.Ĭheck out Hardware Recommendations for more information about video cards and other hardware that has been reported to work with FlightGear.If the whole system is crashing when running FlightGear, please read System Crashes.If FlightGear is crashing, please see Troubleshooting crashes.the black window), see Howto:Understand console output. If you're getting errors in the console (i.e.If you're having graphics problems, please check the list of Problematic Video Cards and Troubleshooting graphics artifacts.If FlightGear runs slowly, please see Troubleshooting performance issues and Howto:Use the system monitor.To rule out some of the most common problems, see Frequently asked questions#Problems.3 Possible pitfalls when modifying base package files.If you can't reach the url, then the problem is not FG or version 3.4. A browser is good enough, either your computer can reach the site or not. Via an external source instead of trying to use FG. You may also want to check that you have access to said URL (the one PINTO posted in the command) I'm trying to help, but I do not think installing 3.4 again is the issue here. It's very hard for proper support from me using a version I never used in my life. As I said, I don't use FG 3.4 and as such SVN is of zero consequence to if you can please download and install the latest version. Pinto, please verify that the address you posted is available outside of the sim. Have you tried reinstalling? Beyond that, I'm at a loss, and seeing as how you aren't very willing to work with us without being salty, I'm gonna recommend you use google as your at-home tech support instead and bid you good day. PINTO wrote in Fri 7:45 pm:That works for everyone but you, which tells me either your system is messed up and reinstalling flightgear is your best option, or the error is an ebkac. Note: If you did not get a reponse, even after 7 days, you may want to check out the FlightGear mailing lists to ask your question there. If you are seeing corrupted/broken textures, please see this article. To run FlightGear on old computers with bad OpenGL support, please take a look at this wiki article. If you experience FlightGear crashes, please report a bug using the issue tracker (can be also used for feature requests). please upload a screenshot of the problem. copy&paste your commandline (tick the "Show commandline box on the last page of FGRun or the "Others" section on the Mac launcher). is there any output printed to the console (black window)? does the problem occur with any aircraft, at any airport? what OS (Windows Xp/Vista, Mac etc.) are you running? Make sure to include answers to at least the following questions in your initial post. In order to help you, we need to know a lot of information.