Jump to content

Archived

This topic is now archived and is closed to further replies.

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

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.


Ryan Kelly

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.


Stevan Makarevich

 

cherokee180.gif

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


Win10: 2004 19041.264
CPU: 9900KS at 5.5GHz
Memory: 32Gb at 3900 MHz.
GPU:  RTX 24Gb Titan
2 x 2160p projectors at 30Hz onto 200 FOV curved screen

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


Win10: 2004 19041.264
CPU: 9900KS at 5.5GHz
Memory: 32Gb at 3900 MHz.
GPU:  RTX 24Gb Titan
2 x 2160p projectors at 30Hz onto 200 FOV curved screen

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.


Rick Almeida

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


Win10: 2004 19041.264
CPU: 9900KS at 5.5GHz
Memory: 32Gb at 3900 MHz.
GPU:  RTX 24Gb Titan
2 x 2160p projectors at 30Hz onto 200 FOV curved screen

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.


Rick Almeida

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.


Jim Barrett

Licensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.

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

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    18%
    $4,640.00 of $25,000.00 Donate Now
×
×
  • Create New...