Sign in to follow this  
pracines

An impressive FSX-SE report

Recommended Posts

Today I decided to put FSX-SE through paces that I would not even try with FSX-MS or P3D V2 unless I cut way back on the sliders. I'm trying to determine what is FSX-SEs' limit as far as when it cant take anymore and crashes.

 

A normally brutal schedule in the default 737-800 from KBOS-KLGA-KPHL-KDCA-KCLT-KMCO-KMIA with 30 min stops at each. Without exiting FSX-SE at all, all day long. No CTD, no OOM, smooth as Crisco butter.

 

The only sliders I cut back on were car traffic at 33, water full left. I keep ground shadows, bloom, and DX10 off. All other settings at MAX and I even used the NVidia Inspector to give me 4x4 AA, 8XSS and limited the FPS to 58.

 

I'm extremely happy to report that I never went under 15 FPS yet always smooth as room temperature Crisco butter. I had only the occasional but hardly noticeable stutter when FS Global Real Weather would update the weather via Network connection.

 

My current PC specs are in my profile. Aside from FS Global Real Weather, I have FSUIPC registered, and the Flight 1 KingAir B200 as the only add-ons installed in FSX-SE so far.   

 

I intend to do days of International flights in the default 747 to only the FSX high detail airports without exiting FSX-SE to see if I can get it to crash. if it lasts for 5 days then I will begin the process of adding all the add-ons I have as they become available.

 

I'm still not going to be totally full of joy until LM or Dovetail get us a simulator that has no VAS limit worries and yet has the performance improvements that FSX-SE has (leaps and bounds over FSX-DVD)....then our PC's can be utilized to their fullest. In the mean time Dovetail has done a very impressive job optimizing FSX-SE for me.

 

Share this post


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

In trying to do the long flight between detailed airports, it seems FSX SE is not up for the task. Even with total vanilla installation and absolutely no adjustments to the settings, and no NVidia setting adjustments, this SE version cant fly for more than 4-6 straight hours. It even CTD's (terrain.dll) over the north pole with default settings. Makes no sense, I tried all kinds of combinations of settings, 3 video drivers, I ran all the legacy simconnect's, on 3 different PC,s (XP, Win7, Win 10), and SE cannot handle long flights.

 

I wonder if the trade off between high FPS and stability is a factor, many others are having this same problem, some CTD faster than others.    

Share this post


Link to post
Share on other sites

It even CTD's (terrain.dll) over the north pole with default settings. Makes no sense, I tried all kinds of combinations of settings, 3 video drivers, I ran all the legacy simconnect's, on 3 different PC,s (XP, Win7, Win 10), and SE cannot handle long flights.

I can confirm this statement. The long haul customer is not going to find this satisfactory. It will be interesting to see if DTG finds this niche customer important enough to warrant addressing the issue. My hopes are squarely upon the shoulders of P3d at present.

Share this post


Link to post
Share on other sites

 

 


It even CTD's (terrain.dll) over the north pole with default settings.

 

I was having sporadic CTDs due to the TERRAIN.DLL - this link may be of interest to you https://steamcommunity.com/app/314160/discussions/1/622954747288223523/

 

Just setting the AffinityMask didn't seem to do it for me (although I went much further before crashing), so I'm trying an optimized FSX.CFG using the Bojote tool. I will try another long-distance trip with the PMDG 747 tomorrow.

Share this post


Link to post
Share on other sites

I can also confirm the terrain dll crash. I had this in regular fsx if my autogen was too high at complex areas. No with SE being so good with vas, I ahve my autogen set at extremely dense. Hopefully DTG can fix this

Share this post


Link to post
Share on other sites

I was having sporadic CTDs due to the TERRAIN.DLL - this link may be of interest to you https://steamcommunity.com/app/314160/discussions/1/622954747288223523/

 

There are two reports on that thread which both point to the same offset in TERRAIN.DLL for the access violation which is occurring. The offset is 00059BE8.

 

No one here has yet posted any details of the crash offset in TERRAIN.DLL, so I don't know if this is the main or only one. If it is a frequent one, then maybe I can implement a temporary workaround in FSUIPC as I did with he most prevalent G3D.DLL crash in FSX. I've had a brief look at the code and I think avoidance action might be feasible, though whatt the graphics results would then be I couldn't say.

 

So, could all of you experiencing this crash please post the actual crash details -- the module offset is really all I need, and confirmation that the error code is C0000005 (= access violation).

 

If I do manage to do anything I'll need a tester who can guarantee to get the crash happening in a reasonable timeframe. I haven't got the time nor patience to wait till something might or might not happen! ;-)

 

[LATER]

Okay. Any registered users who does get (or knows he can get) the Terrain crash at 00059BE8, please try an interim test version -- download link: FSUIPC4938gTEST2.zip. Read the "read me" inside. Let me know how you get on, please.

 

Regards

Pete

Share this post


Link to post
Share on other sites

Pete,

 

- AVsim does not let me paste anything in their forums. I will post under your topic in your forum regarding this terrain.dll error.

 

Thank you for your time.

Share this post


Link to post
Share on other sites

Pete I will start a thread in your forum - AVsim does not let me paste anything in their forums.

 

 

Okay ... thanks.

Pete

Share this post


Link to post
Share on other sites

6 hours into a 7 hour flight, I get a CTD with that terrrain.dll. Just when I was thinking that I'd cracked it with OOMs. So frustrating.

 

Have made that AM adjustment. Let's see if it does the trick. Will try another long flight again, tomorrow.

Share this post


Link to post
Share on other sites

6 hours into a 7 hour flight, I get a CTD with that terrrain.dll. Just when I was thinking that I'd cracked it with OOMs. So frustrating.

 

Have made that AM adjustment. Let's see if it does the trick. Will try another long flight again, tomorrow.

 

If you are a registered FSUIPC user, please try my interim test version -- download link: FSUIPC4938gTEST2.zip. It has what I hope is a "fix" for the specific TERRAIN.DLL crash I've now seen reported three times.

 

Read the "read me" inside. Let me know how you get on, please.

 

Regards

Pete

Share this post


Link to post
Share on other sites

Thanks, Pete. I need to purchase your product but somehow or the other never ever get around to it. Maybe it is high time now.

Share this post


Link to post
Share on other sites

I was having sporadic CTDs due to the TERRAIN.DLL - this link may be of interest to you https://steamcommunity.com/app/314160/discussions/1/622954747288223523/

 

Just setting the AffinityMask didn't seem to do it for me (although I went much further before crashing), so I'm trying an optimized FSX.CFG using the Bojote tool. I will try another long-distance trip with the PMDG 747 tomorrow.

It appears that FSX-SE already sets the affinity mask automatically to 14 for a non-hyperthreded quad-core CPU. It is not necessary to set it specifically in FSX.cfg - doing so only duplicates what is already there.

 

The Virtuali Couatl add-on manager program which is installed with FSDT and FlightBeam airports, GSX etc, has a screen which shows various "tweaks" that have been applied. In FSX-SE, the manager shows an affinity mask has already been set in SE, even though there is no specific AM under [Job Scheduler] in the CFG file.

 

This is NOT the case with original FSX. If no AM is set in FSX.cfg, then no affinity mask entry appears in the Couatl program tweak screen.

Share this post


Link to post
Share on other sites

If you are a registered FSUIPC user, please try my interim test version -- download link: FSUIPC4938gTEST2.zip. It has what I hope is a "fix" for the specific TERRAIN.DLL crash I've now seen reported three times.

 

Read the "read me" inside. Let me know how you get on, please.

 

Regards

Pete

 

Thanks. I just tried test version "g", Win 8.1, DX10, no manual tweaks applied to fsx.cfg, with the default Cessna 172 and OpusFSI for weather. I flew 35 minutes and then CTD:

 

Fault bucket 73744299698, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: fsx.exe
P2: 10.0.62607.0
P3: 548b7186
P4: terrain.dll
P5: 10.0.62607.0
P6: 548b71c0
P7: c0000005
P8: 0008fb36
P9: 
P10: 

Attached files:
C:\Users\Ray\AppData\Local\Temp\WER533B.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_787e3c3aaa805f5f35f47b779a604c5e8cc2e98d_e499c365_190e6721

Analysis symbol: 
Rechecking for solution: 0
Report Id: a8428520-a5cf-11e4-8207-001fbc02953f
Report Status: 0
Hashed bucket: 8385d9586952128eadcf3f7e8eb38004

Faulting application name: fsx.exe, version: 10.0.62607.0, time stamp: 0x548b7186
Faulting module name: terrain.dll, version: 10.0.62607.0, time stamp: 0x548b71c0
Exception code: 0xc0000005
Fault offset: 0x0008fb36
Faulting process id: 0x53c
Faulting application start time: 0x01d039d8fd2e9fd9
Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Program Files (x86)\Steam\steamapps\common\FSX\terrain.dll
Report Id: a8428520-a5cf-11e4-8207-001fbc02953f
Faulting package full name: 
Faulting package-relative application ID: 

The last thing that I did was to try to open the ATC window via a joystick button assigned with FSUIPC.

 

I have been having the same kind of results with both DX9 and DX10 since switching from FSX Gold with which I never had a terrain.dll CTD.  The CTDs have varied from 20 minutes to over 2 hours into the flight. SteamTerrainPatch=Yes was enabled. Im going to try a few more flights later tonight.

 

 

EDIT: Tried having Steam check the integrity of the game cache and then reran FSX-SE. So far so good. I'm going to let it run on autopilot for a hour and see what happens.

Share this post


Link to post
Share on other sites

smooth as Crisco butter.

 

 

Crisco, make butter ???

 

Damn and i've been usnig Oil all this time.

Share this post


Link to post
Share on other sites

i found a 100% reproducible g3d.dll crash it looks like it might be in the same offset each time as well. goes away when i remove ftx england or use the default cessna instead of 777.  (to see the crash take off in 777 from egll, runway 27L compton 3g departure, will blow up within a few nm away from the airport every time.. doesn't happen with FTX global, but does if you enable hybrid or eu region)

 

naturally the only 'real' solution i could find for it was threads pointing to pete's fix from a few years ago hehe. no idea if this is just a matter of patching out each new offset that shows up or what.

 

sorry to hijack on this thread but since pete is lookin at it i figured that was good of of a place as any. help me obi wan dowson, you're my only hope!

 

cheers y'all

-andy crosby

 

--------------------------------

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4
Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd
Exception code: 0xc0000005
Fault offset: 0x000c7c0a
Faulting process id: 0x2844
Faulting application start time: 0x01d039bfc7bde7ea
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\g3d.dll
Report Id: badeb191-a5b4-11e4-889f-e0cb4e2c4e6f
 
Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4
Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd
Exception code: 0xc0000005
Fault offset: 0x000c7c0a
Faulting process id: 0x544
Faulting application start time: 0x01d039bcae2abc2d
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\g3d.dll
Report Id: f307e0bb-a5b2-11e4-889f-e0cb4e2c4e6f
 
Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4
Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd
Exception code: 0xc0000005
Fault offset: 0x000c7c0a
Faulting process id: 0x2730
Faulting application start time: 0x01d0393989215598
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\g3d.dll
Report Id: 3978eabd-a52f-11e4-889f-e0cb4e2c4e6f
 
Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4
Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd
Exception code: 0xc0000005
Fault offset: 0x000c7c0a
Faulting process id: 0xc58
Faulting application start time: 0x01d0393597f60a94
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\g3d.dll
Report Id: 1cf52dd2-a52c-11e4-889f-e0cb4e2c4e6f
 
Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4
Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd
Exception code: 0xc0000005
Fault offset: 0x000c7c0a
Faulting process id: 0xc58
Faulting application start time: 0x01d039316407ef13
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\g3d.dll
Report Id: 685f9133-a527-11e4-889f-e0cb4e2c4e6f
----------------------------------------

Share this post


Link to post
Share on other sites

Thanks, Pete. I need to purchase your product but somehow or the other never ever get around to it. Maybe it is high time now.

 

Don't buy it specifically for this "fix" as I've just learned that it may not work. It might merely succeeds in moving it on a bit. If so, then the corruption is too serious for my simple workaround I'm afraid.

 

for those already registered it might be worth persisting with the fix enabled. See more below.

 

Pete

Thanks. I just tried test version "g", Win 8.1, DX10, no manual tweaks applied to fsx.cfg, with the default Cessna 172 and OpusFSI for weather. I flew 35 minutes and then CTD:

 

You appear to still be using the original FSX-SE release from last December! (build 62607). My fix won't have any chance to work on that. It will only patch into 62608 version Terrain.DLL.

 

How is it you didn't get the update installed?

 

If you run the up-to-date FSX-SE, then it will be still worth keeping the TERRAIN patch enabled in FSUIPC, even though, as I said above, it is looking doubtful that it fixes it. I really won't know until someone does a SUCCESSFUL flight and can check in his FSUIPC4.LOG file that FSUIPC4 did actually trap and stop a TERRAIN crash. (Just search for TERRAIN in the Log file after FSX-SE is closed).

 

Pete

Share this post


Link to post
Share on other sites

This is NOT the case with original FSX. If no AM is set in FSX.cfg, then no affinity mask entry appears in the Couatl program tweak screen.

No, it's the same in FSX. The Affinity mask tweak in the Addon Manager screen will always appear, regardless of the version of the sim or if the settings is present in the FSX.CFG or not.

 

The only difference between FSX and FSX:SE, is the default value used internally by FSX when there's no setting.

 

In FSX, the default value is the same as the OS value, which is "use all cores", which translates into a 15 on a quad core system.

 

In FSX:SE the default is 14, which means "use all cores except the 1st"

 

In the Addon Manager, even in FSX, if there's NO pre-existing entry, the value is 14, but that doesn't mean the tweak is already applied. It only means that IF you press the "Save to FSX" button, 14 is the value that WILL be saved there, and it will used starting on the next restart. We set it to 14 by default (when there's nothing in the FSX.CFG) because it's universally considered to be the best value on a quad-core system but again, is NOT applied until you SAVE the settings.

 

So, the only difference, between FSX and FSX:SE, is the default value used when there is not setting in the FSX.CFG.

Share this post


Link to post
Share on other sites

 

i found a 100% reproducible g3d.dll crash it looks like it might be in the same offset each time as well. goes away when i remove ftx england or use the default cessna instead of 777.  (to see the crash take off in 777 from egll, runway 27L compton 3g departure, will blow up within a few nm away from the airport every time.. doesn't happen with FTX global, but does if you enable hybrid or eu region)

 

naturally the only 'real' solution i could find for it was threads pointing to pete's fix from a few years ago hehe. no idea if this is just a matter of patching out each new offset that shows up or what.

 

It isn't "patching out offsets" but hooking code into them to pre-check a pointer before it is used to make sure it won't crash the system when it is used.

 

Of all the G3D crashes folks had in FSX, there was only one which was patchable in this way. The others were more like the FSX-SE Terrain.DLL crash which I tried to patch and have now found it mrely moves the crash location.

 

However, I'll take a look at your G3D one when I get time. It won't be today I'm afraid.

 

Please report it on the Steam forum as well though.

 

Pete

Share this post


Link to post
Share on other sites

If this terrain.dll error becomes un fixable, it could render SE unusable. I have not done a flight in the 777 yet, so have not pushed any boundary's yet as I have been re installing. I hope I have not just wasted 3 weeks of my life :)

Mind you, I think everyone should make sure you are all on the latest SE version, and you have verified the integrity of game cache if you have to.

Share this post


Link to post
Share on other sites

I've run multiple long flights on FSX-SE without any CTD.

 

The only difference I see is I'm still running somewhat moderate settings and not going to the right on all the settings.  I've also only loaded base global scenery just to ease into it for now.

 

Not sure if that helps but I've had no crashes with the sim in the 777. 

Share this post


Link to post
Share on other sites

 

 


I flew 35 minutes and then CTD:

Just having purchased the full version FSUPIC4 and registered it, this is not good reading. Maybe this will stall simmers from making the switch? So, the new code has still the old code's bugs!


 

 


If this terrain.dll error becomes un fixable, it could render SE unusable.

Julian, you could well be the harbinger of bad news if that happens.

Share this post


Link to post
Share on other sites

 

 


Julian, you could well be the harbinger of bad news if that happens.

Hope not Rick. I will be testing proper on Thursday, and then I will know if a verify game cache fixes the problem.

Share this post


Link to post
Share on other sites

If this terrain.dll error becomes un fixable, it could render SE unusable. 

 

I think that's a rather over the top reaction. There seems to be many more folks flying good and long flights without this crash than with.

 

I don't think it's a new problem with FSX-SE, i think it is just that with the improvements in both performance and VAS usage folks are winding up the settings more, and it is this which is revealing more bugs in the base FSX code similar to those which also caused a lot of the unpatchable crashes in FSX (eg the many G3D ones which FSUIPC did not patch).

 

At least there is a chance (though may be a small one) that given enough evidence DTG could fix this. There was no chance of MS ever fixing it.

 

Pete

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