Reaching out for help with PAC 750 problem

[LouP]

So, I opened a ticket with Orbx but nobody is getting back to me. I have a problem where the PAC 750 cargo variant is causing msfs to CTD. The passenger version works fine though. Does anyone have any idea what might be different between these to variants that might cause this?

Thanks,
LouP

 

[Wing_Z]

It's going to be a third-party addon that's hurting you.
I loaded all 4 variants: pax, cargo, agri + skydive.
All worked fine.
This at least removes some of the possibilities.

If Orbx becomes live, please ask them to put in the cropduster effects

 

[DennyA]

OrbX hasn't touched the 750 in forever, which makes me think that something else must have gotten an update that's conflicting with the cargo variant.

The files haven't been touched since 2023 (annoying given the promises uptopic of updates), so it's something else that changed, not the plane.

If you're using Addons Linker, turn off everything else, clear the rolling cache, and see if the plane loads for you. (If not using addons linker, temporarily remove all of your other add-ons, and realize why you should use Addons Linker. )

 

[LouP]

Thanks for getting back to me. Orbx finally responded and in addition to clearing the cache files they suggested trying to clear all of the .dat files which I'm testing right now. I'll let you know how it turns out. There is another user on the flight simulator forums having this exact same issue, so I am not alone.

LouP

 

[LouP]

Just for the record, that didn't work. It has to be a conflict with an Asobo update. I have a bad feeling I just won't be able to use the cargo variant again.

LouP

 

[DennyA]

It's very unlikely an Asobo update issue, as I have every Asobo add-on installed and up-to-date, and I just took the cargo version for a successful flight in FS2020. Not denying you and the other poster on the main forum are having issues, but I just flew the Cargo version, with all of my usual add-ons active, and had no problems. So I'm guessing a conflict with another add-on that was updated, or a corrupted file.





Along with deleting the PAC750 and reinstalling it, and temporarily disabling any other add-ons, I'd also suggest running Corsten's cache clear utility, which will zap MSFS and video driver caches and help ensure it's not a corrupted cache file causing the problem.

Corsten´s cache & shader removal tool (2024) for Microsoft Flight Simulator | MSFS

✓ Corsten´s cache & shader removal tool (2024) is a Microsoft Flight Simulator 2020 mod created by Corsten. A tool designed to clean MSFS and GPU shader cache, improving performance by removing outdated or incompatible cache files. Use with caution and follow instructions carefully to ensure...

flightsim.to

 

[DennyA]

Also, I had trouble with Corsten's removal scripts on my system (it gives me permission errors) so mainly I was thinking potential problems could be the rolling cache (you can clear in in MSFS) and the SimObjects cache.

To clear the latter, open this folder:
C:\Users\[YOURUSERNAME]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SimObjects\Airplanes

...and delete all the contents. MSFS will rebuild the cache, so you won't lose anything.

 

[LouP]

Hi Denny,

I was sure this was going to work but ctd again. I am going to try and manually delete the cache folder the tool deletes as I was also getting permission issues.

LouP

 

[LouP]

Hey Denny, does this mean anything to you? I pulled it from the Windows event viewer.

Faulting application name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000013885db
Faulting process id: 0x0x58A4
Faulting application start time: 0x0x1DB67BD755E068F
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: e718b273-1b79-4b2e-9f30-54cfd62f31c8
Faulting package full name: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Lou