FAZ Beta Issues Here

Masauu · Post by **Masauu** » Thu Sep 28, 2006 2:51 pm

Was the periodic 3-5second "pauses" in gameplay an issue of lag spikes, or something else? Everyone seemed to have the issue. I was about to kill a miner and lagged into the rock it was mining =(

Post by **BlackViper** » Thu Sep 28, 2006 3:03 pm

Previously it was lag issues. I did not get to play last night, but most of us who have experienced, it is due to being on the Beta server.

Dogbones · Post by **Dogbones** » Thu Sep 28, 2006 3:15 pm

Freeza wrote:QUOTE (Freeza @ Sep 28 2006, 08:53 AM) It'll be too easy to abuse the auto-balance/clear teams features...on a team...off a team...on a team... /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />

Um we noticed. This is NOT a code issue it is a PEBCAK issue /glare.gif" style="vertical-align:middle" emoid=":glare:" border="0" alt="glare.gif" />

Just like the 'original' randomize, if the game controller 'mashes' it, it will cause problems, just like anything else you can mash, like VCs, although in this case as game controller you can be that much more annoying.

Post by **Tigereye** » Thu Sep 28, 2006 6:06 pm

I refer you all to RoC SR #11.

That is all.

--TE

Post by **pkk** » Fri Sep 29, 2006 2:21 pm

I did download the latest client:

Code: Select all

Initializing
• Reading Settings
• Logging Option: DEBUG
• Loading MRU Callsigns
• Loading Form Position
• Checking Installation
• Ready
• Beta Mode On.
• Checking for system updates
• Checking for existing processes
• Saving Settings
• Saving MRU Callsigns
• Checking connectivity
• Using Port: DirectPlay
• Checking ASGS Client Version
• Client Version: 136
• Server Version: 136
• Securing Installation
• Validating Installation
• Unable to validate Allegiance installation.
• File Allegiance.exe has an invalid signature.

Dogbones · Post by **Dogbones** » Fri Sep 29, 2006 2:43 pm

Launch Alleg directly, without ASGS.
Double click the BETA executable.

Other than Wed nights, or planned larger tests, we fequently update the client, sometime a few times a day, so it doesn't make sense to add all of those signatures to ASGS. During these times we just turn off ASGS.

-Try ASGS first
-If you get an invalid signature make sure you have the latest client
-If you still get the invalid signature try it without ASGS
-If you get a message saying you need to use ASGS check the sticky for updates.

Dog

OniKage · Post by **OniKage** » Tue Oct 03, 2006 8:46 pm

Possibly in the wrong thread but in game my autopilot keeps turning its self off and rips seem to randomly abort for no reason when I'm playing on the beta servers.

Dogbones · Post by **Dogbones** » Tue Oct 03, 2006 9:36 pm

OniKage wrote:QUOTE (OniKage @ Oct 3 2006, 04:46 PM) Possibly in the wrong thread but in game my autopilot keeps turning its self off and rips seem to randomly abort for no reason when I'm playing on the beta servers.

An overly sensitive mouse/joystick would explain both of those behaviors. I am 100% sure about AP, you move the joystick and it turns off auto-pilot. I think it also aborts rip cord, but I would have to double check that. I take it you are not trying to interact with the mini-map correct? Changing your waypoint will abort a teleport.

Also 'normal dead zone' and 'quadratic control response' (<esc> game options) are both saved in the registry keys and the beta and regular allegiance USE DIFFERENT keys. So if you you have changed them from the default for regular alleg you will need to make the same change for the beta. This is also true for the sound hardware accel setting.

Dog

OniKage · Post by **OniKage** » Tue Oct 03, 2006 10:49 pm

Ahh yeah seems in beta for some reason I have to move my throtle control to 0% before I rip or engage AP, normally it doesnt matter what it's set too aslong as I don't move it when I AP/Rip.

guitarism · Post by **guitarism** » Wed Oct 04, 2006 12:04 am

Time to recalibrate that thing.