Permanently turn OFF HDR???

[Radic]

HDR at the best of times is not something I'm very fond of - I can understand the significance of it tactically in a game like ArmA - ie. field of view glare etc. - but IMO it's implementation in ArmA is flawed particularly with respect to NVG usage.

Anyhow, I found I can turn it off by setting HDRprecision=0 in arma.cfg - but somehow the bastard thing keeps being reactivated - I quit the game and go to the .cfg and sure enough it's back at 8

Anyone know what's causing this??

[warchlaq]

Set attribute "read only" on this file.

[weedomatic]

Quote[/b] ]Posted: Feb. 20 2007,12:53 ***

The HDR cannot be disabled because realistic lighting values are used in Armed Assault. This means the daytime light is about 1000x brighter than early morning. Therefore HDR needs to be present, otherwise you would often see nothing (only black or only white, as with under/overexposed photograph).

--------------
Ondrej Spanel, BIS Lead Programmer

[Suma:2007]

[Radic]

Quote[/b] ]Posted: Feb. 20 2007,12:53 ***

The HDR cannot be disabled because realistic lighting values are used in Armed Assault. This means the daytime light is about 1000x brighter than early morning. Therefore HDR needs to be present, otherwise you would often see nothing (only black or only white, as with under/overexposed photograph).

--------------
Ondrej Spanel, BIS Lead Programmer

[Suma:2007]

Point taken - in fact I think setting that HDRprecision value to zero just dials right down the HDR effect as I still get glare when facing the sun etc. yet at night it does make NVG view of consistent intensity (values such as the default 8 cause complete darkness in certain direction of view with NVG's at night).

I might try the read only attribute approach - and also I think it's possibly being set to 8 whenever I alter ANY ingame video option settings - ie. which subsequently cause the game to write to that .cfg file.

[Max Power]

This has been discussed quite a lot. I'm sure that the search function would have been literally ripe with returns.

[Radic]

No, you'd be surprised how little useful info a search yielded - that's why I posted.

[Maddmatt]

Quote[/b] ]Posted: Feb. 20 2007,12:53

The HDR cannot be disabled because realistic lighting values are used in Armed Assault. This means the daytime light is about 1000x brighter than early morning. Therefore HDR needs to be present, otherwise you would often see nothing (only black or only white, as with under/overexposed photograph).

--------------
Ondrej Spanel, BIS Lead Programmer

[Suma:2007]

Point taken - in fact I think setting that HDRprecision value to zero just dials right down the HDR effect as I still get glare when facing the sun etc. yet at night it does make NVG view of consistent intensity (values such as the default 8 cause complete darkness in certain direction of view with NVG's at night).

I might try the read only attribute approach - and also I think it's possibly being set to 8 whenever I alter ANY ingame video option settings - ie. which subsequently cause the game to write to that .cfg file.

Setting HDR precision to 0 does nothing because there is no such thing as 0-bit HDR (or at least it wouldn't work). ArmA just switches back to 8 automatically. It was also stated by Suma a while back if I remember correctly.

[Radic]

:-) That occurred to me last night - so I'll progressively try lower values.

[Max Power]

No, you'd be surprised how little useful info a search yielded - that's why I posted.

Okaaay... maybe the search function is different when I use it.

http://www.flashpoint1985.com/cgi-bin....71dd2f3

The ninth or tenth return of the query "HDR disable" set to 'this month and older' in the threads 'ArmA: General and ArmA: Troubleshooting' gives you a thread where Maruk answers your question succinctly and eloquently on the first page. This is the first return in that query that is a good match to the question you asked and would have taken you 30 seconds from the time you made the query to actually reading Maruk's post.

In fact, using the search engine is so easy that I made this query for information that I already knew just to verify your claim. It took 1/10th the time I took to write this post.

You're either unfamiliar with how the search actually works or you're lazy and a liar. I suspect the former. Read the entire search form once and understand what each of the options means. This will take you at most 2 minutes and will allow you to make queries that give you accurate returns.

Quote[/b] ]
:-) That occurred to me last night - so I'll progressively try lower values.

That number is HDR precision, not amount. Lower values will just solicit erratic behaviour if it doesn't automatically revert them back to 8 bit by default. Higher precision values will give you cleaner and more crisp transitions, less glare, etc. Try setting the values to 16 and see if you like that effect.

[bravo 6]

maybe this can help you:

Isnt there a way to lock these values? The constantly changing brightness hurts my eyes after a while

You can do it but it's really part of the mission design:

Maruk: It's up to the maker of the mission to decide if HDR effects are to be disabled and what aperture to be used. Of course, this static aperture setting will not work well after lighting conditions changed too much. (source: http://tinyurl.com/2dqg3c)

If i can make this work properly i will use this from now on in my future missions. I also hate the constant changes.
Its bad for your eye health!




EDIT:
I tryed this information and i think the information given is kinda vague.
I used the command "setAperture Number", in a trigger.

The values used were: Number = {-1, 0, 1, 2, ..., 10}.

To me all these values sucked. The most appreciated for me was number 10, but its when you start a mission at 600am, because when the clock hits 1000am you will Not be able to see a thing but extreme bright light.
So i kinda disagree with Maruk on that statement, Its not up to mission makers to solve this problem, unless the mission meant to last 2 hours max. Otherwise everything will be ruined by the extreme bright light.
ARMA loses a point for this boring HDR problem.