skeemo

Hey, well i tried that and now i am really confused. Because some thoughts and feelings came up, that i had for the very first time when i saw the white boxes. Ok. Here's how it goes: First, Nates HDR preset mod indeed did change some for me. That is on the one hand a reduction of the white box issue. Yes reduction, i still have the issue, but it seems like it does not happen so often as before. But on the other hand, the issue remains active. I flew the FreeFlight AirStart Mission, which puts you in Kutasi general area. so lots of buildings. Second, and that is the confusing and interesting part: In some white box appearances the complete screen is like doing a bright "flash". It seems like something is blinding you very short. Just like you experience in reality when you drive with your car on a sunny day and a window just reflects sun straight into your eyes for a few moments. This is what i first thought, when i saw those boxes with 1.1.0.7 but no one ever verified that feature. Reflecting surfaces blinding you for just a moment. With Nates hdr.fx it really looks like this. And i have to say this time, it looked really cool - despite the white square. So what you guys think ?

Well it indeed is true, that the issue wasnt there pre patch 1.1.0.7 Anyway, that does not mean that only ED does something "wrong" here. ED maybe just started using a DX effect / command that they didnt used before that version. And then it might be indeed a Card / Driver related issue, which would be very sad, as the 69xx card are very good for the money. And although i instantly started thinking about buying a nvidia card (lol) i am not gonna change my system just for that... So i hope ED and AMD do communicate which each other here. I dont think it will be AMD's business to loose every flightsim enthusiast to nvidia. At least i hope..

Problem introduced with patch 0.7. So ED changed something, which truly might be a problem to ATI cards.

:( really ? that's silly ! I didnt played A10 since the bug arosed...thats bad news. It completly ruins the overall experience for me, as i am a guy who wants to use a feature (HDR) when its available. And so are most ppl here i think.

Hopefully 1.08 adresses / solves this issue. I didnt saw anything in the pre-Changelog..

Sorry dont know.. But two little (offtopic) hints: 1) Its not easy to find out what you are looking for, so better put that in the thread's title .. 2) There already is a COD thread, so better post there. You will reach more people that may help you.

for completing purposes : 6950 here :)

For the guys, where the game does not load: Make sure, you dont use windows' notepad, as it will mess up the lua files. Use Notepad++ !

@Nate, as per page 6 last post, a nvidia user had the same issue. Anyway, i started a topic in the AMD Game Forum, i found a existing Warthog thread over there, discussing XFire caps of Warthog.. @YoYo, lol, no...i just painted a white square in windows paint ;). But it looks pretty much like the real thing, doesn't it ? :)

No, that looks completley different. And as it related to the HDR setting, i dont see a connection to building LOD's YoYo posted a video of it on page 1. You can see it best at around 0:40. I quickly painted a square in the picture above, it looks just much like that.

It is a good one yes. But it lacks of the ability to represent combinations of multiple modifiers e.g. "RSHFT+RCTRL+H". That is "Gain Googles up", which is a default key command...

Ok i tried again some different ingame settings. MSAA off TSAA off HDR on Driver Settings: AA : Use App settings, Filter:Standard AF : Use App Settings Tesselation: AMD opt. CatAI: High Quality, Enable SFO unticked AA Mode: Performance Issue can still be seen. I created a mission where you start in the air over crowed city area. I let the game in pause mode and panned around in external view. As i noticed some of the white boxes i stopped panning and just let the game running in paused for a few minutes. I made a screenshot of the view and marked the areas where i had a lot of the anomalies. I tried to catch one with a shot, which is impossible ;) I tried that with different settings, and it remained the same. New Mission.miz

Turned MSAA off in game. Driver defaults to "Application settings". HDR on TSAA on Issue still there. I want to note that it happens the more the lower you fly over the buildings. Above a certain altitude it might be completely gone. Could be connected to objects LOD distances.

Just a little update, as i reinstalled a vanilla 1.1.0.7, just to sort out any errors during update. Error is still there.

This was the first thing i was thinking about when i started to read your thread, that you need a driver. And that cannot be achieved without signing it in Win7, especially x64. So there is testmode. This is the point where you cannot address all users. I twiddled around with PPJoy several times, and yes it is working in test mode, but i dont have a good feeling using it that way. And it isn't a plug-and-play stuff anyway.

Ah ! That is something that gives me hope as it then isn't a ATI only issue 

Anything new here ?

No. I have it on, left at default settings.

Interesting ! As I suffer from the white flashes bug I will invest some time in testing that too.

If you look into the default profile XML there is an Catalyst AI entry. It is set to "enabled" regardless of the settings in the ccc. So it isn't really off.

Update: ok i played around with disabling the catalyst AI which is not so easy in newer CCC versions. I tried it with editing the CCC's profiles XML. I tried it with RadeonPro and setting the AI setting to global off. The problem is still there. On the other hand you never know if your 3D driver settings really are applied and there is no possibility to check that.

Interesting. Look what i found here : http://forums.guru3d.com/showpost.php?p=3899903&postcount=18

Same here :) Also i am ready for testing any new DCS planes ;)

more info also here : http://forums.eagle.ru/showthread.php?t=71368 from post #8 downward

mhm, they are great cards for the money ! Anyway let's summarise again what we know (Hello Nate :) ) - Could be a AMD 6xxx cars issue (please don't) - Tested with Driver 11.2 - still there - HDR off = issue gone - Tested older hdr.fx - still there - Could be already there before patch 1.1.0.7