State of Allegiance in Linux

Goltred · Post by **Goltred** » Thu Sep 18, 2008 2:59 pm

Uhhhh... Greetings!

I want to join this "crusade" to make Allegiance work under LInux and here is what i've tested so far...

I'm using SUSE 11.0 and my computer has the following specs (or something similar):
AMD64 Dual Core 3800+
1Ghz Ram DDR2 (i think)
nVidia nForce 405 (Integrated Video Card)
Wine 1.1.4

1.- I managed to make Allegiance work (and login to ASGS, etc) in a Virtual Machine (Using Virtualbox)... Of course, not aware of the linking accounts that it may have with other VBox(or VM?) users out there.... My main problem of this is that the complete platform (Linux+VM) consumes too much memory (despite i configured the VM to 256MB ram i think), and thus the game worked quite slow (but still "flyable")... the other problem i had is that when executing Allegiance in full window caused the mouse to work erraticaly (just on the edges of the screen), but while on Windowed mode worked fine...

2.- Until today, i didn't manage to install .Net in Wine, but i was trying version 2.0. After reading the first posts of this Topic i tried with 1.1 and it passed ok (so did the allegiance installation).

After testing ASGS.exe wine just did nothing, so i tried Allegiance and got my monitor to got "Out of Range" (happened before with War3, since the game tries to execute at a specific resolution it causes that problem on the monitor, despite of having Xorg.conf configured to.. what seems... properly). The solution for this is to execute Wine in windowed mode /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />

Having to restart my computer, i changed the settings of Wine and managed to play the Practice Arena mission of Allegiance (texts and images of the screens didn't show), it executed quite slow... but at least i was able to manouver the ship.
Oh, the other thing that didn't display while on game was the indicators of the HUD (speed, armor, reticle, etc...) but it showed characters...
Sound seemed to work fine...

I'm going to run a few more tests trying to install DX9 and also in a software called Play on Linux, which helped me play Warcraft 3 in full window without giving me the "Out of Range" error, that happened when trying to execute it only through Wine

privateerm · Post by **privateerm** » Thu Sep 18, 2008 3:04 pm

Goltred wrote:QUOTE (Goltred @ Sep 18 2008, 11:59 AM) Uhhhh... Greetings!

I want to join this "crusade" to make Allegiance work under LInux and here is what i've tested so far...

I'm using SUSE 11.0 and my computer has the following specs (or something similar):
AMD64 Dual Core 3800+
1Ghz Ram DDR2 (i think)
nVidia nForce 405 (Integrated Video Card)
Wine 1.1.4

1.- I managed to make Allegiance work (and login to ASGS, etc) in a Virtual Machine (Using Virtualbox)... Of course, not aware of the linking accounts that it may have with other VBox(or VM?) users out there.... My main problem of this is that the complete platform (Linux+VM) consumes too much memory (despite i configured the VM to 256MB ram i think), and thus the game worked quite slow (but still "flyable")... the other problem i had is that when executing Allegiance in full window caused the mouse to work erraticaly (just on the edges of the screen), but while on Windowed mode worked fine...

2.- Until today, i didn't manage to install .Net in Wine, but i was trying version 2.0. After reading the first posts of this Topic i tried with 1.1 and it passed ok (so did the allegiance installation).

After testing ASGS.exe wine just did nothing, so i tried Allegiance and got my monitor to got "Out of Range" (happened before with War3, since the game tries to execute at a specific resolution it causes that problem on the monitor, despite of having Xorg.conf configured to.. what seems... properly). The solution for this is to execute Wine in windowed mode /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />

Having to restart my computer, i changed the settings of Wine and managed to play the Practice Arena mission of Allegiance (texts and images of the screens didn't show), it executed quite slow... but at least i was able to manouver the ship.
Oh, the other thing that didn't display while on game was the indicators of the HUD (speed, armor, reticle, etc...) but it showed characters...
Sound seemed to work fine...

I'm going to run a few more tests trying to install DX9 and also in a software called Play on Linux, which helped me play Warcraft 3 in full window without giving me the "Out of Range" error, that happened when trying to execute it only through Wine

Good work!!! I couldn't actully get into the training mission cocpit at all!!! Nice

Goltred · Post by **Goltred** » Thu Sep 18, 2008 8:37 pm

Well.. i've got good and bad news...

First... Play on Linux did no good, the same error (Out of Range) is displayed when i try to run full screen.

I reinstalled everything again, to try and see a specific error i noticed when installing .NET Framework (unfortunately, i didn't manage to take a screenshot of it

). During the install, there's one instance when Registering Modules that it says 'Failed'... to then finish as an installation successful.
Now, when that happens a huge amount of errors are displayed on the terminar when i executed the wine command... The thing about this is that one of the lines also appears when i execute the ASGSClient.exe

Perhaps if we find how to fix the Framework install (perhaps is just a matter of registering a specific dll??) we'll be able to make ASGSClient to work properly (but maybe not...).

Framework Line: fixme

URL_ParseUrl failed to parse L"mscorlib" (Installation Text File: >>>>>>>.Net Framework Install Errors<<<<<<<<)
ASGS Line: fixme

URL_ParseUrl failed to parse L"mscorlib" (ASGSClient.exe Text File: >>>>>>>ASGSClient.exe Errors<<<<<<<)

During the framework installation, there are a lot of lines addressing that 'mscorlib' something....

After this, i did another test against Allegiance.exe with the same results: No Hud indicators, no reticle and crappy FPS... but i noticed a sudden change when i docked into the station and then the ship inmediatly exited (it moved at a normal speed for a couple of seconds!!). I began playing with the views and display and guess what... I managed to play the game perfectly once i press the F12 key!...
The only problem is that to do that you have to play without any HUD or indicator at all

(Apparently, the icons, words and other images of the HUD are dropping the FPS...)

On the other hand, i've saved the DXDiag file of my computer since i've got a question... ASGS is supposed to link accounts according to computer specs (dunno if that's right... i never understood how that worked /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />). Well, according to this file >>>>>>>(DxDiag.txt)<<<<<<< there are a few devices that seems to be equal independent to the computers (Like Display device)... wouldn't that be a problem when it comes to linking accounts?

That's it... now to sleep /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />

finnbryant · Post by **finnbryant** » Mon Sep 22, 2008 9:21 pm

thats awesome, ill be having a go later.
its probably best to give up on ASGS completely for now, if we get alleg going, ASGS may follow, but for now any success will be blocked by updates in ASGS most likely.

One of the main changes in the dx9 alpha in alleg is that the 2D hud stuff was revamped iirc, that means theres a good chance using the alpha would give you full fps while using the hud, i suggest you give it a go.

EdDaalleg · Post by **EdDaalleg** » Fri Oct 03, 2008 6:14 pm

I have only read part of this thread and don't know much about this crap anyway so give me some leeway if I'm repeating stuff.

My brother seems to have Allegiance running moderately well on WINE and with some tweaking it was pretty playable. He was able to play a training mission at a normal framerate in full screen without any graphic errors (it actually looks better than it does on my PC

) but did not try to play online since he had to open the alleg .exe directly. What further stability testing are you looking for? I don't think it will run stably in a variety of modes with different options, but mid-low settings in full screen seemed to work fine.

Also, he is not using the alpha version, should he be?

badpazzword · Post by **badpazzword** » Fri Oct 03, 2008 6:19 pm

I will try and see the situation in Intrepid Beta tomorrow.

[ALSA is currently borked (at least, it was up to today morning) so I'll get no sound.]

Dogbones · Post by **Dogbones** » Fri Oct 03, 2008 9:54 pm

If you are going to try and connect to the beta server make sure you are running the latest beta client as the old client will not connect to the new server.

ASGS is not running (at the moment) on the beta server (fazdev.alleg.net) so you should be able to connect.

Here is the latest client http://betaupdate.alleg.net/Allegiance.exe

You will also need these files which go in the artwork/dev folder. http://fazdev.alleg.net/FAZ/R5beta_artworkdevfolder.zip

The beta client looks for 1.1 registry keys. If you setup 1.0 registry keys you need to replicate them as 1.1 keys and point it at fazdev.alleg.net
Make sure the cfgfile points to http://fazdev.alleg.net/FAZ/FAZ.cfg

finnbryant · Post by **finnbryant** » Mon Nov 10, 2008 1:32 pm

thought I'd update this,

since i can't get in-game at the moment and have finally got something other than integrated graphics I thought I'd give this another whirl.

Using the alpha I successfully got in game, but the settings required were a bit odd (texture packing was required!?!)

The following instructions are in the hope of getting more interested/ensuring that everyone can get to where I am so they may be more basic than necessary.

note: wont work if you have intel integrated graphics, sorry.
get the latest wine.use this guide to install dotnet11 and directx9install alleg (default install settings recommended)test Allegiance.exe don't use the shortcuts, they go to ASGS, which wont work, alleg will be in the "home/.wine/drive_c/wherever_you_installed_it" directory (.wine is hidden). Click free games to download updatesreplace Allegiance.exe with the beta and add the artwork (see dogbones post above) you may want to back up the originalrun "wine regedit" in the terminalgo to "HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Allegiance\1.0" and select Registory>Exportedit the file so that [HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Allegiance\1.0] is replaced by [HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Allegiance\1.1] and "CfgFile"="http://autoupdate.alleg.net/allegiance.cfg" is replaced by "CfgFile"="http://fazdev.alleg.net/FAZ/FAZ.cfg"import back into regeditrun Allegiance.exe againset resolution to your normal display resolution (feel free to change this one, but I didn't test other modes), windowed mode ON, mipmaps OFF, texture pack ON. If you want full screen, set it in game later.sound seems to be an issue, try setting sound quality to low and sound card acceleration on, this seems to work, but if sounds seem to get really quiet, jiggle the quality back and forth.don't minimise, restore or close, when your done, alt-tab out and kill it (i run it from the terminal and keep the terminal in a different workspace, then ctrl-c to kill it.
there are a number of bugs, but it seems stable enough as long as you don't try anything funny.

EDIT: whats really interesting is that I can create and play in a game on the beta sever, which is more than I can do in windows. i thought it was my uni firewall being difficult but i guess not.
so its official, for me, linux is running alleg better than vista!

EDIT 2: missed a step (sorry)

parcival · Post by **parcival** » Mon Nov 10, 2008 1:44 pm

GJ Finn!
How many frames per second do you get?

finnbryant · Post by **finnbryant** » Mon Nov 10, 2008 3:56 pm

around 180 fps @ 1280x1024 on my 8600gt in the protect the minors training mission

lower than windows but not low enough to matter.

btw, don't try to have any sound other than alleg going, it seems to upset it.

just tried with 4x billinear anti-aliasing and 2x anisotropic (set from the nvidia control panel, there are no options in allegs anti-aliasing listbox)
for some reason this made the vsync start working, i got 60 fps with no drops.

EDIT: lol, with x16Q anti-aliasing and x8 anisotropic i got <1 fps

(it actually seemed more like 15 fps until I pressed alt-f so that may be an unfair measurment, i was just impressed at how slow it could go without giving up)
with 16Q on its own I got 20 fps with random drops to 2-3 and freezes, but considering that windows crashes it at 8x that ain't so bad...