July 6, 201015 yr for some reason, i keep getting this error. I go into my scenery library where I delete my two scenery's; st maarten and boston logan than i click "add" where I add my own new boston and st maarten airports. when i do a refresh, my sim reloads the default tampa airports even after i deleted them.This is what I added see below: all I did was rename the folder. Default name was FlyTampa-Boston or FlyTampa-St Maartin. So I deleted the FlyTampa-Boston and added the FlyTampa - Boston Logan Int'l Airport in the library....thats all and it keeps reloading the default one and i keep getting that error. It see's my new added one and I get no error. And what is this NewScenery.CFG and OldScenery.CFG?
July 6, 201015 yr for some reason, i keep getting this error. I go into my scenery library where I delete my two scenery's; st maarten and boston logan than i click "add" where I add my own new boston and st maarten airports. when i do a refresh, my sim reloads the default tampa airports even after i deleted them.This is what I added see below: all I did was rename the folder. Default name was FlyTampa-Boston or FlyTampa-St Maartin. So I deleted the FlyTampa-Boston and added the FlyTampa - Boston Logan Int'l Airport in the library....thats all and it keeps reloading the default one and i keep getting that error. It see's my new added one and I get no error. And what is this NewScenery.CFG and OldScenery.CFG? Not quite sure, but did you exit FS9 and restart so the deletion could take effect before adding the new scenery. I've never attempted to delete and load a new one with the same names before at the same time, so not sure if that can be done or not. Try deleting, exit FS9, restart then add the two new ones. See if that works. I'm just guessing here.Jim D.
July 6, 201015 yr Tried that samething. I posted a new screenshot and I see an OldScenery.CFG and a NewScenery.CFG...I have no idea what those two are.
July 6, 201015 yr Tried that samething. I posted a new screenshot and I see an OldScenery.CFG and a NewScenery.CFG...I have no idea what those two are.For the moment forget about the "old and new" scenery.cfg files and concentrate on getting the scenery.cfg file corrected.Area 39 "should" look like this when you view the scenery.cfg file using Notepad:[Area.039]Title=Addon SceneryLocal=Addon SceneryLayer=39Active=TRUERequired=FALSERemote=There should be no reference to an added scenery at all on this entry (as your error message is reporting).I would use the Scenery Library dialogue in the sim and delete the Addon scenery entry - assuming it is there (and it should be by default).Also double check to see that the other entry has indeed been deleted.Exit the sim and before restarting it, navigate to your Addon scenery folder and locate the file named SCENERY.dat - delete it and restart then restart the sim.Hopefully the error message will not now display.Then using the Scenery Library dialogue once again, add the Addon scenery back in and set it just above Propeller Objects. Exit and restart once again.If still good, then add your other scenery entry.What Operating System are you using? If Vista or Win 7 you probably should turn off UAC (User Account Control) temporarily while making these changes.Keep us posted.
July 6, 201015 yr I did what you have instructed and still get the same error. I use windows xp pro. My regular scenery.cfg looks like this:[Area.39]Title=FlyTampa-BostonLocal=D:\Program Files\Microsoft Games\Flight Simulator 9\Addon Scenery\FlyTampa-Boston\Active=TRUERequired=FALSELayer=39 [Area.34]Title=FlyTampa-MaartenLocal=D:\Program Files\Microsoft Games\Flight Simulator 9\Addon Scenery\FlyTampa-Maarten\Active=TRUERequired=FALSELayer=34I also looked in my OldScenery.CFG and it looks like this:[Area.39]Title=FlyTampa-BostonLocal=D:\Program Files\Microsoft Games\Flight Simulator 9\Addon Scenery\FlyTampa-Boston\Active=TRUERequired=FALSELayer=39[Area.34]Title=FlyTampa-MaartenLocal=D:\Program Files\Microsoft Games\Flight Simulator 9\Addon Scenery\FlyTampa-Maarten\Active=TRUERequired=FALSELayer=34[Area.040]Title=FlyTampa - Boston Logan Int'l AirportLocal=Addon Scenery\FlyTampa - Boston Logan Int'l AirportRemote=Active=TRUERequired=FALSELayer=38Finally, my NewScenery.CFG looks like this:[Area.39]Title=FlyTampa-BostonLocal=D:\Program Files\Microsoft Games\Flight Simulator 9\Addon Scenery\FlyTampa-Boston\Active=TRUERequired=FALSELayer=39 [Area.34]Title=FlyTampa-MaartenLocal=D:\Program Files\Microsoft Games\Flight Simulator 9\Addon Scenery\FlyTampa-Maarten\Active=TRUERequired=FALSELayer=34
July 6, 201015 yr Do you have an entry in your regular scenery.cfg file for Addon scenery?As stated before, mine is area 39:[Area.039]Title=Addon SceneryLocal=Addon SceneryLayer=39Active=TRUERequired=FALSERemote=Do you have this (regardless of area or Layer number) at all?
July 6, 201015 yr I think I fixed the problem. What I did was I deleted my OldScenery.CFG file. I than went into my NewScenery.CFG file and delete the default entry Boston-Logan and added mine in as you can see from the screenshot below. I saved the NewScenery.CFG and no more error pop-up. I go into my Scenery Library and I dont see the default Boston-Logan Add-on only mine.In the Scenery.CFG this is what I have: I put the numbers in order. [Area.038]Title=FlyTampa - Boston Logan Int'l AirportLocal=Addon Scenery\FlyTampa - Boston Logan Int'l AirportRemote=Active=TRUERequired=FALSELayer=38[Area.039]Title=FlyTampa - Princess Juliana Int'l AirportLocal=Addon Scenery\FlyTampa - Princess Juliana Int'l AirportRemote=Active=TRUERequired=FALSELayer=39[Area.040]Title=FlyTampa - Miami Int'l AirportLocal=Addon Scenery\FlyTampa - Miami Int'l AirportRemote=Active=TRUERequired=FALSELayer=40[Area.041]Title=FlyTampa - Tampa Int'l AirportLocal=Addon Scenery\FlyTampa - Tampa Int'l AirportRemote=Active=TRUERequired=FALSELayer=41
July 6, 201015 yr Josh,The error box is telling you that the scenery.cfg has told FS where to find the scenery mentioned in the error box, but it doesn't think that the scenery itself is there.The confusion could be that your sceneries look like they are out of numerical sequence; [Area.039] comes before [Area.034] in your post. Check that your scenery.cfg entries are sequentially numbered, starting from [Area.001] which has an associated 'Layer=1' line. FS can get confused if the Area numbering is out of sequence - or if the 'Layer=' number is not the same as the Area number. The last area in sequence should be the most recent that you added. If yours is out of sequence, there are tools to fix it without having to do it manually - but just check whether this is a problem first.Don't worry about OldScenery - it is an autogenerated version of the previous scenery.cfg before you most recently altered it. It looks like the NewScenery is a temporary file that's generated after you've updated the scenery library, but before you re-start FS9. The re-start re-builds the scenery.cfg file and deletes the NewScenery. So if you've still got a NewScenery file, then this means that you probably haven't re-started FS to bed the new scenery.cfg in. As a note, the extract fromOldScenery that you posted not only has areas 39 and 34 out of sequence, but [Area.040] has a layer number of 38!;)EDIT: looks like you got there before my post! Number sequence is important in this file.
July 6, 201015 yr Thank you for your help anyways! :( I had a few that were out of order so I fixed it:[General]Title=FS9 World SceneryDescription=FS9 Scenery DataClean_on_Exit=FALSE[Area.001]Title=Default TerrainTexture_ID=1Layer=1Active=TRUERequired=TRUELocal=Scenery\WorldRemote=[Area.002]Title=Default SceneryLocal=Scenery\BASELayer=2Active=TRUERequired=TRUERemote=[Area.003]Title=AfricaLayer=3Active=TRUERequired=FALSELocal=Scenery\AfriRemote=[Area.004]Title=AsiaLayer=4Active=TRUERequired=FALSELocal=Scenery\AsiaRemote=[Area.005]Title=AustraliaLayer=5Active=TRUERequired=FALSELocal=Scenery\AustRemote=[Area.006]Title=Eastern EuropeLocal=Scenery\EURELayer=6Active=TRUERequired=FALSERemote=[Area.007]Title=Western EuropeLocal=Scenery\EURWLayer=7Active=TRUERequired=FALSERemote=[Area.008]Title=Central North AmericaLocal=Scenery\NAMCLayer=8Active=TRUERequired=FALSERemote=[Area.009]Title=Eastern North AmericaLocal=Scenery\NAMELayer=9Active=TRUERequired=FALSERemote=[Area.010]Title=Western North AmericaLocal=Scenery\NAMWLayer=10Active=TRUERequired=FALSERemote=[Area.011]Title=OceaniaLayer=11Active=TRUERequired=FALSELocal=Scenery\OcenRemote=[Area.012]Title=South AmericaLayer=12Active=TRUERequired=FALSELocal=Scenery\SameRemote=[Area.013]Title=Amsterdam Aerial PhotoLayer=13Active=TRUERequired=FALSELocal=Scenery\Cities\AmsterdRemote=[Area.014]Title=Anchorage Aerial PhotoLayer=14Active=TRUERequired=FALSELocal=Scenery\Cities\AnchorRemote=[Area.015]Title=Atlanta Aerial PhotoLayer=15Active=TRUERequired=FALSELocal=Scenery\Cities\AtlantaRemote=[Area.016]Title=Chicago Aerial PhotoLayer=16Active=TRUERequired=FALSELocal=Scenery\Cities\ChicagoRemote=[Area.017]Title=Dallas Aerial PhotoLocal=Scenery\Cities\DallasLayer=17Active=TRUERequired=FALSERemote=[Area.018]Title=Denver Aerial PhotoLocal=Scenery\Cities\DenverLayer=18Active=TRUERequired=FALSERemote=[Area.019]Title=Heathrow Aerial PhotoLayer=19Active=TRUERequired=FALSELocal=Scenery\Cities\HeathrowRemote=[Area.020]Title=Hong Kong Aerial PhotoLayer=20Active=TRUERequired=FALSELocal=Scenery\Cities\HongkongRemote=[Area.021]Title=Kitty Hawk Aerial PhotoLayer=21Active=TRUERequired=FALSELocal=Scenery\Cities\KittyhwkRemote=[Area.022]Title=Las Vegas Aerial PhotoLayer=22Active=TRUERequired=FALSELocal=Scenery\Cities\LasvegasRemote=[Area.023]Title=Los Angeles Aerial PhotoLayer=23Active=TRUERequired=FALSELocal=Scenery\Cities\LaRemote=[Area.024]Title=Miami Aerial PhotoLayer=24Active=TRUERequired=FALSELocal=Scenery\Cities\MiamiRemote=[Area.025]Title=New York Aerial PhotoLocal=Scenery\Cities\NewYorkLayer=25Active=TRUERequired=FALSERemote=[Area.026]Title=Niagara Aerial PhotoLayer=26Active=TRUERequired=FALSELocal=Scenery\Cities\NiagaraRemote=[Area.027]Title=Oshkosh Aerial PhotoLocal=Scenery\Cities\OshkoshLayer=27Active=TRUERequired=FALSERemote=[Area.028]Title=Paris Aerial PhotoLayer=28Active=TRUERequired=FALSELocal=Scenery\Cities\ParisRemote=[Area.029]Title=Phoenix Aerial PhotoLayer=29Active=TRUERequired=FALSELocal=Scenery\Cities\PhoenixRemote=[Area.030]Title=San Francisco Aerial PhotoLayer=30Active=TRUERequired=FALSELocal=Scenery\Cities\SanfranRemote=[Area.031]Title=Seattle Aerial PhotoLocal=Scenery\Cities\SeattleLayer=31Active=TRUERequired=FALSERemote=[Area.032]Title=St. Maarten Aerial PhotoLocal=Scenery\Cities\StmaartenLayer=32Active=TRUERequired=FALSERemote=[Area.033]Title=Sydney Aerial PhotoLayer=33Active=TRUERequired=FALSELocal=Scenery\Cities\SydneyRemote=[Area.034]Title=Generic LibrariesLocal=Scenery\GenericLayer=34Active=TRUERequired=TRUERemote=[Area.035]Title=Vehicle LibrariesLocal=Scenery\VehiclesLayer=35Active=TRUERequired=TRUERemote=[Area.036]Title=Propeller ObjectsLocal=Scenery\propsLayer=36Active=TRUERequired=TRUERemote=[Area.037]Title=Tokyo Aerial PhotoLocal=Scenery\Cities\TokyoRemote=Active=TRUERequired=FALSELayer=37[Area.038]Title=FlyTampa - Boston Logan Int'l AirportLocal=Addon Scenery\FlyTampa - Boston Logan Int'l AirportRemote=Active=TRUERequired=FALSELayer=38[Area.039]Title=FlyTampa - Princess Juliana Int'l AirportLocal=Addon Scenery\FlyTampa - Princess Juliana Int'l AirportRemote=Active=TRUERequired=FALSELayer=39[Area.040]Title=FlyTampa - Miami Int'l AirportLocal=Addon Scenery\FlyTampa - Miami Int'l AirportRemote=Active=TRUERequired=FALSELayer=40[Area.041]Title=FlyTampa - Tampa Int'l AirportLocal=Addon Scenery\FlyTampa - Tampa Int'l AirportRemote=Active=TRUERequired=FALSELayer=41
July 6, 201015 yr Josh,Looks like your entries are mis-numbered from default (Tokyo is Area.034 by default), but that shouldn't make much difference. However, you do have an entry missing from your scenery.cfg file:[Area.038]Title=Addon SceneryLayer=38Active=TRUERequired=FALSELocal=Addon SceneryRemote=The way FS works is that if you put scenery into the 'Addon Scenery' folder then you don't have to manually add it through the scenery menu - this is why the above entry is there. The way you've done it is OK, but anything that would normally go in 'Addon Scenery' (like Rwy12 objects and libraries, or any custom AFCADs you may want to add) would all have to be added manually. Your choice though.;)
July 6, 201015 yr I prefer to add things manually to be sure. And the Tokyo photo is right below the boston logan and right above the propellor...that is okay? Update: For some strange reason now, after I installed fscuip, fsgenises when I try to enter FS9, the logo appears and then thats it...it wont enter the sim.
July 6, 201015 yr I also prefer to add things manually into a dedicated scenery folder (I actually have very little in the Addon Scenery folder beyond RWY12 stuff and AFCADs). All of the manually-added sceneries add to the end of the scenery.cfg, after the last of the default entries, which is - Addon Scenery, Area.038! The reason it's there is that being a default location, what it contains is automatically loaded by the sim early on in the process and is available for any sceneries that follow that have been manually input. Also, a number of addons (e.g. AFCAD files) are easier to accommodate in that folder since otherwise, you're down to putting single files into individual folders - and then you have to worry about their placement in the file to make sure they show up when they should. A rule of thumb is that the most recently added sceneries are loaded in preference to earlier ones, in other words, the default sceneries 1-38 are loaded first, and then the ones you add after that are loaded later, which then are used by the sim in preference to the earlier-loaded one. A whizzo new Heathrow recently added as area 145 in the scenery.cfg would show up in the sim in preference to the original default airport, as an example. So the higher area numbers have higher priority.It may be more convenient in the long run to put the Addon Scenery reference back into the scenery.cfg file, and to put Tokyo in the right place - although it probably won't make much difference where it now is, although a default location will be out of its designed sequence. Since you only have three add-on sceneries so far, it should be easy enough to do this - much easier than when you have many hundreds of sceneries, like many simmers do. Then it becomes a nightmare if you have to rebuild the scenery.cfg because something's gone wrong and you can't see the wood for the trees.;)EDIT: A thought for your non-booting: I don't have FSGenesis so can't comment on how it installs, but being scenery-based, it might be putting things into the Addon Scenery folder - that wouldn't then be accessible to the sim since the scenery.cfg doesn't contain a reference to that location, so it might stop loading at that point. Just a thought. Never had an issue with FSUIPC.
July 6, 201015 yr It's why it is good practice BEFORE adding any scenery to start FS9 and then exit (don't believe you need to go past the main menu). This will ensure any pending changes in NewScenery are installed (FS9 scenery library only does actual update on a restart). Once that is done you can add scenery via scenery library, manually, or 3rd party update and FS9 should be consistent when next started.scott s..
July 6, 201015 yr when I try to point the airport installer to my add-on scenery folder....it will not let me.
July 7, 201015 yr Hi,The problem is shown in the two screen shots you provided.Your Boston scenery that's in the scenery.cfg (Screen Capture #1) is as follows:[Area.39]Title=FlyTampa-BostonLocal=D:\Program Files\Microsoft Games\Flight Simulator 9\Addon Scenery\FlyTampa-Boston\Active=TRUERequired=FALSELayer=39Your path statement (shown above - Local=) is incorrect.========================================The Local path statement is incomplete, (as seen in Screen Capture #2) it should read:========================================[Area.039]Title=FlyTampa - Boston Logan Int'l Airport (the change in this line is not important, its the next line thats important)Local=D:\Program Files\Microsoft Games\Flight Simulator 9\Addon Scenery\FlyTampa - Boston Logan Int'l AirportRemote=Active=TRUERequired=FALSELayer=39you could also have it as follows:[Area.39]Title=FlyTampa-BostonLocal=Addon Scenery\FlyTampa - Boston Logan Int'l AirportActive=TRUERequired=FALSELayer=39Notice the addition of: (Logan Int'l Airport) to the end of (FlyTampa - Boston) this gives you the correct path (as seen in Screen Capture #2) and will remove the error you see during the start of FS. Not quite sure, but did you exit FS9 and restart so the deletion could take effect before adding the new scenery. I've never attempted to delete and load a new one with the same names before at the same time, so not sure if that can be done or not. Try deleting, exit FS9, restart then add the two new ones. See if that works. I'm just guessing here.Jim D. Former Beta Tester - (for a few companies) - As well as provide Regional Voice Set Recordings Two: AMD-9950X | One: AMD-7950X3D | Three: Asus TUF 4090s | Three: 64GB DDR5 RAM 6000mhz | Three: Cosair 1300 P/S | Three: 990Pro 2TB NVME One: Eugenius ECS2512 - 2.5 GHz Switch | Three: Ice Giant Elite CPU Coolers | Three: 75" 4K UHDTVs | One: Boeing 737NG Flight Deck
Create an account or sign in to comment