ARMA II Beta Builds Released: Latest version/build: 1.04.6xxxx

[Natalon 0]

What ATI drivers are you using? Don't forget to add that.

I am using this ATI drivers:

Driver Packaging Version 8.64-090714a1-085212C-ATI

Catalystâ„¢ Version 09.8

Provider ATI Technologies Inc.

2D Driver Version 6.14.10.6983

2D Driver File Path System/CurrentControlSet/Control/Video/{4872859D-BC01-4707-BEA0-3E0AA72F9AD1}/0000

Direct3D Version 6.14.10.0685

OpenGL Version 6.14.10.8870

Catalystâ„¢ Control Center Version 2009.0714.2132.36830

AIW/VIVO WDM Driver Version 6.14.10.6238

AIW/VIVO WDM SP Driver Version 6.14.10.6238

[interox 10]

Latest beta patch + latest nvidia beta driver [191.00]causes my game to look like a photograph negative. The intro scene flying over the carrier and all subsequent images. Prior to installing beta patch all was well apart from ctd's. I'm using the main desktop shortcut with the -no splash -mod=beta switch. If I use the beta shortcut the problem ceases.

[erazor 10]

Or maybe they'll realize that SecuRom 7 doesn't do anything except for inconvenience people so they should just remove it altogether and save us the trouble? That's how I would feel if I was BI!

Agreed - The constant CD drive accessing and ingame stuttering due to this is driving me insane.

Hell often the CD just spins when i don't even have ARMA2 running.. and it does this for extended periods of times which prompts me to take the CD out of the drive. Its madness!

[4 IN 1 0]

Latest beta patch + latest nvidia beta driver [191.00]causes my game to look like a photograph negative. The intro scene flying over the carrier and all subsequent images. Prior to installing beta patch all was well apart from ctd's. I'm using the main desktop shortcut with the -no splash -mod=beta switch. If I use the beta shortcut the problem ceases.

Always remember to run the beta with the shortcut of the .exe within the beta folder and add -mod=beta switch inthe shortcut, otherwise there is notthing anybody could help you if you have the problem

[santafee 10]

Click on "New issue" in the main menu bar; the one with Overview, Activity, Roadmap, Issues, New issue, Wiki.

Make sure the subject you enter is descriptive without being an epic novel, so it's easy for others to skim the lists and see what it is about with only the subject.

Leave Status, Priority, Assigned to and Target version at their defaults as the people that manage the tracker will set them appropriately.

Oh and of course, do a few searches using different terms to see if anyone else has already reported the issue before adding a new one.

Thank you!

[Dwarden 1125]

RFA always was working in way where lower value usually means lower FPS but also lower lag ... (at least that's what i experience with any title i tested it with)

values 0 and 1 could be unstable, value 3 is default by most drivers...

for most people the sweet spot is 2 or 1 depending on theirs setup ...

@Natalon: are you sure You are running the game with -mod=beta ?

because video error You shown looks like bin.pbo wasn't updated together with binary

Edited September 23, 2009 by Dwarden

[KeyCat 131]

Just tried the 59210 beta and also experience some wierd "strobing" effects, not as bas as SnR but still. Also using fog creates new problems, white anomalies on fences and road textures.

Running Windows XP Pro SP2 and nVidia GTX 260 with 182.50 WHQL.

/KC

[Bulldogs 10]

It's a general FPS issue that is hard to explain to some people. You have to remember that if you lower the MaxprerenderedFrames then you lower your FPS (not significantly, but it can be noticeable), but the plus side being that it can remove mouse lag issues.

For this point, as mentioned avoid 0 or 1 values as that has a tendancy to nuke your fps (basically it's not pre-rendering frames, so when it go's to load the next frame on screen it looks in the buffer, see's nothing and has to wait for the next frame to load)

[InFireBaptize 0]

GPU_MaxFramesAhead=1000;

What does it do and what's the optimal setting?

[Natalon 0]

@Natalon: are you sure You are running the game with -mod=beta ?

because video error You shown looks like bin.pbo wasn't updated together with binary

Yes, i am sure...

btw.. it is not the first beta, i have installed... ;)

Edited September 23, 2009 by Natalon

[MehMan 0]

You need to run it with the beta executable, not the regular arma executable.

[mlenser 10]

Natalon, Wouldn't it be in your case "D:\ArmA2\ArmA2 Game\BETA\arma2.exe" -nosplash -mod=beta

You appear to be running the main exe?

[Natalon 0]

Natalon, Wouldn't it be in your case D:\ArmA2\ArmA2 Game\BETA\arma2.exe -nosplash -mod=beta

You appear to be running the main exe?

No, i dont run the main exe... ich made a backup of the main exe and copied the beta.exe in the normal directory

There is no different, if i change it in D:\arma2\arma2 game\beta\arma2.exe -nosplash -mod=beta

Edited September 23, 2009 by Natalon

[Bulldogs 10]

Then you've corrupted your install. Replace the beta exe with your originial one in the main directory, then install the beta to the \beta directory and change your shortcut to ArmA2 install dir\BETA\arma2.exe -nosplash -mod=beta

[-HA-badger 0]

After the beta build 59210 I have more image problems. For example:

- Flashing textures

- Periodically completely darkening the screen

- Do not load close lody

In patch 1.04 there was no such problems, as in the previous one patches. My graphics card is Nvidia GF 8600 GTS

[SnR 1]

@SNR:

Did you read my post before yours?

Check that.

I just had a look at it and see no answer to the problem ?

Thanks anyway

My fix is to switch Post effects off, which stopped the constant strobing.

But im seeing minimal flashing textures around the weapon, hands and lots more.

ATI 9.9 Drivers

[Seitan 8]

badger;1446284']After the beta build 59210 I have more image problems. For example:

- Flashing textures

- Periodically completely darkening the screen

- Do not load close lody

In patch 1.04 there was no such problems' date=' as in the previous one patches. My graphics card is Nvidia GF 8600 GTS[/quote']

All the same problems here with latest beta 59210. :j:

8800GT here. No problems with previous betas or 1.04.

[Herbal Influence 10]

First time I am having problems.

I installed all beta patches after they have been released and they ran fine.

Then I upgraded to 1.04 - ran fine.

Just now I tried to install the newest beta patches for 1.04.

Systems says: "You only have 1.03 - need to have 1.04"

But as I said, I HAVE 1.04 running.

At last installing it was easy and in the main screeen on the right bottom side it says that I *am* running 1.04 ...

Clueless ... :-(

[InFireBaptize 0]

First time I am having problems.

I installed all beta patches after they have been released and they ran fine.

Then I upgraded to 1.04 - ran fine.

Just now I tried to install the newest beta patches for 1.04.

Systems says: "You only have 1.03 - need to have 1.04"

But as I said, I HAVE 1.04 running.

At last installing it was easy and in the main screeen on the right bottom side it says that I *am* running 1.04 ...

Clueless ... :-(

check post#832.

[Herbal Influence 10]

Wow - thanx! Fast response ! Did work !

[snake eyes 0]

I'm getting this problem since before 1.04 [introduced in the 1.03 betas]

Also in the civie boat with the canopy their heads stick through:(

Edit:Alright I just double checked and it appears that the Female civilians are having a problem.. i tried the rocker/USMC etc. and only those models are standing while in cargo [i'll do more testing, but so far that's the problem]

All the men, civilians/Soldiers worked as they should.

Edited September 23, 2009 by snake eyes

[rundll.exe 12]

@snakes eyes

That bug has been around from the beginning.. Females dont have the animations defined for a lot of proxies I think, just lazyness from BIS to make them ;)

@Alex72

No offence here, but can you try to get your findings a bit more scientific when you post them? I really like your enthousiasm, but it also seems to cause confusion for others. For example, rendering 500 frames in advance would mean a lag of 20 seconds at 25fps. So you could have figured that it was not a valid setting anyway, your drivers will go to the max value then (2/3/4).

Also the cfg looks like this for me

GPU_MaxFramesAhead=1000;

GPU_DetectedFramesAhead=4;

So it seems that my drivers default (and max) to 4, and I didnt really feel mouse lag at 25fps. And there isnt much change in responsiveness when I set GPU_MaxFramesAhead to 1 or 0. It just seems more choppier. So I guess this is only for the people who really suffer from input delay.

Notice that after changing GPU_MaxFramesAhead, GPU_DetectedFramesAhead will change to the same value, when its lower as the default. (with GPU_MaxFramesAhead at a large value), so it doesnt make sense to manually set that one afaik.

[snake eyes 0]

@snakes eyes

That bug has been around from the beginning.. Females dont have the animations defined for a lot of proxies I think, just lazyness from BIS to make them ;)

Strange i could of sworn i did not have that problem before the beta patches:o

[NoRailgunner 0]

With latest beta version I got huge arma2.RPT files (~10MB default SP mission) - lots of them are mainly (numbers differ):

DebugFSM: 251,-1 "animHandler" condition: 2 ""

DebugFSM: 251,-1 "ca\Modules\BC\data\fsms\animHandler.fsm" state: 21 "BC_React2_1"

DebugFSM: 256,-1 "animHandler" condition: 1 ""

DebugFSM: 256,-1 "ca\Modules\BC\data\fsms\animHandlerNon.fsm" state: 19 "BC_React4"

DebugFSM: 257,-1 "animHandler" condition: 2 ""

DebugFSM: 257,-1 "ca\Modules\BC\data\fsms\animHandler.fsm" state: 18 "BC_React3"

DebugFSM: 251,-1 "animHandler" condition: 0 ""

DebugFSM: 251,-1 "ca\Modules\BC\data\fsms\animHandler.fsm" state: 7 "END"

DebugFSM: 256,-1 "animHandler" condition: 2 ""

DebugFSM: 256,-1 "ca\Modules\BC\data\fsms\animHandlerNon.fsm" state: 20 "BC_React1_1"

DebugFSM: 260,-1 "animHandler" condition: 2 ""

DebugFSM: 260,-1 "ca\Modules\BC\data\fsms\animHandlerNon.fsm" state: 17 "BC_React2"

DebugFSM: 2,-1 "agony" condition: 0 ""

DebugFSM: 2,-1 "ca\Modules\AIS\data\fsms\agony.fsm" state: 3 "A_T___E_A_S_E"

DebugFSM: 3,-1 "agony" condition: 6 ""

DebugFSM: 3,-1 "ca\Modules\AIS\data\fsms\agony.fsm" state: 25 "AIS_Agony_Freeze"

DebugFSM: 29,-1 "Idle Special Anim" condition: 0 ""

DebugFSM: 29,-1 "CA\animals2\Data\scripts\idleSpecialAnim.fsm" state: 1 "play_anim"

DebugFSM: 29,-1 "Idle Special Anim" condition: 0 ""

DebugFSM: 29,-1 "CA\animals2\Data\scripts\idleSpecialAnim.fsm" state: 2 "Continue"

DebugFSM: 29,-1 "Idle Special Anim" condition: 0 ""

DebugFSM: 29,-1 "CA\animals2\Data\scripts\idleSpecialAnim.fsm" state: 3 "set_Timer"

Something screwed the FSM/AI :confused:

[Pauldarrington 9]

I was testing around in the editor with the beta and i think i came across the sound cutting out and then popping back again but only for about 2-3 secs then everything is fine, this includes mulitiple weapons being fired