Prepar3D Forums

Hello,

Some unusual behaviour has been reported whereby individual content errors are being reported via message boxes when the vehicle in question is selected in Prepar3Dv4, irrespective of whether content error reporting is enabled in the UI.

Does anyone have any idea of what mechanism could be behind this? My assumption is a third-party application, but I've been unable to identify which one.

An image showing the message box can be seen here.

Thanks
Nick

Nick,

P3D startup, gauge error.

Which aircraft did you select?

Hello Vaughan,

The aircraft is the A2A 172 (I work for A2A). It's not the gauge error itself that's the mystery, but rather what's causing them to be presented as individual message boxes to this one customer.

As far as I'm aware, P3D will only write them to a logfile if content error reporting is enabled.

Thanks,
Nick

Nick M wrote: ↑Thu Feb 20, 2020 6:52 pm Hello Vaughan,

The aircraft is the A2A 172 (I work for A2A). It's not the gauge error itself that's the mystery, but rather what's causing them to be presented as individual message boxes to this one customer.

As far as I'm aware, P3D will only write them to a logfile if content error reporting is enabled.

Thanks,
Nick

Do you see the error in the log file also?

Yes, the error is a valid one but the customer reports the message boxes appear irrespective of whether content error reporting is enabled in the UI.

Thanks,
Nick

Nick,

Have you seen this in your in-house or beta testing?

No, we haven't seen content errors being presented in this fashion, only written to the logfile. This is why I suspect it's some third-party software which is flagging them individually as message boxes.

Nick,

Possibly having the user go through all the General Debugging Steps could help find it.

The user is having to click on each message box individually (one for each content error) to accept them.

None of the information I can find on content error reporting references anything other than them being written to the logfile.

Thanks,
Nick

Do you have "MissingLibraryAlert=1" or "ShowMissingTextureAlert=1" in your Prepar3D.cfg?

Hello ananda,

I did actually try adding these entries (they go in the [SCENERY] section I believe?) to see if this allowed me to replicate the behaviour this user is reporting, but without success.

So I don't think these entries would be causing the issue, and I doubt they're present for this person anyway. (They must be manually added I understand.)

Thanks,
Nick