Hi Mark,

 

Thanks for that...

My GTN750 is broken. Anyone else?

GTN750 broken has been reported by many on the Steam forums.

 

I had a really strange experience with the update.  The Beta was rock solid and after update I could not get the sim to load.  The aircraft would show up and then after about 15 seconds the sim would crash......Microsoft has detected error, etc.

 

After multiple restarts and tries, I finally was able to load the defaul Baron at a small default airport.  Next I was able to move it to FSDT's KDFW and then finally load up the PMDG NGX.  After that things were fine, I flew on Vatsim (with lots of ATC) to Imaginesim's KATL.  The flight was a bit choppy, has a number of pauses along the way which was unexpected as I had done a full defrag of the drive the night before.  Then landed at KATL and right after I exited the runway I ran out of memory.  The memory part might have been my fault because I really cranked up the sliders and LOD once I got the Beta stable and I had not fully tested it to find out what might happen as a result.

Hi Guys,

 

For your info: Orbx has now fixed the Object Flow update, just reload FSX SE, accept update, run boxes when prompted and your away!

 

Sorted!

 

Cheers,

My GTN750 is broken. Anyone else?

This is an unfortunate consequence of FSX:SE being a moving target. Whenever any add on has to access memory addresses in order to 'hook' into the sim's rendering engine, and a new version changes all of the memory addresses...

 

...the add on developer has to update their product accordingly. It is just that simple. Flight1 have a consistent history of having updates available within a few days though.

Terrain .dll crashes are fixed.

 

Objectflow - You need to download and install the latest ORBX libraries and it will fix this problem.

 

Today instead of getting the Objectflow hasn't been tested message with the option to Run once, when starting FSX-SE that I have been getting since the BETA, I got an update available message, with an update button, and a new objectflow module automatically was updated into FSX-SE. Now no more error messages.

Today instead of getting the Objectflow hasn't been tested message with the option to Run once, when starting FSX-SE that I have been getting since the BETA, I got an update available message, with an update button, and a new objectflow module automatically was updated into FSX-SE. Now no more error messages.

Thats because you fired up the sim after ORBX already updated. I went through the same error messages today until a few hours ago (no beta) when the ORBX fix kicked in

Anyone else getting a crash when loading up a complex aircraft at a payware airport?  PMDG at any FSDT, Aerosoft same thing.  PMDG at Aerosoft Airport.  Appcrash FSUIPC is what is reported in the windows log.  I can load default plane in default airport.

Anyone else getting a crash when loading up a complex aircraft at a payware airport?  PMDG at any FSDT, Aerosoft same thing.  PMDG at Aerosoft Airport.  Appcrash FSUIPC is what is reported in the windows log.  I can load default plane in default airport.

 

If it reports FSUIPC you need to submit the report on my support forum together with the Window crash log details, AND the FSUIPC4 log file from the FS Modules folder.

 

I don't support FSUIPC here.

 

Pete

OK will do when I get home from work.

Steam only installed 2 of the 4 simconnects (as reported now on the Steam forums).  You need to install the other two to fix most of the problems.

 

\STEAM\steamapps\common\FSX\SDK

Steam only installed 2 of the 4 simconnects (as reported now on the Steam forums).  You need to install the other two to fix most of the problems.

 

I'm surprised it installed any other than its own. Must be a change in the latest release, because it didn't use to.

 

FSUIPC is quite happy with any installed version. it just prefers the latest one for the version of FS in which it runs. But I know many add-ons are configured to only use a specific version.

 

Pete

Pete, there was some discussion on the Steam forums about this issue and the developers advised they were planning to include more simconnect version in the final release.  I think most of us took that to mean we did not have to run the simconnects after the update but that may not be the case.

Hi,

 

for the information of anyone flying the Coolsky dc9 , Espen has put out an update that enables the aircraft to work in the new build for FSX SE. Its available to download through the Coolsky forums.

 

Steve

Pete, there was some discussion on the Steam forums about this issue and the developers advised they were planning to include more simconnect version in the final release.  I think most of us took that to mean we did not have to run the simconnects after the update but that may not be the case.

 

Yeah, it was the simconnects.  Installed them and we are all good.

Yeah, it was the simconnects.  Installed them and we are all good.

 

Sorry, I'm confused. Do you mean that installing additional versions of SimConnect "fixed" a crash reported to be in FSUIPC? If so i need to see the details (crash report and Log) as I requested, because FSUIPC should be okay with any version of SimConnect, and should, in fact, be using the Steam version which surely must have been installed.

 

There mst already be a lot of FSX-SE only users who are also sing FSUIPC. I doubt that they have all installed additional SimConnect versions. I certainly didn't initially and all was well. I only needed to install the others for other add-ons.

 

Really, I do need to fix things if there was an FSUIPC crash, so please help.

 

Pete