Updated client available.
Known issue with LAN games only. The client will crash when you try to join unless you first select "Free Games" and then "LAN Games". We will fix this and it should NOT impact playing on the beta server.
FAZ Beta R4 Known Issues
The release needs to be updated. I cant seem to locate the 07.06.05 version that the server / client are running. (or so it says on the http://fazdev.alleg.net/FAZ/motdR4.mdl )
I guess the MOTD hasn't been updated in awhile. You'll want the current version that is pinned at the top of the forum.
EDIT: I can't seem to connect to the lobby now. I guess the lobby is having problems?
EDIT: I can't seem to connect to the lobby now. I guess the lobby is having problems?
Last edited by aem on Wed Jun 27, 2007 11:32 pm, edited 1 time in total.
Hmm, I have not been keeping this motd up to date as it is not the motd that you see when you connect to the beta lobby. At least not the one I see, but that depends on your config file. I'll try and keep them both up to date.
Latest client is 07.06.24
http://fazdev.alleg.net/FAZ/motdR4.mdl
Latest client is 07.06.24
http://fazdev.alleg.net/FAZ/motdR4.mdl

DOG PROPERTY LAWS:
2. If it's in my mouth, it's mine.
[unless it tastes bad, then it is yours.]
-
Trigger1969
- Posts: 137
- Joined: Sat Apr 21, 2007 9:36 pm
- Location: Some backwoods part of Texas
Ok, I'm not sure why, but I just logged into the beta (first time) and I can not input the letter "s" into the lobby chat. I can use "s" for a voicechat command though? Any ideas? I havent tried to use it in game yet, but you'd be amazed how often the letter "s" is used in conversation!
Okay, letter "s" does not work in game chat either. Anyone have any ideas?? 5hoot, typing like thi5 i5 5o annoying.
Okay, letter "s" does not work in game chat either. Anyone have any ideas?? 5hoot, typing like thi5 i5 5o annoying.
Last edited by Trigger1969 on Wed Jul 04, 2007 5:24 pm, edited 1 time in total.

-
Grimmwolf_GB
- Posts: 3711
- Joined: Wed Jul 02, 2003 7:00 am
- Location: Germany
- Contact:
When we were playing the Beta yesterday, Alleg crashed on me like so:
1) The screen gets garbled. Especially the area around the reticle. The garbled parts have what looks like stuff Windows placed in at random (I could make out a menu bar in several pieces). Alephs look like uhh... most of the blue is turned transparent and only the brightest blue streaks show in dark brown. The models are mostly gone to shimmering bits of random textures. Most of the 2D overlays survive though.
2) The game behaves like when it is disconnecting (pings climbing). I can fly around.
3) When I minimized the game to see whats up, I see a windows crash message (with the report option and such). I hit close, Alleg closes. I can get back into Bizarro-Alleg if I want to (maximizes properly).
Looks like an occasion of the E_A_V error.
System:
AMD Opteron 165 on a nF4 SLI based motherboard (A8N-SLI Deluxe) with latest chipset drivers.
ATI X800XT with Catalyst 7.4
All WinXP updates applied, all drivers except display up-to-date. (Newer Catalysts are all Vista and HD2xxx updates anyway).
Some other background info:
When R3 was released, the game become completely unplayable for me. CTDs seconds after launch. Nothing helped. So I created a new WinXP install for the game and the issue was fixed. The problem has come back in a slight way recently, with CTDs every few hours or so (3 seems to be the sweetspot ATM).
Bug #2:
I don't have much info on this, but here goes.
aarm was commanding. A miner wanders into a sector filled with enemies from wherever (I was out in a different sector, hunting enemy miners) and gets promptly raped. aarm goes like so on TS : "See that's something the AI will NOT do in R3." I am not sure about the chain of events that led to it, but I tend to trust aarm on all things commanding (and everything else on that matter), so I think the miner AI code might need another looksee and some rigorous testing.
1) The screen gets garbled. Especially the area around the reticle. The garbled parts have what looks like stuff Windows placed in at random (I could make out a menu bar in several pieces). Alephs look like uhh... most of the blue is turned transparent and only the brightest blue streaks show in dark brown. The models are mostly gone to shimmering bits of random textures. Most of the 2D overlays survive though.
2) The game behaves like when it is disconnecting (pings climbing). I can fly around.
3) When I minimized the game to see whats up, I see a windows crash message (with the report option and such). I hit close, Alleg closes. I can get back into Bizarro-Alleg if I want to (maximizes properly).
Looks like an occasion of the E_A_V error.
System:
AMD Opteron 165 on a nF4 SLI based motherboard (A8N-SLI Deluxe) with latest chipset drivers.
ATI X800XT with Catalyst 7.4
All WinXP updates applied, all drivers except display up-to-date. (Newer Catalysts are all Vista and HD2xxx updates anyway).
Some other background info:
When R3 was released, the game become completely unplayable for me. CTDs seconds after launch. Nothing helped. So I created a new WinXP install for the game and the issue was fixed. The problem has come back in a slight way recently, with CTDs every few hours or so (3 seems to be the sweetspot ATM).
Bug #2:
I don't have much info on this, but here goes.
aarm was commanding. A miner wanders into a sector filled with enemies from wherever (I was out in a different sector, hunting enemy miners) and gets promptly raped. aarm goes like so on TS : "See that's something the AI will NOT do in R3." I am not sure about the chain of events that led to it, but I tend to trust aarm on all things commanding (and everything else on that matter), so I think the miner AI code might need another looksee and some rigorous testing.
Last edited by ImmortalZ on Thu Jul 05, 2007 8:13 am, edited 1 time in total.
I have never had any of these issues with R4. My biggest problem is that some little shyte has a wireless device that is disrupting / dampenning my WiFi connection to the internet. I know said sheot head isn't aware that his actions cause me to plot his murder, but it must be done. ... where was i going with this?ImmortalZ wrote:QUOTE (ImmortalZ @ Jul 5 2007, 05:06 AM) When we were playing the Beta yesterday, Alleg crashed on me like so:
1) The screen gets garbled. Especially the area around the reticle. The garbled parts have what looks like stuff Windows placed in at random (I could make out a menu bar in several pieces). Alephs look like uhh... most of the blue is turned transparent and only the brightest blue streaks show in dark brown. The models are mostly gone to shimmering bits of random textures. Most of the 2D overlays survive though.
2) The game behaves like when it is disconnecting (pings climbing). I can fly around.
3) When I minimized the game to see whats up, I see a windows crash message (with the report option and such). I hit close, Alleg closes. I can get back into Bizarro-Alleg if I want to (maximizes properly).
hm.
yes. please gold this beta. i like the massive additions to game functionality. (options and stuff)

