Sign in to follow this  
hadoken

FSX Steam Edition 62610

Recommended Posts

Sorry if this has been posted already, but has anyone ran into any compatibility issue with the PMDG 777 and FSX-SE 62610?

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I get an airplane that loads with no gauges, with the yokes fully turned to the right. 

Share this post


Link to post
Share on other sites

Brendan, have you installed all the simconnect files found in the SDK folders in the root FSX SE folder? I'll bet that you also didn't get asked to enter your registration key when you first selected the aircraft.

 

To the original poster, as of the latest SP1D update (which is what you will get if you download the installer now) is fully compatible with FSX SE.

Share this post


Link to post
Share on other sites

I get an airplane that loads with no gauges, with the yokes fully turned to the right. 

Okay thanks, I have the same thing in my 777 also after updating to 62610. I just wanted to confirm if it was a compatiablity issue with the 777 and the latest Steam Build. Hopefully a fix will be coming soon.

 

Brendan, have you installed all the simconnect files found in the SDK folders in the root FSX SE folder? I'll bet that you also didn't get asked to enter your registration key when you first selected the aircraft.

 

To the original poster, as of the latest SP1D update (which is what you will get if you download the installer now) is fully compatible with FSX SE.

SP1D is for the 737 if I'm not mistaken. My question is in regards to compatiablity between the latest FSX-SE 62610 build and the PMDG 777. The 737 SP1D works fine with FSX-SE build 62610.

Share this post


Link to post
Share on other sites

Brendan, have you installed all the simconnect files found in the SDK folders in the root FSX SE folder? I'll bet that you also didn't get asked to enter your registration key when you first selected the aircraft.

 

To the original poster, as of the latest SP1D update (which is what you will get if you download the installer now) is fully compatible with FSX SE.

 

You're exactly right- the registration window didn't even pop up on the first time loading- I'm not sure what updated with the new build (I thought it was just going to fix terrain.dll errors that are popping up), but it seems to have broken some externals. I'll retry simconnect installs. 

Share this post


Link to post
Share on other sites

You're exactly right- the registration window didn't even pop up on the first time loading- I'm not sure what updated with the new build (I thought it was just going to fix terrain.dll errors that are popping up), but it seems to have broken some externals. I'll retry simconnect installs. 

This is just my guess, but I don't think that 777 is complied for simconnect 62610. The 737 probably was and therefore doesn't have any issues with FSX-SE build 62610. I think the 777 is probably complied for simconnect 62608. PMDG will probably have to release an updated installer to fix the 777.

 

If you have Active Sky Next, you should see the same incompatiablity. The current build of ASN isn't compiled for simconnect 62610 either. These simconnect issue should be sorted out soon.

Share this post


Link to post
Share on other sites

I'll second that. The 737 works fine with the new FSX-SE build, but the 777 doesn't, and now that you mention it- ASN doesn't either. You're not alone!

Share this post


Link to post
Share on other sites

I'll second that. The 737 works fine with the new FSX-SE build, but the 777 doesn't, and now that you mention it- ASN doesn't either. You're not alone!

ugh...so you guys already reinstalled the simconnect msi's and getting the dreaded no registration with the 777 in 62610?

 

i havent been in the steam version since i got p3d a few weeks ago....but plan on using it soon to test something.

do you know if the update auto-installs or gives you the option to bypass it.  SE was working fine for me...no errors that the update is supposed to address.

Share this post


Link to post
Share on other sites

When the new build of SE installed, on initial run a new simconnect dialogue appeared- it looked like I could cancel out of it if I wanted. I didn't because  I always thought more versions of simconnect were better than less. I was wrong I guess!

Share this post


Link to post
Share on other sites

Well. I enabled the beta and it broke my 777 install. No gear and guages all black. (like when it is unregistered). FSX regular works fine. Reinstalled. No go, same thing. Looks like the beta broke my PMDG.

Share this post


Link to post
Share on other sites

Well. I enabled the beta and it broke my 777 install. No gear and guages all black. (like when it is unregistered). FSX regular works fine. Reinstalled. No go, same thing. Looks like the beta broke my PMDG.

You can opt out of the beta without it messing up your addons. Once you opt out, it will reinstall the old version.

Share this post


Link to post
Share on other sites

Looks like the beta broke my PMDG.

 

...beta of...?

 

...of FSX:SE. Disregard!

 

Yeah, probably not a good idea to opt into betas unless we note that the aircraft is compatible.

Share this post


Link to post
Share on other sites

You can opt out of the beta without it messing up your addons. Once you opt out, it will reinstall the old version.

 

Thanks, I'll try that. I was hoping this beta would be the silver bullet for all the terrain.dll problems.. .but it appears to have caused more problems than solved.

...beta of...?

 

 

Dovetail released an update beta of FSX:SE, that is supposed to heal all the g3d.dll, ntdll.dll and terrain.dll problems people have been experiencing on long flights (VAS management improved with SE, but now they had terrain.dll errors). Because the fsx.exe version is different, it broke compatibility with addons- as well as PMDG aircraft, the 737 being the exception. 

Share this post


Link to post
Share on other sites

The beta runs untill the 16th so there will still be glitches. As mentioned go to the Steam library , right click FSX and opt out of the BETA and the live version will be active and that should give you back your 777

Share this post


Link to post
Share on other sites

You can opt out of the beta without it messing up your addons. Once you opt out, it will reinstall the old version.

 

Yes. I understand, just reporting my results. (PMDG no workee under the beta g3d fix). No matter, FSX SE in not working for me either way. I get a choice between terrain.dll errors or my PMDG stuff doesn't work. FSX Box runs fine so I will just wait out Dovetails work on the repairs. I wouldn't even bother but FSX SE runs so smoothly until the terrain or g3d crash that I really would like to see it work out. That and I love Steam.

Share this post


Link to post
Share on other sites

...beta of...?

 

...of FSX:SE. Disregard!

 

Yeah, probably not a good idea to opt into betas unless we note that the aircraft is compatible.

Tried the new FSUIPC, still no go. This is going to be a huge problem if every time they update FSX, it breaks addons. So far it broke ASN (now fixed with latest BETA) Orbx ObjectFlow.dll is issuing a compatibility message, but still allowing to run, and now this. The big problem is this BETA is slated for only about 9 to 10 days, after that it will be automatically pushed to users. Users won't have the ability to opt out then! I don't know what the ultimate solution will be, but I do know we can't expect the addon developers to continually update their software to work every time DTG wants to update the core app!

 

Tom Cain

Share this post


Link to post
Share on other sites

 

 


Tried the new FSUIPC, still no go. This is going to be a huge problem if every time they update FSX, it breaks addons. So far it broke ASN (now fixed with latest BETA) Orbx ObjectFlow.dll is issuing a compatibility message, but still allowing to run, and now this. The big problem is this BETA is slated for only about 9 to 10 days, after that it will be automatically pushed to users. Users won't have the ability to opt out then! I don't know what the ultimate solution will be, but I do know we can't expect the addon developers to continually update their software to work every time DTG wants to update the core app!

 

Frustrating to be sure. If you wouldn't mind, point everyone you can to the link I posted earlier. They're apparently soliciting comments.

Share this post


Link to post
Share on other sites

I'll confirm my 777 is broken after the beta install.  On the flip side, I was able to get ASN up and working this morning.

Share this post


Link to post
Share on other sites

I have the same issue, updated to the Beta FSX.SE & the 777 don't work. I get black screens & the landing gear don't show so the plane is floating in the air.

 

Waiting for a fix for this soon.

Share this post


Link to post
Share on other sites

I have the same issue, updated to the Beta FSX.SE & the 777 don't work. I get black screens & the landing gear don't show so the plane is floating in the air.

 

Waiting for a fix for this soon.

 

Make a post at the link I referenced above, please. DTG is soliciting comments from people who are having issues with the update.

Share this post


Link to post
Share on other sites

I have the same issue, updated to the Beta FSX.SE & the 777 don't work. I get black screens & the landing gear don't show so the plane is floating in the air.

 

Waiting for a fix for this soon.

See previous post #20) The problem is this Beta is only slated for about another week, so if it's not fixed by then, the update is going to be pushed to all users, and the 777 will become unusable for all FSX-SE users. Not good, and a significant flaw in DTG's/Steam's  business model!

 

Tom Cain

Share this post


Link to post
Share on other sites

Tried the new FSUIPC, still no go. This is going to be a huge problem if every time they update FSX, it breaks addons. So far it broke ASN (now fixed with latest BETA) Orbx ObjectFlow.dll is issuing a compatibility message, but still allowing to run, and now this. The big problem is this BETA is slated for only about 9 to 10 days, after that it will be automatically pushed to users. Users won't have the ability to opt out then! I don't know what the ultimate solution will be, but I do know we can't expect the addon developers to continually update their software to work every time DTG wants to update the core app!

 

Tom Cain

totally agree with that one.

 

I was thinking about starting to move to FSX SE but I found out it probably is not for me:

Only a few of my old scenery addons would work out of the box with Steam.

Getting older addons to work in Steam seems to almost allways require some tinkering and I just dont have the time to tinker with both FSX AND with FSX SE.

 

The good thing about FSX (box) is that it remained unchanged since 2006.

(I know this is not good for VAS etc).

That is why everything we bought years ago still works today.

Just like with Xplane and P3D, the constant updating of FSX SE is both good (performance wise) and bad (compatibility wise).

 

The auto-update feature of FSX SE is a huge problem when it come to compatibility!

 

I thought I would just install FSX and FSX SE side by side on the same PC rather than getting rid of FSX (box).

That would allow me to still use all the addons I have, and at the same time explore Steam.

I would buy only Steam compatible addons then and slowly build and expand on it.

But it seems FSX SE and FSX can bite each other.

And there is no way I am going to sacrifice all the work it took to get a functioning FSX install with various addons for an experiment.

I have read of people having to completely uninstall FSX and manually remove remainders of it to make FSX SE work properly! (sounds like a fresh windows install is the more secure way to go).

I dont know why that is though.....I think P3D and FSX on the same PC is absolutely no problem......so why is Steam different?

 

I already use a multi boot system (two windows 7 installs) so that one Win7 boot can use be used for daily use and the other Win7 boot has only FSX related stuff on it.

So I could create a third boot Win7 install and put FSX SE on that, but that is exspensive.

First I'd have to buy a new harddisk to put Win7 on PLUS, since I want FSX SE installed on a separate SSD (if that is even possible??).........I would also have to buy a new/extra 250-500GB SSD.

So we are talking a few hundred bucks here for the experiment......:-(........hmmm.

 

 

So in the end I think FSX SE is only a real option if

- you are new to flightsim AND if you dont mind that only a few addons are available right now that are compatible out of the "box".

 

or

 

- if you dont mind tinkering and testing and playing/messing around with all those uncompatible addons that are out there untill it works.

 

I think I will wait and see if Aerosoft/ORBX and others will make old addons compatible or not.....(probably not though).

 

Please correct me if I am wrong with my assesment......I would love to be prooven ill informed so I can start exploring/testing Steam!

Share this post


Link to post
Share on other sites

totally agree with that one.

 

I was thinking about starting to move to FSX SE but I found out it probably is not for me:

Only a few of my old scenery addons would work out of the box with Steam.

Getting older addons to work in Steam seems to almost allways require some tinkering and I just dont have the time to tinker with both FSX AND with FSX SE.

 

The good thing about FSX (box) is that it remained unchanged since 2006.

(I know this is not good for VAS etc).

That is why everything we bought years ago still works today.

Just like with Xplane and P3D, the constant updating of FSX SE is both good (performance wise) and bad (compatibility wise).

 

The auto-update feature of FSX SE is a huge problem when it come to compatibility!

 

I thought I would just install FSX and FSX SE side by side on the same PC rather than getting rid of FSX (box).

That would allow me to still use all the addons I have, and at the same time explore Steam.

I would buy only Steam compatible addons then and slowly build and expand on it.

But it seems FSX SE and FSX can bite each other.

And there is no way I am going to sacrifice all the work it took to get a functioning FSX install with various addons for an experiment.

I have read of people having to completely uninstall FSX and manually remove remainders of it to make FSX SE work properly! (sounds like a fresh windows install is the more secure way to go).

I dont know why that is though.....I think P3D and FSX on the same PC is absolutely no problem......so why is Steam different?

 

I already use a multi boot system (two windows 7 installs) so that one Win7 boot can use be used for daily use and the other Win7 boot has only FSX related stuff on it.

So I could create a third boot Win7 install and put FSX SE on that, but that is exspensive.

First I'd have to buy a new harddisk to put Win7 on PLUS, since I want FSX SE installed on a separate SSD (if that is even possible??).........I would also have to buy a new/extra 250-500GB SSD.

So we are talking a few hundred bucks here for the experiment......:-(........hmmm.

 

 

So in the end I think FSX SE is only a real option if

- you are new to flightsim AND if you dont mind that only a few addons are available right now that are compatible out of the "box".

 

or

 

- if you dont mind tinkering and testing and playing/messing around with all those uncompatible addons that are out there untill it works.

 

I think I will wait and see if Aerosoft/ORBX and others will make old addons compatible or not.....(probably not though).

 

Please correct me if I am wrong with my assesment......I would love to be prooven ill informed so I can start exploring/testing Steam!

The way to make steam work out of the box is to NOT have a dual install.

 

The problem lies in the way steam sets up the FSX.cfg to read FSX-se.cfg.........and the the scenery cfg will be scenery-se.cfg  (in a dual install)

 

This causes big problems.

 

A clean install of steam will create an almost identical fsx boxed style set up with a few changes and will have the cfg's read the same as in the boxed version. So you wont have any problems. All of my old add ons work except for the F1 mustang.

 

Using a registry cleaner to get rid of the old box version may not be enough and in my case I had to reformat WIN7 ssd . A big job all up but worth it.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this