Free Allegiance Forums

Tested on wine 1.1.8, opensuse 11.0, 7600GT, confirmed Allegiance runs. ASGS not tested.

Wine on default settings except for running in a virtual (windowed) desktop mode. Too many bad experiences with games grabbing full screen and not letting go.

I had to use a fresh .wine otherwise I got a C ...

We really shouldn't use that unsupported red-text 'fix' that I wrote anymore. Upon further investigation, it appears to be a thread safety issue dealing with multicore machines. That 'fix' will effectively shut off all but one of your cores. Not good.

It is possible to just tell Windows to only run ...

QUOTE (Your_Persona @ May 13 2008, 10:43 PM) Can you guys get it to compile on linux?

I've toyed with it with winelib, except the converter isn't smart enough to figure out which source files/folders are being used, so it tries to compile everything. All the extra junk in the code throws it off ...

QUOTE (Badp @ Apr 20 2008, 03:04 PM) badp@bPortatile:~/.wine/drive_c/Program Files/Microsoft Games/Allegiance$ wine ASGClient.exe
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range ...

And I dual-boot XP and Ubuntu and everything worked out of the box in Linux for me. That, I think, is Linux's biggest obstacle right now. There's no guarantee that everything will work right away like in Windows. That's the hardware manufacturers' fault. The Linux geeks have to use experimentation ...

The hackboot should show in the server logs in what file and line (in the source) that it happened. I'll have to look into it to see what it sends to the event viewer.

Whenever the server gets a message from a player, it runs it past some checks to make sure that it's a valid action. For example, if a scout tells the server that it just loaded an aleph res into the missile slot, the HackBoot goes off. Or firing a gun your ship can't load. Stuff like that. It's to ...

The "hard limit" is one value in the server code that sets the size of the memory allocated. Just up it to 500, or even make it dynamically allocated.

Quick question about it:

When this happens, does the ship get the little icon next to it? Or does it make that sound that plays when an enemy ship enters the sector?

Iirc, all the interface pictures have a setting in the plaintext mdl that tells the engine whether the black is transparent or not. With some exceptions (e.g., the HUD), transparency is all or nothing. I suspect that the HUD's semi-transparent parts are hard-coded in.