3 ms·

I remember reading that the Galaxy phones have trouble with pixel refresh rates. In that blacks can ghost because the nature of amoled.

sp332 10y ago
The Rift and Vive also use AMOLED screens, so I don't think it's the pixel tech that's the issue. LEDs can turn on and off extremely fast. It's probably that the screen's electronics were made for power-sipping mobile devices running at most 60 FPS and not 90+ FPS gaming.
- cma 10y ago
  OLED is the issue. Look into the black smear problem on Oculus DK2 and how they had to half-way fix it by overdriving for a frame and then falling back. CV1 of the Rift headset is OLED and has the same issue. They have to run the panels at a notch above minimum brightness to work around it and as a result they lose out on true blacks. https://vrwiki.wikispaces.com/Black+smearing https://vrwiki.wikispaces.com/Black+smearing
  - sp332 10y ago
    None of those threads mention the Rift CV1, the Vive, or the Samsung Galaxy S6 or S7 (the ones that fit in the current Gear VR headsets). I tried the test image from this thread http://forum.xda-developers.com/showthread.php?t=2765793 http://forum.xda-developers.com/showthread.php?t=2765793 on my S6 and didn't see the issue. That thread and this one https://forums.oculus.com/community/discussion/10924/true-black-smearing-in-dk2 https://forums.oculus.com/community/discussion/10924/true-bl... say it's only an issue around areas where the screen is actually black, so keeping things very dark would seem to be worse?
    - cma 10y ago
      I think I wasn't clear. It isn't a notch above minimum brightness as in running the panel very dim. It is a notch above minimum as in: minimum is pure black, and instead of every allowing pure black they set it to one notch higher, because pure black causes the smearing. It isn't an visible issue in Rift CV1 or Vive because they do that as a workaround.
thescriptkiddie 10y ago
http://doc-ok.org/?p=1082 http://doc-ok.org/?p=1082

sp332 10y ago

The Rift and Vive also use AMOLED screens, so I don't think it's the pixel tech that's the issue. LEDs can turn on and off extremely fast. It's probably that the screen's electronics were made for power-sipping mobile devices running at most 60 FPS and not 90+ FPS gaming.

cma 10y ago
OLED is the issue. Look into the black smear problem on Oculus DK2 and how they had to half-way fix it by overdriving for a frame and then falling back. CV1 of the Rift headset is OLED and has the same issue. They have to run the panels at a notch above minimum brightness to work around it and as a result they lose out on true blacks. https://vrwiki.wikispaces.com/Black+smearing https://vrwiki.wikispaces.com/Black+smearing
- sp332 10y ago
  None of those threads mention the Rift CV1, the Vive, or the Samsung Galaxy S6 or S7 (the ones that fit in the current Gear VR headsets). I tried the test image from this thread http://forum.xda-developers.com/showthread.php?t=2765793 http://forum.xda-developers.com/showthread.php?t=2765793 on my S6 and didn't see the issue. That thread and this one https://forums.oculus.com/community/discussion/10924/true-black-smearing-in-dk2 https://forums.oculus.com/community/discussion/10924/true-bl... say it's only an issue around areas where the screen is actually black, so keeping things very dark would seem to be worse?
  - cma 10y ago
    I think I wasn't clear. It isn't a notch above minimum brightness as in running the panel very dim. It is a notch above minimum as in: minimum is pure black, and instead of every allowing pure black they set it to one notch higher, because pure black causes the smearing. It isn't an visible issue in Rift CV1 or Vive because they do that as a workaround.

thescriptkiddie 10y ago

http://doc-ok.org/?p=1082 http://doc-ok.org/?p=1082