Gosh, it's intermittent in my FSUIPC logs.

I wonder if it's related to Simconnect? I have occasional GTN750 fails in the A2A 182 but I reset the avionics switch and it comes back.

Yeah. That's a tough lesson when it comes to programming. At least it was for me...finally clicked a while later.

 

Not much you can do about it, though. Bad pointers are all the programmers. So, in that vein the only thing you can do 'personally' is report a bug to someone, but you'd need to track it down a little bit more to figure out who to send the report to.

Kyle, that message comes from a trapping routine that Pete added to FSUIPC a couple of years ago.

 

He discovered that there is one very specific type of G3D crash that can affect FSX, which caused by a bad pointer. G3D can crash for a number of other reasons, but FSUIPC will catch the bad pointer reference in this particular case before it gets passed, preventing the crash.

 

 

He discovered that there is one very specific type of G3D crash that can affect FSX, which caused by a bad pointer. G3D can crash for a number of other reasons, but FSUIPC will catch the bad pointer reference in this particular case before it gets passed, preventing the crash.

 

Interesting - thanks!

So is it bad software or hardware or anybody's guess?

So is it bad software or hardware or anybody's guess?

 

Error in the rendering engine, or how FSX uses it. Nothing you can do to fix it, which is why FSUIPC is taking care of it. Nothing to worry about.

Ok, I have been testing all day.

UK2000's EGNX to UK2000's EGKK.

In the A2A 182.

ASN on

Track IR

GTN750

Saitek yoke, pedals, and quad and TPM.

 

I have been gradually adding things in the scenery library and see very little difference.  If anything I see VAS increase in all three logs as I went on.

 

But in the last two logs I came across this several times scattered throughout the VAS readings.

 

"G3D bad pointer trapped and crash prevented".

 

What does that mean?  I don't have a clue.

 

Thanks.

Maybe something you added started the pointer error. Why not backtrack, undo the last few additions until you get an error free sim.

 

It's not "fixed" by FSUIPC, the sim is simply saved from crashing. It's possible memory is lost (not given back) and available VAS will decrease, and there's a possibility of other problems too.

It's strange. I was testing VAS by adding back in IOM and Geurnsey.

It shows in some but not all.

I am going to FSUIPC log every flight and see if it shows on every flight.

If it does then I have no idea.

Well, it's possible that nothing comes of it after FSUIPC catches the exception. At least you know it's there.

Well here's the deal.

I made four FSUIPC logged flights.

Same parameters and I typed in notes at the top of each log to remind me of what I did.

Before any flights however I did this:

 

1. I disabled ALL Earth Simulations Isle Of Man and Guernsey entries in the FSX scenery library.

2. Then I installed UK2000's East Mids Extreme as I have the Q400 Airline2Sim videos and wanted that nice scenery.

 

All flights have this in common:

 

A2A 182 with the GTN750 fitted.

ASN on

Summer, (I know it's winter but I like the summer ORBX textures)

Track IR

ORBX ALL UK products except for a handful of airports.

ORBX Global

ORBX Trees

EGNX to EGKK

GSX on landing to use follow me truck to the same exact stand.

All done for VAS checks.

 

Flight 1 - I had ten *** G3D bad pointer trapped and crash prevented ***.

Flight 2 - Now all I did was to ENABLE the Ratcliff power station and install service fleet at EGNX - ZERO G3D's

Flight 3 - Enabled ALL Earth Simulation entries in the scenery library but this time I was 49 miles out from EGKK and the screen went blank for a second or two and I lost the GTN750.  Had to cycle the avionics switch and got it back.  This happens occasionally in the 182 and the Real Air Duke Turbine.  All cores on all planes the same for the GTN750. - I had seven G3D's.

Flight 4 - Installed and registered the newest FSUIPC and rebooted.  Same parameters - ONE G3D error.

 

So, there's no seeming rhyme or reason to it.

 

And curiously VAS stayed about the same throughout.  I was left with an average 2991522 Monitor IPC:024C (S32) = 667012

 

By the way, I REALLY appreciate all the time and effort you guys have spent in reading this stuff and explaining it to me.  If nothing else I have learned a lot.

 

So it would seem that this has probably been happening all along and I never noticed it until I learned how to use an FSUIPC log.

 

Thank you all.

 

 

So it would seem that this has probably been happening all along and I never noticed it until I learned how to use an FSUIPC log.

 

That would be my guess.

I wonder how common this is Kyle?

I wonder how common this is Kyle?

 

Dunno. If it's a programmed function into a tool that supports Flight Sim and Prepar3D, it must be common enough.

 

As I've been saying though: it's probably best to let this one go and let FSUIPC do its thing.

Dunno. If it's a programmed function into a tool that supports Flight Sim and Prepar3D, it must be common enough.

 

As I've been saying though: it's probably best to let this one go and let FSUIPC do its thing.

Yup, that's exactly what I am going to do.  This was only discovered during VAS testing.

 

Cheers.

So, I am going to set up this FSUIPC monitoring, since I am crashing constantly after about 10 minutes. But when I get the warning and see that VAS is low..... what can I do about it? Anything, or is this just a heads-up, "hey, you are about to crash" notification?

4 hours ago, Jonathan Bate said:

So, I am going to set up this FSUIPC monitoring, since I am crashing constantly after about 10 minutes. But when I get the warning and see that VAS is low..... what can I do about it? Anything, or is this just a heads-up, "hey, you are about to crash" notification?

You can pause the sim and save the flight before it crashes. You will then be able to restart FSX, load the saved flight and continue with VAS usage restore to normal.