Really Stupid Range Check Error

[PsychoTechFreak]

I have seen range check errors before patch 4 (ver 1.30) but have never seen it with this Version. I set Maximum Number Of Systems to 255 always ,likely this could raise the possibility of such errors. I received range check errors oftentimes with ver 1.19. With ver 1.27 I have seen the Last one, it was during the "Player placement in progress..." with a Maximum Number Of Systems=255.

I observed the patch history again, and it looks like a problem with numbers with exceed or almost reach the 8bit (256) barrier:

Version 1.21:
1. Fixed - Range check error when you have 255 systems and you give
a ship orders to move to another system.

Version 1.20:
34. Fixed - Range Check Error with a large number of units in a group during combat.
35. Fixed - Range Check Error with huge numbers of shields being generated during combat.
36. Fixed - Range Check Error with a fleet of more than 256 ships during combat.

and so on... the patch history has really a lot of range check error entries

[PsychoTechFreak]

P.S.:
I can feel your pain, Lord Felix. It's no fun to encounter a game crashing error, especially in the later stages of a game..., but take a deep breath, calm down and then send your savegame to MM, if this error is repeatable with the latest patch. I'm absolutely confident that Aaron would be glad to fix it, and you will be addicted to SEIV again.

A game forum is the mirror of a game and its potentiality... if you compare this SEIV forum with forums of other games, like Xtension (oh boy, bloody buggy game, and most of the community is in heavy struggle with the developers, who don't seem to care about the pain in the ... , because they received their money already).

SEIV is more than just a game for me, it is kinda challenge. I will do my best to help improving the game, at some time maybe I mod a race which will be on your PC for years...

[Crazy_Dog]

I have get a RCE in 1.30 with TDM 1.61 after about 30 turns......

[PsychoTechFreak]

I'm afraid the RCE's could be hardly repeatable, otherwise we should flood MM's mailbox with the respective saves and discribtions of the action which caused the error.

May the force be with you...