Liquid War (v5.4.4) - Bugs




Report a new bug
================


  If you have troubles with Liquid War 5, if you think it is a bug, and if it
  is not described in this file, then just send me a mail at "ufoot@ufoot.org"
  with a (precise...) decription of your problem. I'll try and see what I can
  do about it.



Memory bugs
===========


  Memory allocation of Liquid War 5 can get very buggy, especially when you run
  it in a DOS box.

  The main reason is that Liquid War keeps on allocating and freeing bitmaps.
  And sometimes there is not enough DPMI memory to create bitmaps. If this
  happens, Liquid War should exit and give you a short description of the
  problem.

  But it is also possible that Liquid War exits with a page fault error without
  warning you. This is often because the GUI manager of Allegro NEEDS free
  memory to work correctly. And if this memory is not available, it crashes...
  I have tried hard to work this arround but could not make it. All you can do
  to avoid this is to give Liquid War more DPMI memory and try and reduce the
  "-mem n" command line parameter.



Network
=======


  Network support in Liquid War is far from being perfect, so there are a bunch
  of little problems which can appear. Basically, once the game is correctly
  started on a LAN, you should have no problems, but getting the game started
  might be difficult.

  Basically, network support in 5.4.0 and 5.4.1 is half-broken, and setting up
  an internet game is pretty hard.



Interference with other Windows programs
========================================


  It's been reported that Liquid War can run very slowly on Windows when some
  other programs (Mozilla for instance) are running. So if Liquid War's menus
  seem to be really really slow, then try to shut down other applications and
  run the game again.

  This problem does not seem to apply on GNU/Linux - at least if you do not run
  300 daemons together on your machine 8-)



Mouse cursor display
====================


  Most of the time, the mouse cursor will not be displayed correctly, more
  precisely, weird squares can appear now an then where the mouse cursor was. I
  acknowledge this looks ugly but at least it's not a "blocking" bug... ...it's
  ugly, that's all!



Datafile bugs
=============


  Sometimes there are some problems when compiling the datafile, this includes:

  * The liquidwarcol, liquidwarmap and liquidwartex utilities might freeze or
    segfault. Typing "make" again often solves the problem.

  * The background image sometimes ends up using the wrong palette, which has a
    very nasty consequence: it looks ugly.

  These bugs are quite hard to get rid off, since I can not reproduce them
  easily. The good solution would be to completely rewrite the liquidwarcol,
  liquidwarmap and liquidwartex utilities.

