New Allegiance installer
I noticed yesterday that I made something wrong on high res textures mdls...
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
It's now fixed... Forgot to update asteroid.7z file...pkk wrote:QUOTE (pkk @ Oct 22 2010, 06:38 AM) I noticed yesterday that I made something wrong on high res textures mdls...
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
Here's my experience and observations:
I used the installer on a new machine running Windows 7 Home Premium 64-bit. This machine is about as clean as you can get it from the store. (It didn't even have all the available updates applied yet.) It also has a trial version of Norton Security Center installed. I also wanted to run it as if a newbie was trying to install the game.
Step 1: DL'ed the installer from the link pkk supplied. DL was fine.
Step 2: Ran installer, letting it choose the default location of C:\Program FIle (x86)\Microsoft Games\Allegiance and I checked all installation options (hi-res textures, etc.)
The install seemed to go fine, no errors reported.
Observation: no game icons were placed on the Desktop. Nor was I prompted or reminded to make a game account.
Step 3: Launch Game - ASGS immediately reported: OOBE failed. (before I typed in a user name and password)
Step 4: Exit out of ASGS and Launch it agin. This time no OOBE failed message. I log-in with a nick and password (no game account created yet, remember). I got an error message "specified Account doesn't exist" message. This is as expected, since I didn't create a game account yet.
Observation: the error message is a little cryptic, but is does give an idea of what the problem is. However, there is no help as to how this is resolved. (ie go to freeallegiance.org and create a game account. A direct linky would solve this problem, I think.
Step 5: Created Game account
Step 6: Validated the game account
Step 7: Launch Allegiance, try to log in kept getting "specified account does not exist" message. I suspect that I had a typo in the password, but the error message I got tended to make me think that the account hadn't been activated yet. (ie it wasn't obvious that my error could have been an incorrect password)
Step 8: Reboot (just in case)
Step 9: Launch game, fix password typo. Allegiance client launches. Autoupdate pushes its stuff. Client and ASGS crash without displaying an error. I'm just staring at my Desktop wondering if anything is supposed to happen (and if I was suspicious, wtf did this game just write to my hard drive?)
Step X: Run Allegiance again. Log in through ASGS, client launches. More AU action. Doesn't crash this time. I get the the MotD, join lobby. See games list. Join a game and got into NOAT. I didn't try to join the game (as I don't have the time atm) to check out if the high-res stuff worked well. Will try that a bit later.
Nice job on the installer! I do note that not all of the little glitches I encountered were the fault of the installer. Some of them have to do with ASGS and our procedures. I just wanted to try to capture the "new user experience" as best as I could, and report in a single place all the little glitches that could cause a new player to just quit due to frustration or lack of appropriate feedback.
edit: While I think of it, I wasn't prompted for DirectX9. I'll have to check the machine just to make sure it's installed.
I used the installer on a new machine running Windows 7 Home Premium 64-bit. This machine is about as clean as you can get it from the store. (It didn't even have all the available updates applied yet.) It also has a trial version of Norton Security Center installed. I also wanted to run it as if a newbie was trying to install the game.
Step 1: DL'ed the installer from the link pkk supplied. DL was fine.
Step 2: Ran installer, letting it choose the default location of C:\Program FIle (x86)\Microsoft Games\Allegiance and I checked all installation options (hi-res textures, etc.)
The install seemed to go fine, no errors reported.
Observation: no game icons were placed on the Desktop. Nor was I prompted or reminded to make a game account.
Step 3: Launch Game - ASGS immediately reported: OOBE failed. (before I typed in a user name and password)
Step 4: Exit out of ASGS and Launch it agin. This time no OOBE failed message. I log-in with a nick and password (no game account created yet, remember). I got an error message "specified Account doesn't exist" message. This is as expected, since I didn't create a game account yet.
Observation: the error message is a little cryptic, but is does give an idea of what the problem is. However, there is no help as to how this is resolved. (ie go to freeallegiance.org and create a game account. A direct linky would solve this problem, I think.
Step 5: Created Game account
Step 6: Validated the game account
Step 7: Launch Allegiance, try to log in kept getting "specified account does not exist" message. I suspect that I had a typo in the password, but the error message I got tended to make me think that the account hadn't been activated yet. (ie it wasn't obvious that my error could have been an incorrect password)
Step 8: Reboot (just in case)
Step 9: Launch game, fix password typo. Allegiance client launches. Autoupdate pushes its stuff. Client and ASGS crash without displaying an error. I'm just staring at my Desktop wondering if anything is supposed to happen (and if I was suspicious, wtf did this game just write to my hard drive?)
Step X: Run Allegiance again. Log in through ASGS, client launches. More AU action. Doesn't crash this time. I get the the MotD, join lobby. See games list. Join a game and got into NOAT. I didn't try to join the game (as I don't have the time atm) to check out if the high-res stuff worked well. Will try that a bit later.
Nice job on the installer! I do note that not all of the little glitches I encountered were the fault of the installer. Some of them have to do with ASGS and our procedures. I just wanted to try to capture the "new user experience" as best as I could, and report in a single place all the little glitches that could cause a new player to just quit due to frustration or lack of appropriate feedback.
edit: While I think of it, I wasn't prompted for DirectX9. I'll have to check the machine just to make sure it's installed.
Last edited by FreeBeer on Sat Oct 23, 2010 10:41 am, edited 1 time in total.
Maybe it's a missing registry key, have to analyze that problem with processmon, so I may fix it.FreeBeer wrote:QUOTE (FreeBeer @ Oct 22 2010, 05:11 PM) Step 3: Launch Game - ASGS immediately reported: OOBE failed. (before I typed in a user name and password)
Step 4: Exit out of ASGS and Launch it agin. This time no OOBE failed message. I log-in with a nick and password (no game account created yet, remember). I got an error message "specified Account doesn't exist" message. This is as expected, since I didn't create a game account yet.
Observation: the error message is a little cryptic, but is does give an idea of what the problem is. However, there is no help as to how this is resolved. (ie go to freeallegiance.org and create a game account. A direct linky would solve this problem, I think.
ASGS crashs, while in-game autoupdate is downloading cc_10.igc. That file is protected by ASGS, that's why it crashs.FreeBeer wrote:QUOTE (FreeBeer @ Oct 22 2010, 05:11 PM) Step X: Run Allegiance again. Log in through ASGS, client launches. More AU action. Doesn't crash this time. I get the the MotD, join lobby. See games list. Join a game and got into NOAT. I didn't try to join the game (as I don't have the time atm) to check out if the high-res stuff worked well. Will try that a bit later.
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
-
Grimmwolf_GB
- Posts: 3711
- Joined: Wed Jul 02, 2003 7:00 am
- Location: Germany
- Contact:
I'm done with testing so far...
Any more suggestions?
PS:
Waiting for new updated readme of ZLs.
Any more suggestions?
PS:
Waiting for new updated readme of ZLs.
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
So far the installer has worked perfectly.
Thanks PKK (WinXP)
Thanks PKK (WinXP)
I decided to relive the days gone by in my new blog.
---
Remember, what I say is IMO always. If I say that something sucks, it actually means "I think it sucks" OK?
---
Remember, what I say is IMO always. If I say that something sucks, it actually means "I think it sucks" OK?
Cookie Monster wrote:QUOTE (Cookie Monster @ Jan 31 2012, 03:09 PM) True story.
Except the big about dorjan being jelly, that's just spidey's ego.
Just something I noticed, perhaps unrelated to the installer, but I thought I'd pass it along just in case:
Last week I used the installer to install the game on a new Win 7 64-bit machine. Install seemed to go just fine. I don't recall being prompted for DX9, but I was able to log-in, and sit in NOAT. Today I tried the Beta (selecting Beta mode in ASGS, then logging in). I got an error message stating that I need to install DX9. (ie the failed runtime DX9[whatever].dll missing error).
I'm in the process of installing that now. Will let you know how it goes.
Last week I used the installer to install the game on a new Win 7 64-bit machine. Install seemed to go just fine. I don't recall being prompted for DX9, but I was able to log-in, and sit in NOAT. Today I tried the Beta (selecting Beta mode in ASGS, then logging in). I got an error message stating that I need to install DX9. (ie the failed runtime DX9[whatever].dll missing error).
I'm in the process of installing that now. Will let you know how it goes.
Beta uses newer DirectX 9 D3D dll (Feb 2010) than R5 (Mar 2009)... That "issue" will be fixed on next build of installer.FreeBeer wrote:QUOTE (FreeBeer @ Oct 27 2010, 08:13 PM) Last week I used the installer to install the game on a new Win 7 64-bit machine. Install seemed to go just fine. I don't recall being prompted for DX9, but I was able to log-in, and sit in NOAT. Today I tried the Beta (selecting Beta mode in ASGS, then logging in). I got an error message stating that I need to install DX9. (ie the failed runtime DX9[whatever].dll missing error).
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
