Build Testing

SixthtySixthSix · Post by **SixthtySixthSix** » Thu May 01, 2008 4:27 am

Worked my way all the way through the R3 build without having to ask a question on the forum! Got Allegiance.exe built with one warning in the Virtual Key Mapping routine... shifting by 32 bits? Well, nvm that...

When I copy Allegiance.EXE into my game folder and try to start ASGS up, ASGS does exactly what I expected it to do- the validator returns an Invalid Signature error and refuses to start. /mad.gif" style="vertical-align:middle" emoid=":mad:" border="0" alt="mad.gif" />

How then, can I test my builds? Do I need to be building R4/R5? With the regular updates, will I have to constantly update my current build files? What if your updates write over a file I am developing?... but particularly, how can I test my builds?

Too, are the servers compatible with R3 or R3 mods (or any mods for that matter)?

/mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />

ShadowMoses · Post by **ShadowMoses** » Thu May 01, 2008 5:07 am

Does your modifications include "infinite ammo" and "godlike"? =]

Your_Persona · Post by **Your_Persona** » Thu May 01, 2008 7:20 am

SixthtySixth wrote:QUOTE (SixthtySixth @ Apr 30 2008, 10:27 PM) How then, can I test my builds?

/mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />

If your build is compatible with the current beta servers and the servers are not running in protected mode, then you can point your lobby to the beta lobby and connect to that and test.

A more likely situation would be that you need so start up a beta lobby server and game server that you can run against. I'm assuming you read all the dev info in the wiki? freeallegiance.org/FAW ?

Sorry I don't have the desire to look up the specifics, but check our your allegiance.cfg file and also your registry keys.

madpeople · Post by **madpeople** » Thu May 01, 2008 10:37 am

you can start your own lan game, you will need the appropriate R# server for your build.

you can also play the training missions.

SixthtySixthSix · Post by **SixthtySixthSix** » Thu May 01, 2008 1:21 pm

ShadowMoses wrote:QUOTE (ShadowMoses @ May 1 2008, 12:07 AM) Does your modifications include "infinite ammo" and "godlike"? =]

My fellow players hate me when i suggest to the DM that 3d6 is what you are supposed to role for attributes...
...no. Really wanted to go bug hunting...

SixthtySixthSix · Post by **SixthtySixthSix** » Thu May 01, 2008 1:55 pm

Your_Persona wrote:QUOTE (Your_Persona @ May 1 2008, 02:20 AM) If your build is compatible with the current beta servers and the servers are not running in protected mode, then you can point your lobby to the beta lobby and connect to that and test.

A more likely situation would be that you need so start up a beta lobby server and game server that you can run against. I'm assuming you read all the dev info in the wiki? freeallegiance.org/FAW ?

Sorry I don't have the desire to look up the specifics, but check our your allegiance.cfg file and also your registry keys.

Attempting to start my built Allegiance.EXE file in the game directory results in the built-in 'Allegiance Crash Guard' monitor activating and program exit, so no training tests. Haven't checked yet; are the servers in the Rx builds? Are they compiling without needed modifications? Is there a wiki for building the servers if they need mods? Could it just be the R3 version that I'm trying to use? /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />

ASGS:
• Securing Installation
• Unable to secure Allegiance installation.
• EXE Path Information not found in the registry.
...and from this i assume that the Beta is an install? btw, when 'beta' is used, is it referring to the R5 beta? I need to go to R5 anyway...

There has to be some convenient way to test builds other than to generate the entire game directory at build time (read- drop Allegiance.EXE into the game directory to test IT). And being limited to testing the build in a training mission may not allow for full testing... but I wouldn't complain at this point about seeing a version of my build actually run.

Do the (does the) Beta server(s) not check the signature on Allegiance.exe? I was thinking that ASGS and that validation system (that Microsoft dropped) was the problem. I mean, the Allegiance.EXE built from R3 isn't starting when it is moved to the game directory; ASGS doesn't even attempt to execute the file. Or maybe it does and the server is puking out the Invalid Signature error?

ASGS reports:
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 165
• Server Version: 165
• Securing Installation
• Validating Installation
• Unable to validate Allegiance installation.
...a pop-up request to Repair Allegiance... ...and, LOL, ASGS erases my build copy and downloads the current build! /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />
• File Allegiance.exe has an invalid signature.

What is the purpose of the validation tool? Prolly to keep people from writing cheats into their local client? /ninja.gif" style="vertical-align:middle" emoid=":ninja:" border="0" alt="ninja.gif" /> Grrr... I hate cheaters. Mebbe it is just to detect corruption of the executable (innocently prays- little halo, angel wings)? /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" /> So, how can I test my build?

SixthtySixthSix · Post by **SixthtySixthSix** » Thu May 01, 2008 2:04 pm

madpeople wrote:QUOTE (madpeople @ May 1 2008, 05:37 AM) you can start your own lan game, you will need the appropriate R# server for your build.

you can also play the training missions.

Are the servers in the Rx distribution? Are they snuck off in a corner? Is this going to involve the UIsvr that doesn't want to build? /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />

Nope, training missions are out- Allegiance.EXE starts, then Crash Guard pops up, so no training missions. I'm thinking that this is because I have built from R3 and tried to run the R3 build in the current R4/5 game directory. The Lobby reports R4. Should I build R4 for compatibility or R5, or the R5 beta?

Yah, training missions would be just fine for testing and getting a feel of the engine... /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />

the_dare · Post by **the_dare** » Thu May 01, 2008 2:24 pm

try launching allegiance with out asgs! i dont think you can play a moded old version of alleg on the live servers!

SixthtySixthSix · Post by **SixthtySixthSix** » Thu May 01, 2008 10:31 pm

the_dare wrote:QUOTE (the_dare @ May 1 2008, 09:24 AM) try launching allegiance with out asgs! i dont think you can play a moded old version of alleg on the live servers!

...yah, did. Even the current game distribution's Allegiance.exe doesn't log on to the servers- you have to use ASGS. But the R3 build isn't working even Without ASGS... not even the training missions. I think it is because I built R3 and dropped it in the R4 game build. I hope that's it. If that isn't it I dunno what it could be... R3 wouldn't have been distributed if it wasn't at least somewhat stable.

Have you built Rx? How do you test your builds? /blink.gif" style="vertical-align:middle" emoid=":o" border="0" alt="blink.gif" />

apochboi · Post by **apochboi** » Thu May 01, 2008 11:32 pm

I really didnt read all of this thread, but i've no idea why you are using r3 for anything. R3 is old, we now use R4 and currently the dev team are making R5. Both servers and lobbys will reject that build. Perhaps get yourself the R4 server if you need that instead and do your testing with that.