Free Microsoft Flight Simulator Addons FSX Downloads aircraft, planes, military.
#STEAM FSX FSNAVIGATOR HOW TO#
I discussed how to deal with this earlier in this thread, in post #7, option 1) or option 2).12:00pm. Scroll through it and see if it has entries for all your addon scenery.Īlso, check if you have a separate FSX:SE entry at path C:\ProgramData\Microsoft\FSX-SE.
You can do this by opening it with notepad. The correct location is explained in the FSC manual).
(Note that there are several scenery.cfg files in various places in FSX, but only one is used. Make sure that it has the correct scenery.cfg file. You can check by navigating to that folder and finding the scenery.cfg file there. When you look at the FSC Database Manager window, after you select your FSX:SE path in the window on the left, is the correct scenery.cfg path showing in the window on the right? The path should be something likeĬ:\ProgramData\Microsoft\FSX. I am assuming that you are running FSC on the same machine as FSX:SE. if an add-on airports has different gates/parking slots than FSX, FSC reads the default FSX gates/parking slots instead of the add-on ones. I have a single FSX-SE installation on a Win 7/64 machine, and FSC works fine except it does not read add-on airports, i.e. This would eliminate the more complicated procedure I described in 2) above. This would make it easy for the user to point the FSCDBManager to the correct folder. All the user would have to do is point it to C:\ProgramData\Microsoft\FSX-SE instead. Right now it can't be changed if it finds C:\ProgramData\Microsoft\FSX.
#STEAM FSX FSNAVIGATOR INSTALL#
I believe FSC is already working fine w/ a clean install of FSX:SE, but I'm not sure since I have a dual install.ī) You could made a small change to FSCDBManager, so that when it automatically locates C:\ProgramData\Microsoft\FSX, the user would still have the option of changing it. This is because with a FSX:SE only install, I believe, the installer keeps the same file names as FSX:MS and FSCDBManager will find them as it normally does. Run FSCDBManager.Ī) I believe none of these problems exist for someone with a clean install of FSX:SE, and no trace of FSX:MS. Then rename the newly copied scenery.cfg to scenerycfg.fsc so that the networked FSCDBManager can read it. (It will probably ask if you want to overwrite the scenery.cfg file already there. Go to C:\ProgramData\Microsoft\FSX-SE, copy the scenery.cfg file to the top level of FSX:SE. Point it to C:\ProgramData\Microsoft\FSX-SE.ģ) For a network install, instead of using FSCFSXCFG.exe to copy the scenery.cfg file to the top level of FSX:SE, do it manually. This will cause FSCDBManager to ask where to find the scenery.cfg file instead of automatically finding the original C:\ProgramData\Microsoft\FSX location. After runing FSCDBManager, remove the scenery.cfg file copied from C:\ProgramData\Microsoft\FSX-SE, and then reinstall the FSX:MS scenery.cfg file that you have backed up.Ģ) rename C:\ProgramData\Microsoft\FSX to something else. However there are some workarounds that make FSC work.ġ) rename/backup the scenery.cfg file in C:\ProgramData\Microsoft\FSX and then copy the scenery.cfg file from C:\ProgramData\Microsoft\FSX-SE to C:\ProgramData\Microsoft\FSX. This causes Steam to install using different names for some folders, including the all-important C:\ProgramData\Microsoft\FSX. I have a dual install of FSX:MS (Microsoft boxed version) and FSX:SE (Steam version). I have FSC 9.6 working with FSX Steam version.
0 kommentar(er)
