Semi-permanent image burn-in O_O

[Mrmo]

The weird 1080i mode has, after 20 or so minutes of gameplay, left my monitor with a flickering, burned-in image of the health meter in the top left corner of the screen. I connected the monitor to a different PC and the flickering box with the word RAIDEN could still be somewhat clearly discerned.

It persisted through both restarting the PC and switching the monitor on and off, and appears to have faded after half an hour of LCD conditioning (rapidly switching every pixel color to uniform RGBCMYK) and keeping the monitor shut down for a while.

This is something I have NEVER ever encountered before, and I'm an avid gamer for 20+ years now. It literally scared me!

[C0unt_Zer0]

right, but why would it only crop up in this particular game? There has to be something about the settings that is causing this to happen, be it driver related or game related. Other people are having issues with this game not running at 60hz & I would bet that's what's causing the issue here, it would definitely explain the flickering.

edit: Thanks Mrmojinto, I'll mess around with it & see if we can get this solved. I forgot about the built-in conditioning & ran a seizure inducing youtube video on it instead lol

[Anika]

The only problem I have with this game is rare screen tearing (IPS monitor), but I fixed it by forcing adaptive vsync in nvidia panel options.

[C0unt_Zer0]

hmm, can you confirm it's running @ 60hz? it seems the nvidia users are able to force 60hz in the nvidia options, i'll try it in CCC when i get home (really want to finish this game..)

[Anika]

Yes, If you disable Vsync you will get 60 fps instead of 50 with enabled.

[Anika]

I think that I very lucky to run game at 60 fps(only drops in last chapter to 50-55) with all max on my old config. I've seen some people having problems with monsters like GTX 780(compared to my 560 xD)

[C0unt_Zer0]

So after messing with CCC (which is garbage & I miss nvidia's software) I couldn't find a configuration to solve this issue. After reading a bit more here I did find something that works. It's this little program someone else posted that enables borderless windowed mode. It will stop the flickering & in turn stop burn-in. Get it here: http://gc-modding.googlecode.com/files/WindowedBorderlessGaming_1.1.1.4.zip

originally posted ITT:http://steamcommunity.com/app/235460/discussions/0/630802344416412017/

So it seems my hunch was correct, When in fullscreen mode this game forces a weird refresh rate, causing the flickering & our IPS panels seem to not be too fond of it. The work-around is a little hacky, but at least I can finish the game without worrying about constantly seeing the state of raiden's health when I'm done playing lol. It does make some lines run through the menus but it doesn't seem to affect anything actually being rendered so it shouldn't drive you too crazy (& again, it's better than burn-in).

So This is an issue with the game itself & could be resolved with a patch.

[Anika]

Hmm.. strange, some people have big problems, some haven't any (like me). I think it's really depends on hardware.
But i'm glad to see that you fixed it. :)

[truehorror]

So I'm definitely not a person who knows a lot about resolutions etc. But I thought this game was 1080p? Is there a way for me to see easily whether the game is running on i or p, from what I remember reading you could actually see if its in 1080i.
It sucks that so many people are having problems with the game, I havent had pretty much any problems at all if I dont include the horrible mouse control on the accurate sword slicing mode when you press shift.

[Anika]

My game is running at 1080p (progressive, PC monitor)
1080i (interlaced) have halfed refresh rate and pixels onscreen, standart created specialy for tv signal broadcasting and yeah you can see the difference: http://www.brorsoft.com/images/how-to/video-converter/1080i-vs-1080p.gif

[Hor1]

Same problem, same monitor (Dell U2312HM), so it seems to be a monitor problem.

[Mrmo]

Alright, three monitors can't be a coincidence ;/

[Hor1]

if anyone finds out a foolproof solution feel free to share. :)
I'd like to play it, but not at any cost.

The strange thing is, yesterday I played for an hour and a half, no problem at all, today approx. half an hour - burn is.
Strange

[Tigeron Starfire]

Seems like this is IPS monitor related! I had the same thing happen after playing on my 27" LG - Model #27EA63. I'm doing the website pixel conditioner now, and it is helping. The flickering is much less noticeable, if not gone after letting it work for about half an hour. Still, it's weird - I've never had this happen before.

I had it in fullscreen and I was playing for about two hours. The burn in appeared right after I stopped. Neither turning off the monitor nor restarting would quickly fix the issue, although I wouldn't see it so much on black or white pixels. However, it was really obvious on top of the blue sky on my desktop wallpaper.

The game itself is pretty fun, I just worry about continuing to play it with the health bar burn in, as a lot of you have seen already. XD

[C0unt_Zer0]

the best solution i've found yet is posted above, that program is tiny, no install is required & it adds no more than 3 extra clicks to launching the game. It displays properly that way. IPS panels apparently don't like running at whatever refresh rate fullscreen mode is locked into. The game is running at less than 60hz in fullscreen, but does run at 60hz in borderless windowed mode without any performance hit.

[Baron von Whimsy]

I just use Game Companion, allows fake fullscreen of any application, whilst avoiding the application having to switch itself to a fullscreen mode. It requires no clicks at all, beyond telling it which executables to act upon.
http://www.nexusmods.com/newvegas/mods/42956/?

The refresh rate is only on fullscreen 1920 x 1080, and seems pretty damaging to any monitor. And your eyes, 25Hz was not pretty to look at.


I like how there's talk of how "CCC is laaaaame".
I doubt you guys have ever used Nvidia's Optimus BS, but let me just say, CCC is the lesser of two evils.
You have one basic issue with CCC, and it's resolved with a couple of minutes work (Overscanning, on different refresh rates).

Nvidia's offering is an issue everytime you want to add a program that it "thinks" it has already profiled.
Sometimes it really has, but just can't understand why you didn't install to the default location, and so just assumes that's not the program you were referring to. (seriously.)
And you can't just change the location, because it just opens the previous profile, so you end up using a tool to add a profile (which you can't expect a novice to do), or you have to add a function into your program to check if your program already has a profile, and if not, to make one and restart the application, and all because godforbid that s&$* actually having a working system that actually does what it's supposed to; elevate actual graphically intensive programs to the discrete GPU automatically.

And god help you if your application has a generic name.
"Client.exe" or "Game.exe" are the bane of my existance.


So yeah, I miss CCC's generic, attitudeless approach to handling my graphical profiling when I'm using my laptop.

How's that greener grass looking now?