Error message with 1.03

[cbelva]

I have installed version 1.03 and started the British scenario "Thin Blue Line". After several turn I get an error message that reads "Bad Quadrant in QuadrantToCorner():0". The error message appears at the end of the combat resolution phase and after clicking on the Proceed message. I can click it off with the "OK" button and continue, but I find that I can no longer right click and issue orders. I played the US scenario, "Meeting of Titans" and did not have this problem. I played this scenario 3 times now and received this error each time.

[CapnDarwin]

cbelva,

Dang! We thought we killed that glitch. It showed up in the last build and even delayed the 103 release to fix it and it looked that way too. I'll get with Rob and see if we can track down why it is scenario dependant.

Thanks for the info!

[cbelva]

Glad to be of service. I did notice one more glitch. If you exit out of a scenario by selecting "Start a New Game" the pull down menu, after opening the new new scenario when you select a unit on the map, the appropiate unit is not highlighted on the force tree. Also, if you select a unit on the force tree, the corresponding unit is not selected on the map. I have to exit out of the program, restart the program in order for it to work.

[cbelva]

Cap'n D,

Want to pass on that I got that error again playing as the Soviet in the US scenario "Meeting of Titans".

[CapnDarwin]

I talked with Rob this evening and he is looking into the bug. Hopefully he'll be able to knock it down over the weekend.

Sorry for the trouble.

[IronManBeta]

ORIGINAL: Capn Darwin

I talked with Rob this evening and he is looking into the bug. Hopefully he'll be able to knock it down over the weekend.

Sorry for the trouble.

It is said that all people are but six connections removed from knowing every other person alive, and something similar might be said for game code. A change in one place can surface a problem in a seemingly utterly unrelated spot via a series of connections generated by the player. I have tracked this one down and have fixed the immediate problem. We just need to test it a little to make sure that the fix did not cause something else via these 'connections'. Look for a version 1.03a soon.

Thanks also, Chelva, for the other issues. That ought to be an easy fix and that will be covered too.

Thanks for your patience.

Cheers, Rob.

[Rainbow7]

Just to add that I've seen this error in scenario 4 after installing 1.03.