TNCM Problem Need help
TNCM Problem Need help
I bought the complete package this morning and installed it and everything works great including the airport SABA and St.Barthelemy(don't know how to spell it) but for some reason the textures for St.Maarten airport are no showing up the modifications to the ground have been made as you can tell but the buildings and runways and taxiways are not showing up. I attached a picture
- Attachments
-
- TNCM.JPG (60.56 KiB) Viewed 8640 times
- george[flytampa]
- Site Admin
- Posts: 3868
- george[flytampa]
- Site Admin
- Posts: 3868
viewtopic.php?t=2384
Go to this thread and he had the exact same thing go wrong and i used the solution provided and now it woks great
Go to this thread and he had the exact same thing go wrong and i used the solution provided and now it woks great
Guys,
After reading the other thread and seeing what the issue was I thought I would add my .02...
What is happening is that your scenery.cfg is getting confused. The easiest way to fix this is to
A. Edit your scenery.cfg to ensure it is correct.
B. Make 2 copies of your scenery.cfg and call one Oldscenery.cfg and the other newscenery.cfg Make sure all three files are exactly the same, place them in the FS root and overwrite if necessary. Now just restart, you will get the progress bar as it rebuilds your CORRECT scenery.cfg and voila.
Basically FS almost always has BOTH a scenery.cfg and an oldscenery.cfg present in the FS9 root directory and for the most part MS does a good job of keeping them matched. When you add new scenery it can not be written to your scenery .cfg because it is in use. Instead it adds newscenery.cfg If the two don't match though you will see issues described in this thread and they will get out of synch completely.
Hope this helps everyone,
-Paul
After reading the other thread and seeing what the issue was I thought I would add my .02...
What is happening is that your scenery.cfg is getting confused. The easiest way to fix this is to
A. Edit your scenery.cfg to ensure it is correct.
B. Make 2 copies of your scenery.cfg and call one Oldscenery.cfg and the other newscenery.cfg Make sure all three files are exactly the same, place them in the FS root and overwrite if necessary. Now just restart, you will get the progress bar as it rebuilds your CORRECT scenery.cfg and voila.
Basically FS almost always has BOTH a scenery.cfg and an oldscenery.cfg present in the FS9 root directory and for the most part MS does a good job of keeping them matched. When you add new scenery it can not be written to your scenery .cfg because it is in use. Instead it adds newscenery.cfg If the two don't match though you will see issues described in this thread and they will get out of synch completely.
Hope this helps everyone,
-Paul
The deal with the scenery CFGs is as follows.
When you add a scenery in the scenery manager within FS, having made the changes the new CFG is written to Newscenery.cfg. FS looks for this file when it starts up because, if it is there, FS knows to use that file for rebuilding the scenery. Its why you have to close the sim and restart after you've added some scenery layers.
Oldscenery.cfg is merely the previous version of your scenery.cfg and is almost never the same as scenery.cfg or Newscenery.cfg (it might be the same if you've added a scenery layer and taken it straight back out).
FS is not actually very good at keeping scenery.CFG in good shape. Drop a scenery layer down by several priority levels, use the sim once or twice and then remove that scenery. FS leaves a hole there, a gap in the numbering sequence that can cause any number of problems even though the sim loads okay.
You must use something like Rana Hossain's FlightsimManager program or similar CFG checkers to get those numbers back in sequence. If I'm adding scenery layers manually (as I often do because for me its quicker) I always run the cfg checker first. If I remove scenery layers I always run it. If it comes up with no errors I'm surprised (and I've not been surprised often - usually there's an error). Its possible that if you delete a layer and change another layer's priority, then FS bothers to check for numbering and then we get no errors.
Paul - scenery.cfg can be written to when FS is operating. I've edited it myself (ages ago, before I knew about newscenery.cfg) when FS is running. It is used once, at startup and then is no longer required. If you use the scenery manager it might lock that file for the duration of your scenery configurations, but that's all. If you make changes in the scenery manager it doesn't write to scenery.cfg at all; that file is read-only and newscenery.cfg is written.
Also bear in mind that if you've manually changed scenery.cfg and there's a newscenery.cfg file present in the same folder, your manual changes will be lost because FS will read newscenery.cfg instead (overwriting your scenery.cfg and putting a copy of your changes into oldscenery.cfg).
When you add a scenery in the scenery manager within FS, having made the changes the new CFG is written to Newscenery.cfg. FS looks for this file when it starts up because, if it is there, FS knows to use that file for rebuilding the scenery. Its why you have to close the sim and restart after you've added some scenery layers.
Oldscenery.cfg is merely the previous version of your scenery.cfg and is almost never the same as scenery.cfg or Newscenery.cfg (it might be the same if you've added a scenery layer and taken it straight back out).
FS is not actually very good at keeping scenery.CFG in good shape. Drop a scenery layer down by several priority levels, use the sim once or twice and then remove that scenery. FS leaves a hole there, a gap in the numbering sequence that can cause any number of problems even though the sim loads okay.
You must use something like Rana Hossain's FlightsimManager program or similar CFG checkers to get those numbers back in sequence. If I'm adding scenery layers manually (as I often do because for me its quicker) I always run the cfg checker first. If I remove scenery layers I always run it. If it comes up with no errors I'm surprised (and I've not been surprised often - usually there's an error). Its possible that if you delete a layer and change another layer's priority, then FS bothers to check for numbering and then we get no errors.
Paul - scenery.cfg can be written to when FS is operating. I've edited it myself (ages ago, before I knew about newscenery.cfg) when FS is running. It is used once, at startup and then is no longer required. If you use the scenery manager it might lock that file for the duration of your scenery configurations, but that's all. If you make changes in the scenery manager it doesn't write to scenery.cfg at all; that file is read-only and newscenery.cfg is written.
Also bear in mind that if you've manually changed scenery.cfg and there's a newscenery.cfg file present in the same folder, your manual changes will be lost because FS will read newscenery.cfg instead (overwriting your scenery.cfg and putting a copy of your changes into oldscenery.cfg).