Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

Most Stable 2.5?

20 replies · 3,978 views · Started 15 February 2009

Link wrote:Always the current one, although occasionally there's the odd exception.

Like, for example, the current one. There's some serious problems with the last few builds. Build 910 is the way to go right now.

Always use the latest one. How do you think bugs get discovered and then fixed? If you don't use the latest ones, we're destined to be far away from 2.5's release forever.

Beta Link wrote:Like, for example, the current one. There's some serious problems with the last few builds. Build 910 is the way to go right now.

Actually no, the only issue was with 935.
It's fixed now.

I actually agree with Gleeok, but it's still important for people to bug test the latest builds. If you don't want to be bothered with bug testing (and still want to build your quest in v2.5), then build 910 is the way to go.

If you have XP, double click on the volume button at the bottom right of the desktop, and turn SW Synth all the way up.

FefeRawft wrote:Thanks, does anyone know why that happened?

For some reason, ZC uses the same Play/Pause/Stop status and volume as Windows Media Player.

Gleeok wrote:Lies! Everyone knows the 1.90 DOS version is the bestest & mostest stable! *runs away*

lol

Joe123 wrote:What's making it crash?

v956
I've had problems with AUTOSAVE causing it to crash. So I disabled it. Then just regular SAVE would cause a crash. And then sometimes it would just crash. I had made a bug topic about it, but it looks like it got moved/deleted. Probably from my lack of posting here on agn as compared to purezc. I'm running XP and using the ZC-Launcher it comes with. I've even tried using it without the Launcher as well and get the same thing.

ADD IN EDIT- slightly off topic - The ABOUT section under ETC still says ZC 2.11 build 18 for all of my betas dating back to v492 (including v956). I didn't know if that needs to be updated so people can give the correct build/version # when designating problems since some people just replace the "old" version with the new one and not pay attention to what they are currently on. I have all of my builds that I have downloaded in seperate folders, so I don't have a problem.
Just an observation is all. Maybe build means something different than version, if so, sorry for wasting your time in reading this long drawn out edit.