OK thanks.

 

 

Try Flight1's GTN 750 and you won't care about it anymore - wicked!

+1

+1

+2.... I changed over and boy all of sudden the RXP unit is OLD and CLUNKY

Just to let everyone know DTG has decided to keep the Beta (Which was to close today) open for a few more days.

Wanted to say thanks, I've decided I'm going to purchase FSX-SE today after reading this thread and hearing some good things.  I was contemplating installing my boxed FSX gold or SE, and you guys helped me made that decision.  So begins the long installation process and hardware setup, but to be honest I enjoy it and I'm sure i'll run into a few quirks.

 

I'm currently rocking crossfired 6950's (I know crossfire has no advantage in FSX). I'll wait until I'm running a gtx780 until I try directx10.  I'm pretty confident from doing all reading on FSX-SE, its the way to go.

Wanted to say thanks, I've decided I'm going to purchase FSX-SE today after reading this thread and hearing some good things.  I was contemplating installing my boxed FSX gold or SE, and you guys helped me made that decision.  So begins the long installation process and hardware setup, but to be honest I enjoy it and I'm sure i'll run into a few quirks.

 

I'm currently rocking crossfired 6950's (I know crossfire has no advantage in FSX). I'll wait until I'm running a gtx780 until I try directx10.  I'm pretty confident from doing all reading on FSX-SE, its the way to go.

Make sure that when steam installs fsx the the FSX,cfg and Scenery.cfg are named just that. If steam installs FSX as FSX-se.cfg then you need to run a registry repair, assuming of course that you had FSX boxed installed at some time

Make sure that when steam installs fsx the the FSX,cfg and Scenery.cfg are named just that. If steam installs FSX as FSX-se.cfg then you need to run a registry repair, assuming of course that you had FSX boxed installed at some time

Beer,

 

Thanks for the heads up, this is a clean install PC now as I upgraded to SSD's for both Windows and FSX drive.  So I shouldn't have this problem I assume.  I will still check, thank you!

 

 

Thanks for the heads up, this is a clean install PC now as I upgraded to SSD's for both Windows and FSX drive. So I shouldn't have this problem I assume. I will still check, thank you!

 

Hi, franjoflyer,

 

AFAIK, if you have FSX:MS already on your computer, or possibly remnants of it from a previous install, FSX:SE (Steam) will use different folder names and change the name of at least the fsx.cfg file.  This will confuse any addon installer that was made before FSX:SE.  But if you are doing a new, clean install of FSX:SE, the folder and file names should be the same. 

 

Another issue is that FSX:SE does not install all SimConnect files that addons use, especially older ones.  But it does provide a way to install them.  If you go to:

... SteamLibrary\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces

 

you will see three subfolders.  Go into each of them and run simconnect.msi.  This will install the ones older addons need.  However some older addons, such as the Level-D 767, can only be made to work w/ some additional tweaking.

 

You should also know that the PMDG 777 does not appear to work w/ the new Beta version, and there are reports of similar issues w/ thee Aerosoft A320.  It is unclear how and when these will be fixed with the next non-Beta update.

 

Mike

Try Flight1's GTN 750 and you won't care about it anymore - wicked!

Add RealAir Duke Turbine 2 and you're laughing :rolleyes:

 

It does not retrofit into the same airplanes I want, and I like the simplicity of the 430 and 530 better. It simulates the models in real aircraft the gtn is not in many.

Another issue is that FSX:SE does not install all SimConnect files that addons use, especially older ones. But it does provide a way to install them. If you go to:

... SteamLibrary\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces

 

you will see three subfolders. Go into each of them and run simconnect.msi. This will install the ones older addons need. However some older addons, such as the Level-D 767, can only be made to work w/ some additional tweaking.

 

You should also know that the PMDG 777 does not appear to work w/ the new Beta version, and there are reports of similar issues w/ thee Aerosoft A320. It is unclear how and when these will be fixed with the next non-Beta update.

 

Mike

Mike thanks so much for the info. The truth is I have zero clue how to fly jets. Im a long way from that. I own opusfsx and a2a172 cesna. Would it be a good idea to install those anyway just to be safe?

 

I think im not going to install the beta yet and stick to the normal version as the beta ends soon

 

Everybody is so helpful here what a great community.

 

 

I own opusfsx and a2a172 cesna. Would it be a good idea to install those anyway just to be safe?

I think im not going to install the beta yet and stick to the normal version as the beta ends soon

 

I found a post that says the A2A aircraft are working OK, except possibly for beacon lights.  I'm not familiar w/ Opus, but I don't see how it could hurt to try it.

 

Glad to  be of help!

 

Mike

Beer,

 

Thanks for the heads up, this is a clean install PC now as I upgraded to SSD's for both Windows and FSX drive.  So I shouldn't have this problem I assume.  I will still check, thank you!

Your and I are in exactly the same place, clean SSDs and I too decided on FSX-SE over FSX-MS and P3D v2.5. I will however keep the old FSX on a separate SSD and my old Windows 7 on another SSD, I have quick swap bays for the SSDs.

Well its installed.  I have it installed to my D:\SteamLibrary\steamapps\common\FSX (Samsung Evo 250gb SSD)

but my fsx.cfg file is in my c:\Users\Franjo\AppData\Roaming\Microsoft\FSX directory. While my scenary.cfg is in my game install directory D:\SteamLibrary\steamapps\common\FSX.  Is this all ok?

 

Capt Spiers, I won't lie I'm pretty pumped up.  

Scenery.cfg will be in C:\ProgramData\Microsoft\FSX

For some reason, FSX has several scenery.cfg files.  The one it's actually using should be in:

 

C:\ProgramData\Microsoft\FSX

 

Your folder names look good -- same as original FSX so less confusing for addon installers.

 

Mike