Sorry for gatecrashing your topic @Drumcode. I've tried my test flight 6 times this morning and cannot get P3D to crash. Even used the same time as yesterday's crash but still it works. Frustrating isn't the word. Still on v4.5.

just having a read through...as you do..not that im having these probs as i dont use ai yet...but:

If you test today at the same time, nothing happens , all good, great.

But if you have a bad Ai plane...that only gets used on a tuesday, you wont see a crash untill next tuesday...if you follow..(that particular airline may not fly there more than once a week...)

....just an observation from reading the thread....i have no experience with the programs.

After 6 successful tests with the scenario that crashed yesterday I setup a new flight from EGLL to EHAM. Taxied out and lined up on 27R. On rotation the sim crashed. Looking at Event Viewer the reports show what happened in sequence...

11:57:24

Application: PREPAR3D.EXE
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFF0C7B11F8
Stack:

11:57:26

Faulting application name: PREPAR3D.EXE, version: 4.5.12.30293, time stamp: 0x5cd47aad
Faulting module name: FSUIPC5.dll, version: 5.1.5.1, time stamp: 0x5ce4055a
Exception code: 0xc0000005
Fault offset: 0x00000000000e11f8
Faulting process ID: 0xff0
Faulting application start time: 0x01d516082b1b1d1a
Faulting application path: D:\P3Dv4\PREPAR3D.EXE
Faulting module path: D:\P3Dv4\Modules\FSUIPC5.dll
Report ID: e9fe369f-f2e6-4e9a-8461-7fd94e909d99
Faulting package full name:
Faulting package-relative application ID:

11:57:29

Faulting application name: PREPAR3D.EXE, version: 4.5.12.30293, time stamp: 0x5cd47aad
Faulting module name: FSUIPC5.dll, version: 5.1.5.1, time stamp: 0x5ce4055a
Exception code: 0xc000041d
Fault offset: 0x00000000000e11f8
Faulting process ID: 0xff0
Faulting application start time: 0x01d516082b1b1d1a
Faulting application path: D:\P3Dv4\PREPAR3D.EXE
Faulting module path: D:\P3Dv4\Modules\FSUIPC5.dll
Report ID: b0d2595a-b1f0-4ead-832d-34d9890080e6
Faulting package full name:
Faulting package-relative application ID:

So whilst FSUIPC5 may look like the problem it isn't because it was caused by a .NET runtime 1026 error.

I've spoken to Pete and he suggests reverting to 4.4, deleting shaders and trying the tests again. Doing that now.

Luke, I tested at exactly the same time as the crash yesterday. Good idea but probably not a bad Ai texture/

Edited May 29, 20197 yr by Ray Proudfoot

@Ray Proudfoot Just curious, right before it crashes, do you hear like 3 or 4 break ups of P3D sound? I did, every time. I reverted back to 4.4 yesterday, but did not have the time to actually do a flight yet. I hope we can all get to the bottom of it, as I really like how they improved the night lights and the DL.

Edited May 29, 20197 yr by Drumcode

48 minutes ago, Drumcode said:

@Ray Proudfoot Just curious, right before it crashes, do you hear like 3 or 4 break ups of P3D sound? I did, every time. I reverted back to 4.4 yesterday, but did not have the time to actually do a flight yet. I hope we can all get to the bottom of it, as I really like how they improved the night lights and the DL.

Yes I did. Certainly some break in the sound but the crash comes so quickly nothing lasts long. I reverted to 4.4 and flew EGCC-EGLL and no crash on approach (unlike yesterday) so I'm staying with 4.4 for now.

6 hours ago, Ray Proudfoot said:

Yes, I have the AIG Ai. I haven't tried a flight without it yet. I'll be constructing a series of tests today to try and establish where the problem lies. I will stick to 4.5 and use 100% AIG Ai for the first test at EGLL. If it crashes then repeat with 50% of the BGLs. If it still crashes then substitute those 50% with the other 50% just in case it's a bad BGL.

Incidentally, please state what build of P3D you're using and what the crash type was. MIne are KERNELBASE.dll with 4.5.

Hi Ray 

Using v4.5.12.30293. Just checked my event viewer from last night and I have the exact same 3 errors reported as you with the same exception codes.

Unfortunately I’m not in a position to revert, so I’ll have to make do without AI for now 😟 but I’ll keep doing some more testing 

Regards

G

Annoyingly I’ve been using AppCrashView to access information about crashes and the .net error doesn’t show in that...

Edited May 29, 20197 yr by Gandalf

@Gandalf, that's encouraging. What position was your aircraft in when it happened? Distance from arrival airport would be a start. was it a busy airport taxing the system?

No, I was flying from EGKK-LEAL, both default airports as I’m trying to keep add ons at the absolute minimum while this is happening.

Crashed about 160 miles from LEAL at FL 370...

So very different circumstances to mine. I don't suppose you have autosave enabled? If so, try loading the last saved flight before the crash and see if you can reproduce it.

Had another crash at EGLL on take-off roll with v4.4. KERNELBASE one this time. I'm going to disable AIG Ai and switch back to UT LIve. No other changes. If no further crashes then AIG has to be suspect. Finding which aircraft should be fun! 🙄

Edited May 30, 20197 yr by Ray Proudfoot

Strangely I did my usual flight from egkk-Leal last night with AIM OCI but no Radar Contact and didn’t have a crash. Wasn’t going to mention it until I’d tried it a couple more times... 😉

Ill have another go this evening, once the cricket’s finished... 🙂

Which fsuipc dll were you using? Haven’t downloaded the ‘b’ version yet

Regards

G (or Q 😁)

Remember I tested the same scenario 6 times yesterday at EGLL without it crashing. Difficult to get consistency even with saved flight. Yes, still on the b variant of FSUIPC5.

My flight to EHAM was fine with UT Live traffic. All I can do is continue for several days without AIG and if no crashes then it has to be suspect. All test flights will be out of EGLL as that is the one airport I cannot successfully depart from.

All the b version does is provide offsets for airborne and ground Ai to be counted.

I reverted back to 4.4 and CTD on descent to Denver, with FSUIPC error in the event viewer. Does any of you use military AI by any chance?

2 hours ago, Drumcode said:

I reverted back to 4.4 and CTD on descent to Denver, with FSUIPC error in the event viewer. Does any of you use military AI by any chance?

Not that I’m aware of. I haven’t installed any via AIM OCI....

3 hours ago, Drumcode said:

I reverted back to 4.4 and CTD on descent to Denver, with FSUIPC error in the event viewer. Does any of you use military AI by any chance?

Yes, I have the military option selected. Do you suspect that?

Check Event Viewer. Was there another error a few seconds before the FSUIPC one?