R4
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?
Where can the timout delay thing be modified?
Edit: Oh wait, that's server side, right?
Last edited by Norgonq1 on Thu Nov 01, 2007 4:43 pm, edited 1 time in total.


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
For those getting the
Code: Select all
Launching Allegiance
• Unable to launch Allegiance.
• Allegiance did not launch in the time allotted.
Tiger is working on why the server is crashing


DOG PROPERTY LAWS:
2. If it's in my mouth, it's mine.
[unless it tastes bad, then it is yours.]
-
- Posts: 3170
- Joined: Sun Jul 16, 2006 12:51 am
-
- Posts: 1248
- Joined: Sun Jun 19, 2005 7:00 am
-
- Posts: 1248
- Joined: Sun Jun 19, 2005 7:00 am
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
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

Last edited by SP4WN on Thu Nov 01, 2007 6:10 pm, edited 1 time in total.
It worked fine for me in beta, but now it just closes right after asgs launches alleg. Annoyed.
Code: Select all
• Initializing
• Reading Settings
• Logging Option: SIMPLE
• Loading MRU Callsigns
• Loading Form Position
• Checking Installation
• Checking OOBE
• Ready
• 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
• Preparing Key
• Key Generated
• Connecting to ASGS Server
• Authenticating
• Ticket Received
• Return Value: 0
• Callsign: ^Shizoku@Xt(24)
• Authenticated successfully
• Checking messages
• Return Value: 0
• No messages
• Checking polls
• Return Value: 0
• No polls
• Logged In
• Launching Allegiance
• Active
• Allegiance exited with code: EXCEPTION_ACCESS_VIOLATION
• Creating Crashfile
• Beginning Logout
• Closing processes
• Sending Logout Request
• Logged Out

-
- Posts: 1248
- Joined: Sun Jun 19, 2005 7:00 am
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
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
Last edited by One-Man-Bucket on Thu Nov 01, 2007 6:10 pm, edited 1 time in total.