Posted: Fri Jun 08, 2007 4:07 am
This is a listing of known problems with the R4 beta client and/or server. If you've ran into one not on this list post in this thread. This is not the place to make comments about gameplay or feature changes. If you don't like cons building fast for example, don't post that in this thread. If you see an obvious bug with cons building this would be the place though.
White: Issues that have not been resolved.
Green: A solution has been coded and the issue should be resolved in the next build
Red: Newly added to the list (may or may not be a result of a new build)
Striketrough: Should be resolved in the most recent build, post if you are still having problems.
Known Issues
The new Voice Chat packs going around are NOT compatible with the newest R4 build. To play R4 for now you will need to use a compatible Quick Chat list. You may download the default list that comes with Allegiance from http://www.AllegTraining.com/quickchat.zip. Extract it and put QuickChat.mdl in the dev folder that the beta uses (Program Files/Allegiance/artwork/dev/).
UPDATE: The installer will now do this for you if you say yes when asked about having any of the new voice chat packs.
GraphicsGarbled text in the chat pane for many people when in 32bpp mode using certain ATI cardsSome parts of the inventory pane (F4) become completely transparent.Small lines or shapes that aren't supposed to be there.Missing pixels.Screen flickering occasionally, like a model is in the background (post if you see this because it seems very rare)Idle cons/drones "dancing" or "jittery" May only occur when you have a ship in the sector and are moving. (haven't tested this with other players in the sector yet, post if you have more details)F3 View Grid cutTurning off teams:Can't start the game when yellow is turned off.Balance button assigns players to teams which are turned off.Joining a team that has been turned off in a method such as the following (correction, bug exists but I was incorrect in the way it occurs): This can happen when you are on a team and the game hasn't started, but you leave, the team you were on is closed, and you rejoin to find yourself on the closed team.OtherDonations not set correctly following mutiny, as shown by the following example with Team 2 turned off.The mission briefing is covered up by the map previewWhen the number of drones allowed is turned up some tend to go missing from the server. Their location is listed as "unknown" in F6 (team pane) and trying to go to them crashes the server.Ranks currently get cut off for players with long namesSuccessful mutiny does not give new commander the moneyF6 crashingIf you think you have experienced any of the following issues, in particular, please double check you have the latest client and test it again to confirm and post here:ANY problems with graphics in 16bpp modeANY crashes or problems you think are related to F6.Draw or resign votes where the commander on the other team automatically votes no without being askedMiners reluctant to mine, having to order them around when you shouldn't (or other miner/con problems)Any information related to cons going out of the sector and killing themselvesThis happening:
White: Issues that have not been resolved.
Green: A solution has been coded and the issue should be resolved in the next build
Red: Newly added to the list (may or may not be a result of a new build)
Striketrough: Should be resolved in the most recent build, post if you are still having problems.
Known Issues
The new Voice Chat packs going around are NOT compatible with the newest R4 build. To play R4 for now you will need to use a compatible Quick Chat list. You may download the default list that comes with Allegiance from http://www.AllegTraining.com/quickchat.zip. Extract it and put QuickChat.mdl in the dev folder that the beta uses (Program Files/Allegiance/artwork/dev/).
UPDATE: The installer will now do this for you if you say yes when asked about having any of the new voice chat packs.
GraphicsGarbled text in the chat pane for many people when in 32bpp mode using certain ATI cardsSome parts of the inventory pane (F4) become completely transparent.Small lines or shapes that aren't supposed to be there.Missing pixels.Screen flickering occasionally, like a model is in the background (post if you see this because it seems very rare)Idle cons/drones "dancing" or "jittery" May only occur when you have a ship in the sector and are moving. (haven't tested this with other players in the sector yet, post if you have more details)F3 View Grid cutTurning off teams:Can't start the game when yellow is turned off.Balance button assigns players to teams which are turned off.Joining a team that has been turned off in a method such as the following (correction, bug exists but I was incorrect in the way it occurs): This can happen when you are on a team and the game hasn't started, but you leave, the team you were on is closed, and you rejoin to find yourself on the closed team.OtherDonations not set correctly following mutiny, as shown by the following example with Team 2 turned off.
Code: Select all
Player1, Player2, and Player3 join Team 1, Player1 is commander.
Player2 mutinies and the vote is successful and he gets the money from Player1
All players are still donating to Player1.Unless it is supposed to happen?apathos wrote:QUOTE (apathos @ Jun 1 2007, 10:59 AM) Only other thing, when in a 1 team game with FF on, the game did not end when all the techbases and garrisons were destroyed. I had one outpost left, which I built a garrison const. from, held con and then blew up the outpost. That ended the game. While down to just the outpost I could not build techbases, but I could build any other constructor (caltrop, drone, op, tp, etc.), and I could still build miners. Maybe it was supposed to be this way, but if not, there it is.