I've been playing a game against the AI but when I try to remove my constructors from their current task the game gives me a stack overflow problem and crashes (or has to be closed when it does not close automatically). It seems to be connected with the number of buildings, as either of my currently done buildings have this problem, and I have expanded like a madman in the game.

I've tried to increase dosbox memory by altering the config file but it had no effect. Anyone knows a possible fix (other than not building stuff? :P)

hi

I have an original copy of MAX patched to 1.04 as the patch actually comes on the disk and at present I have a game running against 3 god mode AI’s I'm around 550 Turns in and I to get this issue I’ve even tried copying my save file into a copy of MAX that comes from GOG.com to no avail the problems persist.

To make sure that the save wasn't bad I borrowed my friends copy of MAX the (GOG.com Version) started a new game and spent several days testing it to see if it was any more stable and I've come to the conclusion that it’s just as bad for crashing as the original even with the 1.04 patch

As to hoping for a fix from GOG.com don't hold ya breath because it’s not going to happen after testing the GOG.com version of MAX I contacted them about the various issues and crashes I'd experienced while testing in the hope they might be able to fix it because if they could then I was going to buy a copy however the response I received was not encouraging. So basically MAX and indeed any other game they sell can not and will not be fixed if like MAX it has issues because they are simply a reseller and don't have access to the source code.

Personally I'm of the opinion this is very bad practise if they are going to be selling games that are known to be badly unstable then they should get the company to give them access to the source code so they can fix outstanding issues or they shouldn't be selling them

Further more GOG should be upfront about the fact they cant and wont fix games like MAX that are unstable and the fact that they are either deliberately evasive about this fact or clearly clueless doesn't help because prior to contacting them about the issues I’d experienced I emailed them to enquire if the multitude of bugs for MAX had been fixed and the response I got clearly came from some clueless customer services representative that doesn't know what there talking about In other words I don't have a clue and I'm to lazy to go and ask someone in the tech department who should know so I can actually give a proper answer to my enquiry.

I'm sorry to be slamming you guys but clearly you have some serious shortcoming that need to be addressed and you need to seriously rethink your whole approach to this and actually make sure you get access to the source code before selling a game further more you need to hire some programmers who's job it is to go over the source code of troublesome games like MAX with a fine tooth comb and correct any outstanding issues if you cant or wont do this they you shouldn't be selling games that are known to be buggy and or unstable.

as to your original question i don't think there is anything you can do about it as i understand it its a limitation of dos because each structure etc takes up a memory space and what is happening is that you are simply running out of memory spaces the only way this can be fixed is with a patch or a rewrite of the game its self neither of which will be happening so ya pretty much stuffed am afraid unless anyone knows of and an unofficial fix ? if so them please speak up because i would love to see MAX fixed and stable

Are you going to blame steam/impulse/gamersgates/whatever also for selling buggy games? Cause they sure are.

Probably known, but there is a small solution to alot of MAX common memory bugs.

[url=http://www.dosbox.com/wiki/TOOLS:DOS32A]http://www.dosbox.com/wiki/TOOLS:DOS32A[/url]

I am just trying out having a 1on1 ipx game. We had only 2 "connection lost to remote computer " issues so far, with an older other DOS Extender, but the game itself can be continued. Turn 134 and still testing. Who knows, maybe its only a connection issue, instead of bugs in the code.

To quote an old MAXR developer, mague/klei:
"The original M.A.X. is really much more stable if the original DOS Extender is removed and replaced by another one. No more memory related errors and freezes such as lost units in depots, memory assertion errors, unaccessible grids, misaligned grids. We can forget all of these issues. I've played 278 turns, and can still play."
You can check his game out here - I think it speaks for itself
http://imageshack.us/photo/my-images/5/utopiacity.jpg/

I share to help,
Sal from maxr.org

actually that's not technically true yes it helps but there are still plenty of issues

for example units becoming stuck in a loop and becoming unusable this effect can be replicated by getting a unit and having it fire on another unit or structure but the units has to not have enough fire power to finish the job on that turn so that at the start of the next turn the unit will automatically resume attacking

now at this point if you just reload the save a few time like you would if the game had crashed eventually the unit will get caught in a loop there shot will be frozen in mid are and when you tell the unit to do something all you will get is the little blue light bulb icon and the unit will become unusable

the same effect can be observed when using the auto path function to build say a road the engineer can get stuck and caught in a loop becoming unusable and this is achieved in the same way as the previous problem although sometimes this can happen even with out reloading

the crash caused by to many building/units still exists as well and changing the dos extender doesn't fix it