v1.35 Ground Combat Bug

aroenche · #1 April 19th, 2001, 11:07 AM

v1.35

In the combat simulator, a successful planet capture causes an "Access violation at address 004D2260 in module 'SE4.EXE'. Read address of FFFFFFFF." when closing the ground combat dialog. This does not occur if the invasion fails. Reproducable using both large and small transports and troops on a 400M planet with pop only.

Anyone else seeing this?

Dragonswrd · #2 April 19th, 2001, 11:28 AM

I haven't received that error, yet.

Aussie Gamer · #3 April 19th, 2001, 11:14 PM

It looks like you gotten a corrupted file somewhere.
You might have to delete SE4 completely and reload it. Hopefully you can save the game and rerun it on the fresh SE4 files.

Dracus · #4 April 20th, 2001, 01:57 AM

I was getting this before the patch at 310 turns. I can't even finish my game. I have rebooted the pc and still get it every time. I have loaded the files onto another pc and still get it. I have already sent the files to MM.

It also was happening when I use tact battle and then pick resolve combat around 304 turns.

[This message has been edited by Dracus (edited 19 April 2001).]

Dr Strangelove · #5 April 20th, 2001, 10:16 PM

Are you playing a game stareted using a different Version and are any of your troops equipped with cluster bombs or small rockets? The patch supposedly allows only fighters to carry these componenets. I'm not sure what would happen if you installed it to a game in which you had previously designed troops using these components.

aroenche · #6 April 20th, 2001, 11:12 PM

I removed the existing install and directory, re-installed from CD, ran the 1.35 patch, created a new single player game, designed a toop carrier and troop unit, and reproduced the same error. Troop is equipped with 3 best ground cannon. Error is occurring on turn 2400.0 This error crashes the game.

I'm aware of the new unit restrictions, and that would have been my first guess as well, except that we're looking at a fresh install/no mods/newly genned uni.

It seems ironic that between this bug and the base multiplex targetting issues, everything tactical I've tried to do since buying the game has failed.

Judging from the patch history, Aaron & co. have been doing a tremendous job in addressing outstanding issues with game, and I guess I expected a fairly stable platform at this point in time.

Now I'm beginning to question the wisdom of setting up a real game, considering the seemingly obvious issues I've encountered so far just by kicking the tires a little...

Any thoughts?