May 22, 2006

Moo2v140b23 patch released

I have released the Moo2v140b23 patch today. I made a number of changes in order to improve the stability of the game. Hopefully these changes with help reduce the number of crashes during gameplay.

The fixes are as follows:

  • Corrected a problem with the /nohousing switch which could cause it to only apply to players that had the switch on their command line. All players should now receive the settings from the host.
  • Corrected another problem where the /nohousing switch could override the settings stored in a saved game when loaded. This included the stored settings for some other switches. Now the settings should be loaded from the save game file and command line switches should not have and effect on a loaded game.
  • Fixed a problem with black hole generators that caused them not to destroy ships when ship initiative was enabled.
  • Fixed a problem in a display redraw routing that sometimes resulted in memory outside the VESA display memory window to be overwritten. This bug could cause random crashes and lockups.
  • Fixed another problem with a display redraw routing that sometimes resulted in memory outside of the video frame buffers to be overwritten. This could cause parts of the save game to become corrupted, random crashes, and other strange behavior.
  • Fixed a problem that could cause the game to crash when a player was using tractor beams.

4 comments:

siron said...

"This could cause parts of the save game to become corrupted, random crashes, and other strange behavior."

Can you give an example of this "strange behavior"? What parts of the save were corrupted by this bug?

Lord Brazen said...

Any byte in memory could be corrupted by bugs like this. The entire save game is stored in memory while you are playing the game. The possibilities are unlimited.

My point here is that, if your game becomes corrupted by this bug then reloading orion2 and the corrupted autosave will result in a crash again.

For example, if you go to move a ship and it crashes the game so you reload the game and it crashes when you try the same move, it is because the save game is corrupted. Its not a bug in ship movement code. Its a crash as a result of an invalid value in a variable associated with the ship. The value is outside of the normal range so the game crashes.

BloodMalice said...

Fantastic! It's great to see progress being done on this classic game!

Now if only I could find more people to play with... =(

Hit me up at BloodMaliceSmoky@Hotmail.com if you or anyone is ever interested.

siron said...

You will surely find enough opponents at kali:

Kali-Guide

Copyright 2005-2015 Shawn Meunier