Severe screen burn-in on VX3211?

NewHome Forums OSSC & OSSC Pro OSSC – Discussion and support Severe screen burn-in on VX3211?

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #22239
    bluescrn
    Participant

    I bought a Viewsonic VX3211 (32″, 1080p) a little while ago for retro gaming, as it was a model recommended for use with the OSSC, and not too pricey. Seemed great at first, although I’ve not had time to play much on it.

    This weekend, I hooked up a PS2 to it, and was feeding an interlaced signal through the OSSC via RGB, as I preferred the pixelly bob deinterlace from the OSSC to the screen’s native blurry upscaling (and haven’t had much success with force-480p hacks)

    Everything seemed OK (except for the OSSC ocassionally dropping the signal and going black for a couple of seconds), I tried a few games, played a bit of Gradius V, and then without thinking about it, I left it paused and came back maybe 3-4hrs later… to find that I’d got a severe and very odd form of screen burn-in – I could see the bright parts of the image seemed burned in (pause menu text, starfield).

    Thought it might be an OSSC glitch, so tried a different video source and the burn-in was still there 🙁

    It looks like this: https://imgur.com/a/Jp7GbiR – you can clearly see the Gradius V pause menu and power-up bar. And of course the starfield (no, that’s not flickery noise, it’s a burned in starfield?!)

    WTF? – I’ve never heard about burn-in of that sort of severity happening in just a couple of hours on a modern monitor?

    Tried turning the monitor off for a few minutes and it’s not gone away. It’s a bit strange, it’s not like the pixels are stuck, as it’s not visible against a black output. And the really wierd thing is it’s still got an interlace-like flicker to it even on top of a clean 1080p signal…

    Has anyone seen anything like this before? – I’ve never seen anything like this on an LCD. And I guess as a warning to others with this screen… maybe it just has a real problem with burn-in – so don’t leave it showing a high-contrast static image, or maybe it really didn’t like the OSSC output in that particular mode?

    Guess I’ll have to see if it fades at all with time. But as this one may be dead already, has anyone got any better recommendations for a 32″ low-lag OSSC-friendly monitor or TV?…

    (edit: Looks like it’s fading away after running the screen with a different non-static input for a while. After half an hour, it’s way better than it was)

    (edit 2: And after a couple of hours, panic over, it seems to be entirely gone!)

    #22248
    ErebusMaligan
    Participant

    The Bob-deinterlace seems to cause this on certain types of panels. It has a similar (thought not as severe) effect on my monitors, especially with text. I left my PS2 on at the launch menu at one point and that got burned in for a couple of hours.

    #22253
    Galdelico
    Participant

    Once again – apologies to sound like a broken disc 😀 – it’s not really fault of the OSSC’s bob deinterlace per se, and it doesn’t randomly happen with ‘certain types of panels’.
    This is a known issue, at this point, and it’s quite surprising to me how this piece of information – as empirical and ever evolving as it gets – is still buried in several threads on various forums (SHMUPS, here at VGP too…), instead of being brought up and stuck on top of dedicated boards, to everyone’s attention.

    Basically, to this very day, it’s been proven how IPS displays – from many manifacturers, such as LG, HP and ViewSonic – are more or less sensitive to severe screen flicker (which is that constant shimmering effect you get on screen, when you display interlaced sources, like your PS2 480i games), which produces the temporary burn-in/after-flicker mask you experienced and pictured. Not enough tests have been made on VA panels, in order to realistically establish how they behave, while TN monitors appear to be immune to all that.

    Also, it may have made it a bit worse, but the fact you paused the game most likely didn’t make a huge difference: I personally observed the same result – on an LG 4K monitor – after playing Virtua Fighter 2 on my SEGA Saturn for about 10 minutes, with no pauses. Some PS2 games (Ridge Racer V) marked the screen after an even shorter time.

    #22257
    BuckoA51
    Keymaster

    This is a known issue, at this point, and it’s quite surprising to me how this piece of information – as empirical and ever evolving as it gets – is still buried in several threads on various forums (SHMUPS, here at VGP too…), instead of being brought up and stuck on top of dedicated boards, to everyone’s attention.

    The issue is mentioned multiple times in the quickstart guide and on the wiki.

    #22258
    Galdelico
    Participant

    The issue is mentioned multiple times in the quickstart guide and on the wiki.

    Yeah, that’s true, but take a look at this (from the Wiki):

    Beware of using the OSSCs Line2x (bob) or Line4x (bob) deinterlacing modes on sources that display static graphics or text for a long period of time. The OSSCs deinterlacer produces a constant flickering effect. This can cause image retention/burn in to occur faster than normal.

    It doesn’t mention it happens on IPS panels, for instance: now, I’m not aware of extensive tests done with VA displays, but TN monitors appear to be pretty much immune to the whole issue. It’s not as universal as it reads.

    Also, that note makes it sound like the OSSC is doing something odd – or incorrect – whereas the temporary ‘after-flicker’ effect can be easiliy replicated on entirely different machines (such as the New Nintendo 3DS XL consoles that come with IPS screens): the amount of flicker I get by using the OSSC’s bob deinterlace (in Line 2x with scanlines) isn’t really different from what I can see by plugging my 480i sources directly into a CRT TV. If anything, the OSSC provides a cleaner and more stable picture.

    I don’t mean to sound like I’m complaining – I got my OSSC 1.4 I believe during the second production wave, and I’m a HUGE fan ever since 😀 – I just believe this specific issue isn’t really explained as it should be, leading several people to stumble upon it kinda cluelessly, or to leave thinking your device is somehow at fault, when it’s not really the case.

    #22272
    ErebusMaligan
    Participant

    it doesn’t randomly happen with ‘certain types of panels’.

    Nowhere did I say random. Nor did I say only the OSSC could ever cause this.

    it’s been proven how IPS displays

    Are these not certain types of panels? I’m incredibly confused as to why you took issue with saying certain types of panels. I couldn’t remember the specific type of panel, but I remembered seeing a previous post where someone (likely you, since it also mentioned 3DS XL screens) explained this.

    It doesn’t change the fact that using bob-deinterlace (such as this function used by the OSSC) on certain types of panels (IPS ones perhaps) can cause this unfortunate issue. I’m not sure anyone is claiming the OSSC does something wrong, just that people aren’t understanding why this happens or aren’t aware that it will.

    As far as awareness, I’m not really sure anything will really solve that. People still regularly install the non-audio firmware and then ask why there is no sound. Not everyone reads the wiki, and many people probably don’t follow the various forums religiously.

    #22281
    Galdelico
    Participant

    Dude, I didn’t mean to attack you specifically – sincere apologies if I sounded like I wanted to – and there’s absolutely no issue to be concerned about. It’s just my gritty, down-to-the-ground common sense, that very often leads me to point out how certain things are reported, vs. how they could be explained in much clearer ways. That’s all, really. ^_-

    #35234
    GillRios
    Participant

    Hi….there should be no burn in on an LCD as tigger said. This is just Asus’s shit quality. They went to shit when they started concentrating on making money from their “gamer” demographic and then it seems they forgot to make good stuff coz they know the gamers are going to change their hardware in 1 or 2 years time anyway. So who cares if their product dies at the end of 3years.

    seo toronto

    • This reply was modified 7 months, 1 week ago by GillRios.
    #35317
    Zod
    Participant

    I have that monitor it happened to me too but the burns go away after a while, you can accelerate the process by playing an RGB ‘cleaning’ video from a file or even YT.
    That issue wasn’t too common in the past but today it happens to all IPS panels all name brands, no exceptions it seems.

    On that monitor I don’t use the OSSC for playing sources that are interlaced at all times (like most PS2 library) and therefore require constant deinterlaced output, so I never meet the dreaded flickering for longer than a few seconds or minutes within games that have like interlaced ingame menu screens, or progressive but fast flickering items (e.g Progear title screen), none of these are a problem unless you leave these particular screens to display for too long.

    If one seeks a LCD that doesn’t have this temporary pixel marking/retention weakness, then it has to be a VA, ViewSonic don’t have a large one that would be identically as good and convenient as the VX3211-mh in 32″ size, they do have 27″ but all curved AFAIK, except the VG2739 which is rather old and lacks enough info to recommend. Maybe they have a good 24″ VA idk.
    (NB: rare cases of VAs marking to flicker have happened though, I think I’ve seen a couple of cases on rtings website, but that wasn’t much)

    Other brands I don’t really care about since for the OSSC I don’t believe there are any making monitors offering as much convenience, compatibility and quality for the original OSSC than those select ViewSonics (that mostly won’t matter later with the OSSC Pro but for now that’s the status)
    Maybe there are a couple VA models out there from other manufacturers that handle everything as well in the ViewSonic fashion, but that’s impossible to guess without users specifically trying them with an OSSC and reporting to the community.

Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.