'GPU_DetectedFramesAhead' random values?

[fred41 42]

... i am trying to find out, why the value 'GPU_DetectedFramesAhead' in 'arma3.cfg' becomes sometimes '1' and sometimes '2'.

It seems arma is 'testing' something at game start and later writes a resulting value in arma3.cfg.

Does someone, devs included, know, how this value is calculated and why it gives different values under same conditions?

Thanks.

[RuecanOnRails 10]

I'm not sure how it's calculated, or why it's giving different results each run. It's likely calculated during launch with the quick benchmark/hardware test. Try running -nobenchmark and see if it still changes. Would making the arma3.cfg read-only be a temporary solution?

Are you able to make a repeatable mission or set up that others can confirm and test?

[mp5gosu 10]

I guess, it is VSYNC related. For example, if you have stable 60+ FPS, it will get capped at 60.(relates to value of 2). If you have 30+ FPS but less than 60,it will get capped at 30 (value of 1). Not sure what these values are in particular. Maybe that 60 refers to 1 and so on.

Gesendet von meinem Nexus 7 mit Tapatalk

[kklownboy 43]

mine never changes when set

GPU_MaxFramesAhead=1;

GPU_DetectedFramesAhead=1;

Or any value/number set on both of them(1-4, tho max is 8) This is with a AMD card.

Vsync has nothing to do with it.

[fred41 42]

Ok guys, thanks for your answers.

Based on your replys i found the following:

1. 'GPU_DetectedFramesAhead' is still modified by arma, even with '-noBenchmark'

2. without any load, 'GPU_DetectedFramesAhead' is always set to 1 on my system, with vsync=ON/OFF

3. with heavy load (synthetical loop in onEachFrame event) arma sets it to 1, if VSYNC is ON and to 2, if VSYNC is OFF

CONCLUSION:

It is not randomly and seems to have some meaning :)

[megagoth1702 252]

Any updates on this?