Full system specs? (hardware, OS, software,fg version,fg startup parameters,environment variables,runtime settings,scenery version,console warnings/errors etc.) >In scenery module w080n40 it appears as if all the objects>have been shifted a few hundred feet. If you fly around New>York, you'll notice that quite a few buildings are in the>water. Also an airport to the north of New York City has an>electric power line tower just next to the runway!>>Second problem is that the scenery loader is not dealing with>the San Francisco base module. If I start in this module I>can see the scenery ok but it won't load any other modules>that I have downloaded and installed.well,if San Fransisco works, how exactly did you come up with the conclusion that the San Fransisco scenery "module" is causing you any problems?>I just get water no>matter where I go, no matter if I have the modules or not. If>I start from say KLAX and try to fly into the San Fran scenery>module, I get water again. most likely you simply haven't installed the scenery tiles properly, or might have failed to start up FlightGear so that its made aware of any newly added tiles (in non-standard locations).>The files are in a separate directory from the base module>that came with FlightGear. >>FlightGear is in C:Program FilesFlightGear>Base Module is in C:Program>FilesFlightGeardataScenery>Downloaded modules in C:Program>FilesFlightGeardataWorldScenery>That are extracted to C:Program FilesFlightGearscenery>>This was what was suggested in the getstart.pdf.Not sure about that, based on the above information you seem to have put the downloaded ARCHIVES into $FG_ROOT/WorldScenery whereas you have put the actual (extracted) tiles into C:Program FilesFlightGearscenery?Don't get me wrong, you can do this but FlightGear is not able to deal with compressed tiles and concerning your real scenery path, we can't tell whether it's supposed to work or not because you failed to provide the startup parameters you are using,in this case it is specifically important to tell us about the configuration you are using for startup (any parameters and runtime settings you may be using).Are you starting FG from a shell or GUI frontend?Have you actually specified "C:Program FilesFlightGearscenery" as a scenery folder? Otherwise, FlightGear would not know about it, especially because you installed the scenery to a non-standard location, you even put it outside of its base package directory.>I'm running under Windows XP, and used the 'Install &>Uninstall Scenery' application to install the scenery.>>Any help would be appreciated.Are you using fgrun/"FlightGear Launch Control"?Check the first wizard page and add the above path to the scenery field.
AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!
Full system specs? (hardware, OS, software,fg version,fg startup parameters,environment variables,runtime settings,scenery version,console warnings/errors etc.) >In scenery module w080n40 it appears as if all the objects>have been shifted a few hundred feet. If you fly around New>York, you'll notice that quite a few buildings are in the>water. Also an airport to the north of New York City has an>electric power line tower just next to the runway!>>Second problem is that the scenery loader is not dealing with>the San Francisco base module. If I start in this module I>can see the scenery ok but it won't load any other modules>that I have downloaded and installed.well,if San Fransisco works, how exactly did you come up with the conclusion that the San Fransisco scenery "module" is causing you any problems?>I just get water no>matter where I go, no matter if I have the modules or not. If>I start from say KLAX and try to fly into the San Fran scenery>module, I get water again. most likely you simply haven't installed the scenery tiles properly, or might have failed to start up FlightGear so that its made aware of any newly added tiles (in non-standard locations).>The files are in a separate directory from the base module>that came with FlightGear. >>FlightGear is in C:Program FilesFlightGear>Base Module is in C:Program>FilesFlightGeardataScenery>Downloaded modules in C:Program>FilesFlightGeardataWorldScenery>That are extracted to C:Program FilesFlightGearscenery>>This was what was suggested in the getstart.pdf.Not sure about that, based on the above information you seem to have put the downloaded ARCHIVES into $FG_ROOT/WorldScenery whereas you have put the actual (extracted) tiles into C:Program FilesFlightGearscenery?Don't get me wrong, you can do this but FlightGear is not able to deal with compressed tiles and concerning your real scenery path, we can't tell whether it's supposed to work or not because you failed to provide the startup parameters you are using,in this case it is specifically important to tell us about the configuration you are using for startup (any parameters and runtime settings you may be using).Are you starting FG from a shell or GUI frontend?Have you actually specified "C:Program FilesFlightGearscenery" as a scenery folder? Otherwise, FlightGear would not know about it, especially because you installed the scenery to a non-standard location, you even put it outside of its base package directory.>I'm running under Windows XP, and used the 'Install &>Uninstall Scenery' application to install the scenery.>>Any help would be appreciated.Are you using fgrun/"FlightGear Launch Control"?Check the first wizard page and add the above path to the scenery field.
Share this post
Link to post
Share on other sites