Flightsim Commander 9 6 Crackle

Hi, Volker, I have FSC 9.6 working with FSX Steam version. I have a dual install of FSX:MS (Microsoft boxed version) and FSX:SE (Steam version). This causes Steam to install using different names for some folders, including the all-important C: ProgramData Microsoft FSX. Steam names it.FSX-SE.

Jul 17, 2014 como baixar e instalar o flight sim comander no fs2004 e. Fs commander fsx 9.5.0 guide installation. Flightsim commander 9 + route + fmc. FlightSim Commander 9.7 is a professional flight planner, GPS, Moving Map and navigation tool for Flight Simulator 2004, Flight Simulator X, FSX:Steam Edition, and.

However there are some workarounds that make FSC work. 1) 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. 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. 2) rename C: ProgramData Microsoft FSX to something else. This will cause FSCDBManager to ask where to find the scenery.cfg file instead of automatically finding the original C: ProgramData Microsoft FSX location.

Flightsim Commander 9 6 Crackle

Point it to C: ProgramData Microsoft FSX-SE. 3) 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. Go to C: ProgramData Microsoft FSX-SE, copy the scenery.cfg file to the top level of FSX:SE. (It will probably ask if you want to overwrite the scenery.cfg file already there. Choose an option that keeps both files). Then rename the newly copied scenery.cfg to scenerycfg.fsc so that the networked FSCDBManager can read it. Run FSCDBManager.

Volker, two points: A) I believe none of these problems exist for someone with a clean install of FSX:SE, and no trace of FSX:MS. 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. 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. B) 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. Right now it can't be changed if it finds C: ProgramData Microsoft FSX. All the user would have to do is point it to C: ProgramData Microsoft FSX-SE instead. This would make it easy for the user to point the FSCDBManager to the correct folder.

This would eliminate the more complicated procedure I described in 2) above. Hi Mike, thanks for the information and your instructions regarding the use of the FlightSim Commander with FSX-Steam Edition. Please contact me by e-mail. My e-mail address you can find here: Kind regards, Volker Hi Volker, Did you ever sort out if you are going to proceed with a steam version of FSC.

I have FSC 9.6 working great with FSX on my flight sim win 7 64 bit machine and just downloaded FSC 9.6 on my win 8.1 64 bit machine (C: FSC) which has FSX-SE installed only. I had a look around, but I have no idea where FSX-SE is stashed in my system, so have no chance of setting up the database. Blade Trinity Fr Rapidshare Search here. Regards Geoff. Hi Volker, Did you ever sort out if you are going to proceed with a steam version of FSC.

I have FSC 9.6 working great with FSX on my flight sim win 7 64 bit machine and just downloaded FSC 9.6 on my win 8.1 64 bit machine (C: FSC) which has FSX-SE installed only. I had a look around, but I have no idea where FSX-SE is stashed in my system, so have no chance of setting up the database. Regards Geoff Hi Geoff and everyone, FSC should work on a Windows 8 machine w FSX:SE if that is the only version of FSX on the computer (and there is nothing left in the registry from an install of FSX:MS-Box version).

In that case FSX:SE uses the same folder and file names as FSX:MS (and AFAIK all the folders are same in Windows 8 as in Windows 7). It is only with a dual FSX:MS and FSX:SE on the same computer that FS Commander won't find all the correct folders and files. Hi Geoff and everyone, FSC should work on a Windows 8 machine w FSX:SE if that is the only version of FSX on the computer (and there is nothing left in the registry from an install of FSX:MS-Box version). In that case FSX:SE uses the same folder and file names as FSX:MS (and AFAIK all the folders are same in Windows 8 as in Windows 7). It is only with a dual FSX:MS and FSX:SE on the same computer that FS Commander won't find all the correct folders and files. Mike Horst/Mike, on this machine, there has never been a FSX:MS, only FSX:SE. To get FSC working you have to point the database manager at FSX.

I have no idea where the exe file is lurking despite several searches. Regards Geoff. Hi Geoff, not sure which exe file you are missing.Could you clarify? I just directed the FSC database manager to my FSX-SE installation (d: games Steam steamapps common FSX ), and it was happy.

Regards Horst Hi Horst, Thanks for this. Although folders in my Win 8.1 are a tad different, but you put me on the right track and I found the steam version of FSX(very well hidden). My 8.1 does not have a games folder.Anyway, once I found where FSX steam lived, and I set up the database, and flight plan files, FSC 9.6 works great. Thanks for the help. Love these types of forums where every one offers suggestions. Regards Geoff. Hi Geoff and everyone, FSC should work on a Windows 8 machine w FSX:SE if that is the only version of FSX on the computer (and there is nothing left in the registry from an install of FSX:MS-Box version).

In that case FSX:SE uses the same folder and file names as FSX:MS (and AFAIK all the folders are same in Windows 8 as in Windows 7). It is only with a dual FSX:MS and FSX:SE on the same computer that FS Commander won't find all the correct folders and files. Mike ah ok, well that makes sense then. Daxter Psp Iso Torrent Download there.

I have no additional airports in Steam, but in real FSX, additional airport parking bays are indicated in FSC. I just looked at my ORBX YBBN in my real FSX machine with FSC, it indicates the bays different to the steam version of FSX with the standard YBBN parking bays. Maybe I need to get one of my sceneries into the steam version to check. Hi, Por930, You need to have your addon scenery installed in your FSX:SE (Steam version) for it to show up there and for FSC to read it. In your situation, you need to install ORBX YBBN in the Steam version, not just in the 'real' (boxed) version. Since you apparently have both versions of FSX installed, you will need to follow one of the workarounds I gave in post #7 above to get FSC to find your scenery. I am no computer expert and I am addicted to FSCommanderl!

I also use Airport Development Editor (ADE 1.67) mostly to add ILS to existing FSX-SE airports. Have fought with the issue that some of the added ILS will not show on the FSC map, even though when the mouse arrow is on it it will read out the frequencies and that FSX-SE map will show that the added ILS is there. Have excluded (I believe) probable errors on my part as a good 40% of the additions work alright. Having noted more of this situation after upgrading to Windows 10 and FSX-SE and after reading these posts I guess I will just stop trying to resolve it and sit on it for the time being.

Must state that I cannot visualize flight simulation without the use of this fantastic FSCommander.

The tool FlightSim Commander 9 has been updated to version 9.6.0.9 and 'supports' P3D V4. Important note: FlightSim Commander Version 9.6 Revision 9 is, under certain conditions, compatible with Prepar3D V4. Requirement: The new and up-to-date FSUIPC5 5.1x from Pete Dowson is required for error-free connection and function of FlightSim Commander with Prepar3D V4. Limitations: FlightSim Commander Version 9.6 Revision 9 currently only identifies Add-On sceneries whose installation path was correctly entered in the file scenery.cfg located in the C: ProgramData Lockheed Martin Prepar3D v4 folder.