Anyone else suffering from these in FSXSE?

 

I've had quite a few of the g3d related ones and thought they were due to FSUIPC not including the g3d fix, but Pete Dowson said that the crash signature in FSXSE in unrelated to the one he fixed in FSXMS.

 

There are two threads in the Steam forum about these crashes (here and here) and the most interesting thing about them is what has seemed to fixed it for some, if not most: Running Bojote's fsx.cfg tweak tool.

 

(Except in the first thread where FTX England seemed to be the culprit.)

 

 

I've tried this solution myself and reflew the flight that crapped out on me the last time. No crash, nothing.

 

 

Things I've added to the fsx.cfg:

 

 

[GRAPHICS]

HIGHMEMFIX=1*

[DISPLAY]

TextureMaxLoad=30

[TERRAIN]

SWAP_WAIT_TIMEOUT=2

[sOUND]

SOUND_LOD=1

[sCENERY]

MAX_ASYNC_BATCHING_JOBS=3
SmallPartRejectRadius=1

 

*Superfluous for FSXSE as it is supposed to be default. One Steam user also reports the crash happened despite the fix being present in his/her config file.

 

 

One of the other ones is either the magic bullet or a damn good placebo.

 

 

So if anyone has the same problem and is able to reliably reproduce it, could he/she add these tweaks one by one and see which one made the decisive difference?

Other than that, feel free to discuss it further.

For comparison to the tweaks added or modified by the Bojote tool, below are my FSX-SE settings as shown on the main screen of the Virtuali add-on manager. The manager will be present on any FSX or FSX-SE installation which has FSDT or FlightBeam airports, or the Quality Wings 757, and does give some insight into applied tweaks. The manager can also be used to modify the FSX.CFG graphically, rather than by editing the file with Notepad.

 

Many of these settings appear to be defaults, or otherwise "baked into" the FSX-SE main executable, though I assume that most can be over-ridden by specific entries in FSX.CFG

 

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL = 4500

 

TERRAIN_MAX_AUOGEN_BUILDINGS_PER_CELL = 3000

 

FIBER_FRAME_TIME_FRACTION = 0.33 (Same as default FSX I believe)

 

TEXTURE_BANDWIDTH_MULT = 160 (This one is explicitly set in the SE FSX.CFG)

 

UsePools = 1

 

PoolSIze = 5 MB

 

SmallPartRejectRadius =1

 

HIGHMEMFIX = 1

 

AffinityMask = 14 (Appears to be set automatically - this is the correct setting for my quad-core non-hyperthreaded CPU)

 

SWAP_WAIT_TIMEOUT = 10

 

TextureMaxLoad = 6

 

TEXTURE_MAX_LOAD = 4096 (Explicitly set in the config file)

 

ForceFullScreenVSync = 1

 

Interestingly, though I operate in windowed mode, not full screen, and do not  have VSync set in NVidia Inspector, I, have absolutely no screen tearing when panning views in FSX-SE.

 

I have about 30 hours with SE. So far, I have had the terrain.dll crash only once. Strangely, it happened over the open ocean, just off of the southern tip of Greenland, about midway through what had been planned as a 9-hour flight from EGSS to KMEM in the PMDG MD-11F. I had over 2 GB of free VAS at the time of the crash.

 

Not sure if the Bojote config tool actually does do something to prevent the terrain.dll / G3D crashes, or if it the placebo effect. Some of his tweaks are the same as default FSX-SE, others are different - specifically SWAP_WAIT_TIMEOUT and TextureMaxLoad. (Which is not to be confused with TEXTURE_MAX_LOAD!)

Just got a - guess what - g3d.dll related crash while background loading a flight at JFK.

 

FSXSE does seem to be quite a bit unstable...

I moved this back to FSX/FSX-SE forum so that you might get more input as it appears to be an issue with just FSX-SE.

 

Best regards,

I will test these changes, but I can not find the FSX-SE Cfg.file? 

Thanks   :wub:

Have not received these errors, but I installed SE on a fresh installation. Not sure if that has to do with it but i wanted a clean install to test.

I moved this back to FSX/FSX-SE forum so that you might get more input as it appears to be an issue with just FSX-SE.

 

Best regards,

 

Umm...where was this thread before?

 

I faintly remember starting it in the FSX forum...

 

 

 

I will test these changes, but I can not find the FSX-SE Cfg.file? 

Thanks   :wub:

 

Oh come on, Ahmed...

 

https://www.google.de/search?q=fsx+steam+fsx.cfg

 

Fourth one down.

 

 

 

Have not received these errors, but I installed SE on a fresh installation. Not sure if that has to do with it but i wanted a clean install to test.

 

My installation is "fresh" as well.

 

 

I hope that the recent update improves matters, but I fear that it won't.

Ah, I have experienced this crash.

 

I've consistently had reproduced this crash while crossing North Atlantic westbound. Terrain.dll v. 10.0.62608 which is in the newest patch. Interesting...I wonder why terrain.dll of all modules will crash at some random point over the blue ocean lol. Time to submit a bug report to DoveTail.

Just got a - guess what - g3d.dll related crash while background loading a flight at JFK.

 

FSXSE does seem to be quite a bit unstable...

Bjeorn, if you're still having this issue, have you tried Steam's Verify Integrity of Game Cache?

 

I had developed issues with FSX-SE, which was running like a champ for a couple of weeks, after I had performed installs of other non-flight sim applications (music notation app., virtual instrument libraries, and a audio mixing app.). Yesterday, I performed this Steam feature, where it identified and fix over 40 "corrupted" files, and the issue stopped.

 

One thing to note if you use the DX10 Fixer app - after performing the Steam feature, it is necessary to use the DX10 fixer to uninstall the libraries and then install them again. Last, none of my FSX user files (FSX.CFG, DLL.XML, EXE.XML) were altered by the Steam feature.

 

The Steam feature has saved me in the past with games I had heavily modded (Oblivion, Fallout 3, Fallout NV, and Skyrim).

Bjeorn,

I found it...Thx 

 

I have about 30 hours with SE. So far, I have had the terrain.dll crash only once. Strangely, it happened over the open ocean, just off of the southern tip of Greenland, about midway through what had been planned as a 9-hour flight from EGSS to KMEM in the PMDG MD-11F. I had over 2 GB of free VAS at the time of the crash.

 

Heh, that's exactly where I got my CTD. Just off the southern tip of Greenland.

Heh, that's exactly where I got my CTD. Just off the southern tip of Greenland.

Interesting! Looks like there may be a glitch in a scenery file in that area. FWIW, I run Pilots's FS Global Ultimate terrain mesh, ORBX Global Base 1.30 textures, and ORBX Vector 1.20.

 

When I had the crash, the Windows event viewer logged an error in both terrain.dll and G3D.dll. I believe both dlls were updated in the FSX-SE update just released. I'll have to re-visit that area and see if there is still an issue

I had this problem with a box version of fsx. Wiped hard drive, installed everything all over, and now on exit I get instead of a g3d.dll crash, a kernel32.dll crash. It only happens when I quit, so at least I can fly. I'd suggest a new windows install then try from scratch. I made the mistake of adding other addons too fast and now I do not know what caused it.

Original FSX was prone to a certain type of G3D crash caused (possibly) by a bug in the graphics engine. Pete Dowson was able to add the ability to detect that one type of G3D instability to later versions of FSUIPC and prevent the crash before it happened. But that crash-prevention routine no longer works, because the new FSX-SE internal code has changed.

 

I do know from reading the FSX forums at the Steam web site, that the terrain/G3D.dll crashes have been quite common in FSX-SE by users running a broad variety of systems, with and without add-ons, so it may be a new bug specific to SE. Both dlls were updated in the new SE build, so I guess time will tell...

Bjeorn, if you're still having this issue, have you tried Steam's Verify Integrity of Game Cache?

 

TBH, shooting little green men into space (and recovering them) is much more interesting at the moment.

 

I know about that function, but did not try it as it will inevitably overwrite default files modified by me or add-ons.

 

 

 

I believe both dlls were updated in the FSX-SE update just released. I'll have to re-visit that area and see if there is still an issue

 

Yup, both .dlls seem to be updated. Fingers crossed...