AfterWorld Survival Forum

With the release of the C209 update we have published news on the main website:
The public release of AfterWorld Survival.


Release notes of the C209 update:

• Fixed crash on exit
• Enabled sounds in game
• Fixed some mobs which had missing/bad textures
• Fixed Dire Wolf animation issues
• Fixed AI logic, so mobs don't run away too far from their original spawn location
• Fixed server crash under certain circumstances (AI related)
• Minor performance improvement (when used medium quality settings)

FYI, i dont think sound is working, it's not for me, unless it needs to be activated somehow.

You need to enable it via Options panel.
Though, the sound effects is still work-in-progress, we don't have yet sounds for everything. In a future updates, we will bring more.

Quote from: Zen "ZenX" Star on August 24, 2012, 02:15:15 pm

FYI, i dont think sound is working, it's not for me, unless it needs to be activated somehow.

You need to enable it via Options panel.
Though, the sound effects is still work-in-progress, we don't have yet sounds for everything. In a future updates, we will bring more.

I had previously gone to Options and seen it was Enabled so i tried alternate Output Device, with no luck.
After reading your reply i went back into Options, Dis-Enabled Sound, Re-Enabled Sound, changed Device Option back to Speakers and could instantly hear sounds

Cheers
Zen

Please..
-Random "freezes". Game UI is responding, menus do work, PDA opens,but avatar does not move. Switching between mouse/cursor works but avatar stays motionless along with crosshair (crosshair stays motionless, no matter how much I move the mouse itseld). After switching to mouse, it's cursor responds.
- Fix respawning in the river "behind" Mugen after client freeze/crash. After relog you often enough discover yourself in the bottom of a river taking "dark matter damage".. Unable to heal or getting out of off the river in time.. ends up with another clone uselessly wasted..
- Fix spawning in "unrecognized location", usually just endless falling trough the air. There is no way out other than Ctrl+D and it always ends up in Mugen again.. Another clone wasted, again.[/i]
those major issues are taking away all enjoyment for now. Feels utterly pointless going out of Mugen, rather sooner than later you are going to end up there again.. Actually it feels like there is no point whatsoever to play. I could run and play with Steppe Spiders but even there, although it's easy to survive, sudden freeze could force you relog and then you are back in Mugen. I hate Mugen.

-While logging in with Minimal settings, with Nvidia at least, I see no ground and very little object textures. After setting the graphics to "low" INGAME, ground appears, most of the closer objects have orange "no material" texture on it. After brining the graphics up more, "medium" or "high", you have very little trees or bushes visible, but you can see all the animals just nice.. I am not sure if it goes under exploit.

In the absence of version information i suppose if we supply the date the last update took place it should allow DL to know what software is running.

Zen

already works here!

If we have to start adding the date and time, then we have to start tracking more information every time we find a bug and the whole point of version numbers is essentially moot from a testing perspective.

The whole point of versions is to allow teams to track changes back to a single known point.

Oops, I meant from the tester's perspective, not testing itself. Obviously version numbers are far more important to the developers.

And it's a valid idea to note the time and date for these small interim updates with no new version numbers because it could help pinpoint the causes of specific bugs. But my guess is that they did not give either update the version number C210 because they fixed very small, very specific bugs and did not need to touch other code. Therefore, any bug that is newly reported after one of these mini updates is either directly related to the fix (which should be easy to spot) or not directly related, in which case it's related to the rest of the game code instead. So just reporting that a new bug was discovered in C209 is clear enough for the devs.