GiaMag411

I'm afraid that this is the only way to make it possible to fly in America. Since I've been tweaking FSX for years now, have a low-medium spec PC even for FSX and this is the first time I've ran into an issue that feels unsolvable, I may as well leave it as it is. I have tons of aircraft, textures, scenery and tweaks that would be lost unfortunately and would take lots of time to set everything up again, so I guess I'll have to live with it until a PC upgrade or something.

 

Once again, thanks everyone for your help

Default ai_player.dll, got the default NAMC, NAME, NAMW and SAME folders, still no luck. At this point I may as well give up and simply avoid America :(.

Thanks again, I will try installing FSX on a new PC, grab some default files from there and see how it goes.

 

Q1: Can a bad AI aircraft cause CTDs all over a continent with traffic sliders set at 0?

Q2: How can a bad flight plan cause CTD all over a continent?

When testing I only select aircraft, location, time and weather. No AI traffic, no flight plan or anything.

 

Will try getting the ai_player.dll and maybe a few scenery files from a clean installation and will report back.

Thanks everyone for your info, really appreciate it. Back in my PC, tried it again, still same error.

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: ai_player.dll, version: 10.0.61637.0, time stamp: 0x46fadb57

Exception code: 0xc0000005

Fault offset: 0x00037519

Faulting process id: 0x17bc

Faulting application start time: 0x01d81999e052d417

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll

Report Id: 7655298b-60a5-4608-9049-c6df45087bae

Faulting package full name:

Faulting package-relative application ID:

 

I hope I won't have to reinstall FSX from scratch. (Or maybe just avoid America?)

With all addons removed from the Scenery Library, I managed to get what I assume is still the same CTD, and was producing almost every time an error, with the same fsx.exe (obviously), same faulting module, the 'ai_player.dll', same exception code etc. With the scenery addons enabled, I get no event / error report. Here is the latest one from yesterday.

 

 

Error from Event Viewer:

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: ai_player.dll, version: 10.0.61637.0, time stamp: 0x46fadb57

Exception code: 0xc0000005

Fault offset: 0x00037399

Faulting process id: 0x3aa8

Faulting application start time: 0x01d80a33f0443cd4

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll

Report Id: 5b3063d6-a1ac-4ea6-b0ea-daa34e6071b2

Faulting package full name:

Faulting package-relative application ID:

I was afraid it may be related to the GPU, but still could not come up with a reason that the issues would be highly region-specific. Flickering has never been an issue like in the showcase video, preventing normal flight, anywhere else in the world (I fly in EU, never had such an issue). Will try running lower settings when able and see if the flickering goes away (in case there is no permanent damage to the GPU). The CTDs all over America though, I still cannot explain. Feels like a certain range of Longitude is a no-go.

Hello everyone, I'm having an issue with FSX in the American continent and I'm at my wits end.

 

Since the last few days I have been trying to spawn at airports in central and eastern NA. For

some reason, I get CTDs right after loading the flight completes. Instead of 'spawning', after

loading completes screen continues staying black, program switches to "Not Responding"

state for a couple of minutes until I eventually get a CTD. Western US works just fine, as

does the EU and every other region. The thing is that this does not leave any info regarding

the error in the Event Viewer. Downloaded AppCrashView just in case, still nothing. Tried

searching my 'Addon Scenery' directory, as well as Scenery/Global and World for any recent

changes, did not find anything suspicious.

 

I have a big list of addons installed, including GEX previously, then ORBX OLC and UTX. (Can't

think of any others that would have such a large scale impact on the FSX world). To note, I've

had these for quite some time and remember just a few months ago testing some addon airports

like KJFK, KBOS, CYUL, CYQX etc and remember everything working fine. Have not installed

anything America related in the last few months at least. I've been troubleshooting the sim

here and there for a long time, but this time I am just clueless. I can't even get near NA

central and eastern regions, not even Greenland. Tried more testing, turns out that the whole

American continent is producing instant CTDs. The only places that don't are the west coast

of the US (Alaska, Washington etc.) until down at NW Mexico. South America doesn't work

at all. The only thing I did a month ago that potentially could have messed with some files

was do some scans with IObit System Care and cleaned my registry.

 

I also did the following experiment: Spawned with the CLS 747-200 (relatively FPS-friendly)

at Boeing Field in Seattle, no issues. Attemted to take-off, climb to a flight level and just

head East (HDG about 100deg). Initially, all ok, as I started to close in on the problematic

region of NA, I started getting some very weird flickering within the sim, rest of PC was ok.

The closer I got, the flickering got more intense, and after about 1h30m of flight time, I got

a CTD again. I posted a relevant video on YT just in case anyone is interested to see what I

mean. As you can see, when the direction of view is towards the (probably) problematic areas,

flickering intensifies. Also when zooming in as well. Tried the same with Aerosoft F-16: No

flickering this time, but still get the same CTD, with the Captain Sim 727, same as with F-16.

Similar weird texture flickering occurs on other things as well and anywhere in the world,

not with this intensity though, (e.g. AI cars occasionally) so this may be a problem to

solve some other time.

 

After playing with the installed addons in the Scenery Library, my crashes now mainly generate

errors with the faulting module reported as being the ai_player.dll. Btw, I have AI aircraft

traffic disabled since I mainly fly on vatsim, I previously had WOAI but still problem free.

 

Also tried renaming the fsx.cfg, scenery.cfg and dll.xml, still no luck.

 

I understand this may be quite rare since I haven't really found anything similar around.

Any info would be greatly appreciated, probably from someone that has ran into this already,

thank you in advance. I will not have access to my PC for the next 20-ish days, waiting for

any suggestion to try out when able.

 

- Windows 10

- CPU: AMD Ryzen 3 1200

- GPU: AMD Radeon RX 550 (with boosted performance from 'AMD Radeon Software')

- FSX Gold Edition

- DX10 Steeve Fixer

- Many WOAI Aircraft Models

- ORBX Open LC 1.30

- ORBX Global 1.40

- ORBX Vector 1.51

- UTX

- ReShade with SweetFX

 

Link to video with flickering (the first minute should be enough to showcase the issue):

Not really the issue so no need to disable. Issue was in the contact points and, as said above, was fixed. Fuselage shaking works just fine.

Update: Issue Fixed.

 

It seems that it was an issue in the aircraft.cfg. After some thinking I decided to have a closer look at what I initially suspected to be the root of the problem, the contact points. The body gear contact points had a max limit of -13 deg steer angle, with the nose wheel at 70 deg. Perfectly normal in reality, but FSX does not handle well the body gear steering as it it is set via the contact points. It probably detects that the body gear, instead of helping out the turn, block it, as they have to be dragged by the aircraft while at an angle, thus working like brakes. Reducing that -13 deg setting to -0.xx removed it. The -0.xx is a non zero value so that there is still some resistance on tight turns, although minor. Personally somewhere around -0.2/-0.5 was ok.

- FSX Acceleration (Golden Edition)

- I use ezdok v2

 

Not sure how these could be related though. In general, this plane has many issues so I wouldn't be surprised if this was one of them with no apparent solution. Every other plane has worked perfectly fine (E.g. Wilco 737 v2 which is what I mainly use).

So I have decided to take this old aircraft for a spin after a while and noticed this:

 

While taxiing, the aircraft resists the turns. When I try to turn, the aircraft brakes so much that you have to add thrust - a lot of thrust - to turn around (60% N1 for the tightest turn), which is obviously unrealistic. The aircraft supposedly has body gear steering, although the corresponding switches don't exist due to low system depth, so it is active all the time. It's not that I care a lot about this, but I'm really curious since I've never ran into a similar problem with any other aircraft I've ever used.

 

Any idea what it could be causing this and, if possible, disable the said setting from? Has anyone encountered such a problem before?

 

(Sorry if this has already been answered sometime, but didn't manage to find anything related)