Beta build 71275 is up!

[Alex72 1]

I had my first CTD with a beta when i tested this one yesterday (vanilla A2). I was in Chernogorsk and was turning around when it happened. I usually test this with the betas to feel it out and it never gave me a CTD.

Will test more when i get home from work.

[jpinard 10]

What I'm most impressed by is your personal benchmarks, because like you said, the _FPS_6 bench does not show a lot of variance between betas, where your benchmarks definitely do.

Yes, you've got to turn the view-distance up to 6000+ before you start to see any meaningful separation in _FPS_6 on my rig.

The HeloTest is by far the most comprehensive. Skimming treetops at a decent clip for 2 minutes, then the latter stage moves into a small battle. Just enough to force the AI to think, deal, the graphics get pushed not by blowing by trees but by the special effects of fire, smoke, explosions, the close formation firing Helos, and vocal cues. The Jet-Test skims along the whole of Chernarus at high subsonic and supersonic speeds, then tops it off with a little hill-top target practice for the AI at the end. This is perfect for really pushing the new thread-streaming algorithm BI is using.

With both tests being 4 minutes you get a very good frame-check and a meaningful average fps.

Edited June 9, 2010 by jpinard

[dogz 10]

jpinard it looks like you have good attention to detail and you appear to be quite thorough.

May I ask why you do not list your HD spec in your system specs???

May I also ask what it is?

[NoRailgunner 0]

langgis08 in this case BIS screwed up the chain of command.

Actually in A2 the player as team/groupleader has to wait on his AI #2 to declare "its safe".

Thought, another idea would be that the AI follow order if those order are repeated by player.

I dont say AI should follow given orders within a millisecond but at least they should follow them - no matter in which situation they are.

[Big Dawg KS 6]

langgis08 in this case BIS screwed up the chain of command.

Actually in A2 the player as team/groupleader has to wait on his AI #2 to declare "its safe".

Thought, another idea would be that the AI follow order if those order are repeated by player.

I dont say AI should follow given orders within a millisecond but at least they should follow them - no matter in which situation they are.

Open an issue in the CIT to request a new command for player leaders to say "Clear" or "It's safe" (same command, different ways of saying it). It should make your team forget about enemies you can no longer see, and only work if there are no enemies still in sight. Much better than simply forcing the AI to assume a given behaviour against their will.

[jumpinghubert 49]

I had my first CTD with a beta when i tested this one yesterday (vanilla A2)..

me too, first time I get ctd with a beta.

[SnR 1]

Vanilla MP gaming all night with no problems at all

[flake 10]

not played sp in a while. tried this beta and its amazing. smooth, looks great and plays really well and the jerky anims is fixed! :D

[bangtail 0]

No CTD's to speak of in a few hours of editing and playing.

I'm using ACE2 and several other mods.

[RadicalAtHeart 11]

Game suddenly freezes or FPS drops to 3 FPS. The only way to end the game is by going to task manager.

However I like this beta.

[maturin 12]

Game suddenly freezes or FPS drops to 3 FPS. The only way to end the game is by going to task manager.

However I like this beta.

I have also been getting freezes leading to very stubborn, drawn-out crashes with the last few betas. It's surprising, because Arma is usually so well-behaved in that regard. It also crashes harmlessly on exit sometimes.

[-=seany=- 5]

CTD is fixed while loading the 3rd party islands, but I have discovered I now get ctd during play after about 10 minutes with this beta on Duala. Without the beta is fine.

-exthreads=7

[jpinard 10]

jpinard it looks like you have good attention to detail and you appear to be quite thorough.

May I ask why you do not list your HD spec in your system specs???

May I also ask what it is?

I have 5 HD's. But you're correct that information is definately relevant. I'll add to my system secs in my first post.

Edited June 9, 2010 by jpinard

[langgis08 10]

By default the game now uses exThreads=7 with a quad-core processor.

Good information, so everyone with a quad-core should get bests results by setting no exThread-parameter at all (if his/her tests with -exThreads=7 have beaten the other parameters, of course).

For me this is the case and so I removed -exThreads=N from command line - having same results as with -exThreads=7.

[Herbal Influence 10]

Everythings fine, performance better during the last betas, but AIs are as difficult to command as before one, two patches.

In simple Sector control mission they don't follow, they don't obey orders, they are so frightened that they stay behind enormous times and walks ssoooooo slowly ...

I thought that this problem mas solved ... but it's here again ... :-(

[Protegimus 0]

Excellent performance is maintained in forest and builtup areas, with FPS rarely dipping below 35. LOD switching is almost imperceptable running from the ramdrive and I was able to increase object and texture detail to very high without the penalty in loading time usually experienced as players view pans and zooms around.

Stability is unfortunately an issue though, with random CTD's experienced - might be 10 minutes, might be 110.

Occasional crash on exit too, as maturin reported.

Parameters -cpuCount=8 -exThreads=7 -maxmem=2047 but testing without parameters doesn't appear to matter.

I see man and child soldier classes have their sensitivity raised to 3.75 in the hotfix.pbo - would be great to know what core change requires this, or what it is aimed at improving.

Protegimus

Edited June 10, 2010 by Protegimus

[chrisg2110 10]

Game crash to Desktop with Beta Patch 71275 :( last Stable Version is 70951.

My System:

Intel Core I7

6 GB DDR 3

ATI 5870

Windows 7 64bit

[Fireball 16]

I've been trying some single player (EW campaign) with -exThreads=7 and since I had a sluggish feeling ("jumping" movement), switched back to -exThreads=3. The jittery movement didn't go away, so I terminated Skype which had blown up itself again to ~200 MBs memory usage and then it was smooth again.

And as expected, switching back to -exThreads=7 it's all fine, but with my GPU I didn't expect improvements;

Indeed that is the case, but it was still a recordable difference; the coastal flight FPSAnalyzer curve (% spent below fps) looks a bit flatter on the top than with -exThreads=3 (thus the high FPS shots had average more FPS again), the average FPS has improved by 1.

One thing I noticed; the scripting performance went bad drastically again; after one hour of host server of a Warfare BE session, 1 "second" of the respawn timer equaled roughly 2 real life seconds again.