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

[Bulldogs 10]

EDIT : Wasn't quite focusing properly. What's actually happening with the value is that if you set

GPU_MaxFramesAhead=1000 then it will take that as your maximum range but will detect what the GPU's drivers are set to and use that value, hence the GPU_DetectedFramesAhead=4 which means that your drivers are set to a value of 4 (look under nVidia control panel, Max-prerendered frames)

The purpose of this being that if you set the frames to their driver maximum (being 8) then the GPU_DetectedFramesAhead=8, but if you lower the Max value to GPU_MaxFramesAhead=3 then it will ignore the drivers value and force the Rendered Frames to 3.

Edited September 24, 2009 by Bulldogs

[maddogx 13]

How come I just got another Beta Informer mail about the 59210 beta patch? I can't check the beta patch site right now.

[Natalon 0]

Post-Processing courses the problem with the grafic. It only occur if the setting of pp is "low".

You don't get the problem if the setting is disabled or "high" or "very high"

C6wPSuz5ODs

[Dwarden 1125]

natalon fully uninstalled beta and installed new one , using correct binary in correct place with correct -mod=beta ? :)

[Natalon 0]

natalon fully uninstalled beta and installed new one , using correct binary in correct place with correct -mod=beta ? :)

surely :)

[Alex72 1]

@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).

I think Kju sorted that right after my post didnt he? I couldnt find any scientific info on the matter so i tested values wich i posted. That was wrong and apologize heeps to you. And no i dont have the same understanding of those values like you maybe have. Very sorry about that.

_____

Those settings doesnt seem to do much however. Mouse still skipping during action. BIS is it impossible to implement the old mouse handling along side the new with a button or some cfg value tweak on/off?

SnR:

The answer to your problem what was i wrote there. You need to add -mod=beta to your target line. Many have had the same problem as you - including me - and the problem was that none of us used that command.

EDIT:

Dont know if we got any answer to if these 2 new additions in the ARMA2.CFG needed VSYNC OFF to work properly? I turned it off to test and it seems skipping is less in the beta when i do. No "scientific" data to back it up though. Feeling again.

Edited September 24, 2009 by Alex72

[SnR 1]

Cheers

I use Arma Launcher and identify the beta exe within its folder, obviously dosent work with this beta.

You need to add -mod=beta to your target line

again sticking with Arma Launcher i used this in its options and it now works

[ShaiCZ 10]

Using 59210, I am getting totally unbelievable increase in performance against 1.03 (couldnt verify pure 1.04 - the new beta came out sooner:o). I have NO popping up textures, no flashing textures, no silver heads, nearly all setting maxed out! Brilliant!

BIS is making some real progress here!;o)

[Dwarden 1125]

and more to come ;)

[eJay 1]

Using 59210, I am getting totally unbelievable increase in performance against 1.03 (couldnt verify pure 1.04 - the new beta came out sooner:o). I have NO popping up textures, no flashing textures, no silver heads, nearly all setting maxed out! Brilliant!

BIS is making some real progress here!;o)

Opposite of this, I'm still seek for better performance. Maybe beta fixed some things in visuals but not in general issues like FPS drop in villages. Still, ArmA II is a mystery from technological point of view. I've got 20-25 frames per seconds with high details while walking in Novy Sobor and about 25-35 while everything on lowest (500 m vd, ugliest textures, no grass, no Posteffects). This is not a huge boost as I see in other games.

[Cionara 10]

New beta runs very smotth but got same bug like Natalon.

Post-Processing courses the problem with the grafic. It only occur if the setting of pp is "low".

You don't get the problem if the setting is disabled or "high" or "very high"

Light is blinking all the time like in a disco.

No matter what settings I choose.

Edited September 24, 2009 by Cionara

[InFireBaptize 0]

i still don't understand those two variables introduced in this patch, are we suppose to leave them on default or play with numbers? when i checked the cfg file they were like this:

GPU_MaxFramesAhead=1000;

GPU_DetectedFramesAhead=2;

should i leave it the way it is?

[Bulldogs 10]

You can leave it that way if you want. Basically you can ignore the first value for now, the second value GPU_DetectedFramesAhead is telling you that this is the setting in driver setup (max-prerendered frames under Nvidia control panel/Ati control center->3d settings), so if you like you can change it under that, but if not then you can raise it under that to a maximum of 8, then you can raise the first value GPU_MaxFramesAhead to what you want it to be for Arma (like 3,4, whatever)

But since it's already detecting that yours is set to 2 then you can leave it there for maximum mouse performance, although, if you want to increase your fps (maybe slightly, maybe more) then goto the nvidia/ati control panel like I mentioned and change your max-prerendered frames to 8 and delete both those lines from Arma2.cfg so that arma 2 reloads them.

Little confusing sorry, but not very good at explaining it.

[bangtail 0]

You can leave it that way if you want. Basically you can ignore the first value for now, the second value GPU_DetectedFramesAhead is telling you that this is the setting in driver setup (max-prerendered frames under Nvidia control panel/Ati control center->3d settings), so if you like you can change it under that, but if not then you can raise it under that to a maximum of 8, then you can raise the first value GPU_MaxFramesAhead to what you want it to be for Arma (like 3,4, whatever)

But since it's already detecting that yours is set to 2 then you can leave it there for maximum mouse performance, although, if you want to increase your fps (maybe slightly, maybe more) then goto the nvidia/ati control panel like I mentioned and change your max-prerendered frames to 8 and delete both those lines from Arma2.cfg so that arma 2 reloads them.

Little confusing sorry, but not very good at explaining it.

It seems that since 1.04, pre rendering (8 FPS) no longer yields the dramatic increases it once did. This could be a function of the newer 191.00 driver set or something that BIS has changed but I was testing it yesterday and the difference was negligible (if there was any at all).

Eth

[Yoma 0]

For all you guys not being able to decently launch beta's:

If you use AddonSync2009 and add a modset containting the beta folder, you can easily launch the beta in a correct way without all the screwups that seem to be all over the place...

Surely the goal of a beta cannot be to detect that people can't use the beta :p

[InFireBaptize 0]

You can leave it that way if you want. Basically you can ignore the first value for now, the second value GPU_DetectedFramesAhead is telling you that this is the setting in driver setup (max-prerendered frames under Nvidia control panel/Ati control center->3d settings), so if you like you can change it under that, but if not then you can raise it under that to a maximum of 8, then you can raise the first value GPU_MaxFramesAhead to what you want it to be for Arma (like 3,4, whatever)

But since it's already detecting that yours is set to 2 then you can leave it there for maximum mouse performance, although, if you want to increase your fps (maybe slightly, maybe more) then goto the nvidia/ati control panel like I mentioned and change your max-prerendered frames to 8 and delete both those lines from Arma2.cfg so that arma 2 reloads them.

Little confusing sorry, but not very good at explaining it.

thanks, better now. The thing is unless i'm missing something but ATI control panel doesn't have such thing to adjust! that's what confused me, if i changed it in the cfg file that wouldn't conflict with the ati driver?

[Bulldogs 10]

I'm not sure what ATi calls it but it should be there somewhere.

As for conflicting, maybe but I doubt it. In all likelyhood when you change it in the cfg it will ignore it if the number is above the driver set and it will use the driver setting instead. I could be wrong though.

[kklownboy 43]

Ati doesnt have the option in the CCC, you can regedit, or you can use Rays tool. Which then you could also turn off Vsync in vista and win7 if you where so inclined. As for me on my ATi H/W it never really made any performance/improvement over stock "render ahead" it only made it worse... But then my mouse/input is fine has always been fine. But on my 9800gx2 i had to play with it alot...

[InFireBaptize 0]

Ati doesnt have the option in the CCC, you can regedit, or you can use Rays tool. Which then you could also turn off Vsync in vista and win7 if you where so inclined. As for me on my ATi H/W it never really made any performance/improvement over stock "render ahead" it only made it worse... But then my mouse/input is fine has always been fine. But on my 9800gx2 i had to play with it alot...

hey,

Can you run ray tool with ati together! would turning vsync off boost fps?

[randir14 10]

It's ATI Tray Tools

http://cid-a50350ea7a969f0c.skydrive.live.com/self.aspx/Public/attsetup.exe

I don't know if you can run it together with Catalyst Control Center but there's no point since ATI Tray Tools has everything CCC has and more. The setting in ATI Tray Tools is called Flip Queue Size.

[bluesteel 0]

The new settings for max_frames_ahead control how many frames the CPU can prepare while the GPU is still busy with the current frame. Typical values are between 0 and 10, anything higher is not practical. Let me explain:

Think of this value as the amount of frames your GPU - and the picture you see on the screen - is late with processing. While you see frame #10, your CPU is already preparing frame #20 to be rendered. Since your mouse inputs are tied to the CPU, this means that when you finally see frame #20, your mouse input will be what you did 10 frames ago.

If you set the value to 1000 and your framerate is 30fps, then you enable your CPU to hypothetically prepare so many frames ahead, that the picture on your screen is over 30 seconds old. That equals a mouse lag of half a minute.

That is why values over 10 are not practical, as they would induce a lag of a third of a second (333ms) at 30fps already. Most likely other factors limit this anyway, I doubt the system can build up a buffer of 1000 pre-computed frames that wait to be sent to the graphics card. Personally I can sense the difference between values of 1 and 3 already, with 3 introducing slight but noticable mouse lag. This is using the option in the NVIDIA control panel, but I assume the ingame controls will behave similarly.

Most likely the game can not even override the value you have set in your ATI or NVIDIA control panel, so values larger than what you have set up there should will not have any effect. Only lower values should be able to do any difference.

[Maddmatt 1]

Most likely the game can not even override the value you have set in your ATI or NVIDIA control panel, so values larger than what you have set up there should will not have any effect. Only lower values should be able to do any difference.

That is correct. You can tell by looking that the "MaxFramesDetected" (or whatever it's called) parameter after quitting the game.

[von_paulus 0]

With this last beta I'm having much more flickering than ever did.

I tried in both in win7 and in win xp. Without the beta I've the usual flickering (texture).

With beta, flickering is everywhere even when I press esc and the image get blurred there is flickering in the lightest parts of the image.

[Bulldogs 10]

Does disabling post processing get rid of the problem?

[kuIoodporny 45]

Latest Beta is Fail, first beta to have any negative effects for me:confused:

Loaded up with pre beta settings, and had constant strobing / screen flashing

in the LHD view.

Went into editor, and found all texture strobing like a Xmas tree.

Turned Post Process OFF and it minimised the problem.

ATI user severely effected by 59210:butbut:

anything about -mod=beta ?