Option to suppress all warnings and errors.

[TheDeadlyShoe]

yeah npr sensors can be weird.

in my intelligence screen i noticed a 200kt swarm mothership that had a str 0.00000000023928398 or somewhere therabouts strength sensor on it (as well as the one that works)

[Steve Walmsley]

Yes, NPR ships with massive active sensors cause an error.   I don't have the detailed error message (I can get the detailed error later on tonight) but here is a comment from the 6.4 bug thread I made.   


"I found some NPR ships with the following sensors:
Active Search Sensor MR1737-R97
Active Search Sensor MR2481-R97

When I deleted them the errors stopped."

This particular error fires quite frequently...one pop up per ship per increment.

I've fixed this for v6.50

[SteelChicken]

I've fixed this for v6.50

QAPLA!

[HavingPhun (OP)]

There are a couple of issues with this proposal.

1) There are some errors you can easily fix (and in fact have to fix or the game will continue to have short increments giving you the same error every time), or have known workarounds.  There is no way for the game to know which errors you can easily fix and therefore only show those
2) Some errors, especially data access ones, result in an endless series of error 91s (Microsoft error codes).  With no popups, the game will simply hang for no apparent reason.

Obviously the ideal is to have no popup errors.  My current campaign has had only one so far, connected with the Check All Pops option, which is now fixed If you do have errors though, read the message and report them so I can fix them for the next version.

Ah well, I had hoped the second bit wasn't the case.  Thanks for the reply.

[TT]

I logged in to the forum to recommend this very thing after doing about an hour and a half at 15 second increments with "GetMaxPotentialSensorRange" errors (error number 6) four times in each turn resolution. This appears to be NPRs fighting it out and the error messages keep you from auto turning your way out of the NPR skirmish. So let me add my vote to HavingPhun's fine suggestion.

[SteelChicken]

I logged in to the forum to recommend this very thing after doing about an hour and a half at 15 second increments with "GetMaxPotentialSensorRange" errors (error number 6) four times in each turn resolution. This appears to be NPRs fighting it out and the error messages keep you from auto turning your way out of the NPR skirmish. So let me add my vote to HavingPhun's fine suggestion.

Sounds like Steve fixed this for 6.5

[TT]

Sounds like Steve fixed this for 6.5

Great! looking forward to 6.5