Free Allegiance Forums

no serverz goin on reg should we all move to beta?

Setting the color depth to 16 didn't help, neither did using safe mode. I checked ctrl+alt+del screen while logging in and the processor usage was nowhere near maximum.

Where can the timout delay thing be modified?
Edit: Oh wait, that's server side, right?

It sounds like the timeout you are seeing is determined by ASGS and ASGS will need to be updated/changed to change that timeout. The 'other' timeout is for joining a game, and Wodk4 added a patch that increased that considerably.

For those getting the message please post in a new thread and include your system config and whether or not you tried the beta. This appears to be only effecting a sub set of you.

Tiger is working on why the server is crashing

We have a game going now.

When i try to launch Allegiance.exe without ASGS it tells me that the aplication configuration is incorrect

works now. just finished first game.

client wont start now.

I logged out and in again, when i viewed lobby it did an autoupdate of two files (mainbackground.mdl or something)

now client crashes on launch

Got the message "File allegiance.exe has an invalid signature. Would you like to repair the file"

Im sure someone somewhere told me never to click yes, clicked no, wont let me log in.


CODE• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 160
• Server Version: 160
• Securing Installation
• Validating Installation
• Unable to validate Allegiance installation.
• File Allegiance.exe has an invalid signature.
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 160
• Server Version: 160
• Securing Installation
• Validating Installation
• Unable to validate Allegiance installation.
• File Allegiance.exe has an invalid signature.
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 160
• Server Version: 160
• Securing Installation
• Validating Installation
• Unable to validate Allegiance installation.
• File Allegiance.exe has an invalid signature.


Edit: After reading through the thread i decided to tick the beta mode option, which works on getting it open rather than the previous error, when i do this i get the old Excess_Access_Violation error

It worked fine for me in beta, but now it just closes right after asgs launches alleg. Annoyed.

Ok, found the bug..

There is an error in the mainbkgndbmp.mdl file. It points to a nonexistant png (in dev/, guess devels forgot to change the path)

To fix:
* Create artowork/dev subfolder
* Put artwork/mainbkgnd2.png in that folder
* play

Edit: this would fix mine and shiz problem
Edit2: here's the png you need if it didn't get downloaded on the update: http://mysko.net/~erik/mainbkgnd2.png