Jump to content
Sign in to follow this  
BL1P

What happened to these changes ?

Recommended Posts

ARMA 2: OA beta build 93825 (1.60 MP compatible build, post 1.60 release)

[93812] Fixed: Restrict gamma value set by profile

[93809] Fixed: Restrict brightness value set by profile

At one point we could lock the gamma and brightness on a server.

But it seems it was removed any ideas why ?

Or if its still possible to do in some other way now ?

Share this post


Link to post
Share on other sites

can anyone else confirm ? what build is affected ? 104648 ? which build was last when it was working fine ?

Share this post


Link to post
Share on other sites

The version of beta on the server we are running is "Beta patch 102591"

And gamma and brightness can be turned upto 2.0 and 1.5

How would we go about doing any tests to see if this function/restriction is working correctly or not ?

Share this post


Link to post
Share on other sites

set it e.g. to 5.0 in client's profile file (while game isn't running) and then start it

Share this post


Link to post
Share on other sites

so I tested 1.62.104648 and i'm unable to set the value beyond maximum in GUI ...

value of 10 is ignored from profile file, so all works as it should

so where is the bug?

Share this post


Link to post
Share on other sites

Maybe im missing the point of the addition to the beta.

I was thinking it was so that servers can restrict the amount players can turn up gamma and brightness.

as in the servers profile has the gamma and brightness settings of :-

gamma=1;

brightness=1;

but even with them set at =1 you can still turn up your gamma to 2.0 and brightness to 1.5.

Sorry if im being dumb just trying to figure this out.

Share this post


Link to post
Share on other sites

no it's just clientside limit so you can't set values over GUI max, there is no server side control on this

Share this post


Link to post
Share on other sites
so I tested 1.62.104648 and i'm unable to set the value beyond maximum in GUI ...

value of 10 is ignored from profile file, so all works as it should

so where is the bug?

O I think I get what its doing now.

It just stops people going above GUI settings of 2.0 for gamma and 1.5 for brightness

ok sorry to bother you Ill go see if I can find a way to restrict it to defaults of 1.0 and 1.0 somehow

So we can play nights knowing none are using high gama.

Thank you very much for your help sorry I misunderstood the purpose of the feature.

Share this post


Link to post
Share on other sites

just use image tone mapping :) e.g. in mission's init.sqf

"filmic" setToneMappingParams[0.153,0.357,0.231,0.1573,0.011,3.750,6,4]; setToneMapping"Filmic";

Share this post


Link to post
Share on other sites
just use image tone mapping :) e.g. in mission's init.sqf

"filmic" setToneMappingParams[0.153,0.357,0.231,0.1573,0.011,3.750,6,4]; setToneMapping"Filmic";

Thanks again but ...

Actually this is already in the init.sqf

Copied from init.sqf :-

"filmic" setToneMappingParams [0.153, 0.357, 0.231, 0.1573, 0.011, 3.750, 6, 4]; setToneMapping "Filmic";

Should that stop it ?

Because if so it isnt :)

Edited by BL1P

Share this post


Link to post
Share on other sites

yet why you think it's solveable (more than limitations we imposed and use of filmic)

anyone can increase gamma / brightness via injectors like sweetFX post process , via AMD/NVIDIA drivers and via monitor settings ...

Share this post


Link to post
Share on other sites
yet why you think it's solveable (more than limitations we imposed and use of filmic)

anyone can increase gamma / brightness via injectors like sweetFX post process , via AMD/NVIDIA drivers and via monitor settings ...

All true.

was just looking for a way to play night without people just turning up gamma ingame.

If it cant be done.. it cant be done. no worries perm day is cool aswell.

Thanks for your help with everything.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

×