RANGE CHECK ERRORS

[nmoppa]

quote:

---

Originally posted by nmoppa:
SE IV is a wonderfull game, however when I battle with large fleets I too often get RANGE CHECK ERRORS. Does anybody know if this is common and/or if there is a solution to this?

---

I have the same problem. HELP!!!

[nmoppa]

I really need help on this on. I have progressed to having developed hugh fleets but when I battle other hugh fleets this error all the time occurs. HELP?!

[Lerchey]

Malfador most likley knows about it, but your best bet is to save every turn for a while, and ship MM a copy of the save game from JUST BEFORE you generate the range check error in combat. If they have the save game, and you can tell them which battle you fought that caused the problem, they may be able to figure out why it's happening and get it fixed.

John

[Dracus]

How large of a fleet? how meny ships and of what size? Have not seen this yet. I have a top of the line computer so I can test this and see if it is a game or system resource error for you.

[Atrocities]

My scripting abilities are limited so the best I can advise regarding what a Range Check error is.

When programing, some varitables, called intergraters, set the parameters of the program. When a specific set of circumstances occurs and data is generated out side of the relm of the program, a Range Check error is created.

In this case, the range check errors are more likely being generated because of the ever changing variables of the game. They have to be reported in order to be fixed. MM needs the save game files and as close of a discription as possible to what you did just prior to the RC error.

As for combat RCE's I get them all the time now. It is extremely frustrating, and a real pain in the tail. Often, I just close the game and go to bed.

A good way around the RCE's is to play Tatical. (Be sure you do not tell the game to resolve combat) or it will crash again.

RCE's are the BSOD of SEIV. I sincerely hope that they are squashed before the game developes a negative reputation for crashing.

------------------
"We've made too many compromises already, too many retreats! They invade our space and we fall back -- they assimilate entire worlds and we fall back! Not again! The line must be drawn here -- this far, no further! And I will make them pay for what they've done!" -- Patric Stewart as Captain Picard
UCP/TCO Ship Yards

[nmoppa]

Thanks for the response, guys. I'm happy at least somebody else also seems to have these problems. Mailing to MM is still impossible, so I could not yet send them my complaints and files. I use to play SE IV with the largest universe possible, 200 stars, the highest level of AI players etc. This of course means it takes a lot of time before you are able to build large fleets. Large fleets in my terms are fleets of over 30 ships with large ships of at least Dreadnought class (1000KT) or Base ships (1500 KT). I normally let the computer resolve the combats, because tactical combat (non auto)Lasts for ages with large fleets. If a fleet of 25+ ships attacks an enemy fleet of more than 10 ships (usually also large ships) it's almost shure you will encounter this problem. And that's very annoying. If you don''t want to resolve battle in tactical combat mode, this means you can only go ahead with another turn and look what the enemy will do. It's even more anoying if the AI decides to attack a system with cloaked ships in it, because the same thing happens then. Does anybody know if MM also checks these forums, which would mean they anyhow are informed about these problems?

By the way, The RANGE CHECK ERROR seems not only a problem with SE IV. I used to play the latest Reach for the Stars and with large fleets battling the same goes for this game.

Finally, I don't think these errors have something to do with my computer's capabilities. I have a Dell Pentium 3 600MGH with 512 MB memory and 30 GB Harddisk

[This message has been edited by nmoppa (edited 07 January 2001).]

[nmoppa]

Does anybody know contact info on beta testers? Just to be able to send them the problems we encounter.

------------------
MAYBE THIS IS A GOOD DAY TO DIE <Worf facing another critical fight>