Matrix Games Forums

Hi there,

Under the 906.15 build I sometimes get this on thread exception error in the EMCON window in the Doctrine settings.
Thought it was the same error as the on thread exception error in de the DB viewer so I did not report it, but it is still present under the 906.15 build. So here is the report with all the sequential error popups that I get before the game gets stuck in a pop up loop and has to be closed down via the task manager...

W.

Hi,

Is there a sequence of steps that consistently generates this error ?

Thanks!

Assuming the simulation was running, if you are very quick you can stop the simulation after you close the last pop-up and the first one reopens. That way you can exit the sim normally, saving the game just in case.

Sunburn, I'm getting this periodically also. I can't put my finger on the steps to reproduce, but I believe it happens when trying to set/change EMCON status for groups or units, usually on larger scenarios.

I'll try to pay closer attention as to what actually causes it, but changing EMCON is what I was doing the last 2 times it happened.

I have to agree with Kitchen Sink that this issue is related to changing the EMCON off grouped units.
With the help of KS's input I have been able to reproduce this problem reliably:

1) Open the provided save of the beginning of the Black Tiger V scenario
2) Select the Surface Group 2150 (the CV group).
3) Go to the AC op. screen and select the 10 available F14E AC.
4) While having all 10 selected go to the doctrine tab and and uncheck the "inherit from parent" box in the EMCON settings tab.
5) Game goes into a popup loop.

This should be able to let you fix this issue.

Good luck.

W.

Bump.

Still an issue under 906.18

Can be reproduced, see post above.

W.

Thanks for the save and steps! Seeing it clearly.

This requires some heavy restructuring of the doctrine code and is dangerous to do just now. Logged, and we will definitely work into this after v1.11 SR7 goes gold.

Thanks.

Just saw this thread mentioned in another one and thought to tell you that these error popups are the same as reported here:

tm.asp?m=4233526

Since I'm not an expert I'm not sure whether these issues could be related just by having same error popups.

Fixed in Build 919.

Thanks for the excellent support.

W.