Jump to content

89-

Founders [standard]
  • Content Count

    145
  • Joined

  • Last visited

Community Reputation

26 Excellent

About 89-

  • Rank
    Founder

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

457 profile views
  1. In my case flickering mostly happens in the beginning of gaming sessions, so definitely not overheating related. Other than this occasional flickering, the HMD works perfectly well.
  2. Thanks for the review, high FOV does sound cool. The sense of speed must be much better, I really do look forward to my first high FOV hmd. For balance: Pimax vs RiftS https://forums.eagle.ru/showpost.php?p=3926163&postcount=940 Pimax vs Reverb https://forums.eagle.ru/showpost.php?p=3953366&postcount=1784
  3. We've got 2 year warrnaty in the EU, so I'm sticking with my Reverb as flickering is minor gripe and does not happen often. Nothing to replace it - RiftS is good, but not Reverb good. Pimax they say is equal to RiftS in the sweet spot and wide FOV is secondary to clarity and definition for me.
  4. I also have occasional flickering, usually (if at all) when I turn it on for the first time in a while, I thought its powerful screens were warming up or something 😄 Flickering stops after 3-5 seconds and doesn't tend to come on afterwards.
  5. Sorry to hear that it was the hardware fault after all. No disconecting issues with mine so far, even though I 've spent a few hours in "active" raoom scale games. Still, considering doing this simple mod now to relieve the cable strain from the plug:
  6. 1903 update is notorious in WMR VR circles, just google "1903 WMR VR problems" Just some examples: https://forums.eagle.ru/showthread.php?t=236149&page=131 https://www.reddit.com/r/WindowsMR/comments/buiymg/win10_1903_odyssey_error_check_your_display_cable/ https://www.reddit.com/r/WindowsMR/comments/bs7cp4/odyssey_build_1903_bug/ https://forums.eagle.ru/showpost.php?p=3946088&postcount=1521 And the worst one - dramatic drop in VR sharpness for all high res WMR headsets, with no fix after months of waiting: https://steamcommunity.com/app/719950/discussions/0/1651045226218511368?l=english&ctp=1 Moreover, for some people even rolling back from the 1903 still gives the same problems... My windows update settings are set to maximum deferral, and no issues with the Reverb on 1809. I'd say your reverb is fine, but you need to *properly* (whatever it means here - not sure myself) roll back away from 1903. It sucks, I know PS Oh yeah, I see 0 difference in 3d image stereo presentation between CV1 and Reverb. Seems like some forced meme floating around the internet 😄
  7. Yep, we are talking about the same thing I think. Basically it looks like we have some faint semitransparent dirt on our glasses that moves with our viewpoint, unlike screendoor that stays fixed independent of our viewpoint. Explained here for example: https://www.roadtovr.com/whats-the-difference-between-screen-door-effect-sde-mura-aliasing-vr-headset/ and here for PSVR https://www.reddit.com/r/PSVR/comments/8jy8fc/persistent_mura_effect/ I personally never noticed this effect in CV1 or RiftS, but you say you had it with Odyssey? In reverb it is pretty apparent - the sky, or the winter Stalingrad make want to clean the glasses I agree that it is not a deal breaker, and nowhere near as bad as the screendoor on past gen HMDs, but Reverb would be better without it still.
  8. Sorry, you said that So do you have this? : It's not a very strong effect, but it is there for me and I'm wondering if it's a general problem with the Reverbs...
  9. I meant mura of course, sorry. Moire is is also an optical side-effect, but thankfully not present in VR. My PC is identical to yours, and my conclusions are also very similar, bar a few bits like the audio. Audio is definitely worse than CV1 for me, but a step up from RiftS. But, overall I completely agree that Reverb's performance is unexpectedly good and its sharpness being excellent when compeared to RiftCV1 and RiftS. One other little niggle is a occasional flickering in one of the screens for about 10 seconds after starting WMR and going straight to game. Do you have that too?
  10. Thank you for the detailed review! Do you see any moire in your set? In my reverb I do, looks like a pattern of dust covering quite a bit of the view. It is particularly noticable when looking at light areas like the sky. The moire pattern moves together with your head, exactly like some faint dirt on your glasses would. Do you have that at all?
  11. Also spent 2 hours battling this, and did not see this page either -until now :) The other solution that worked for me is deleting collision_bounds stuff in Steam/config/chaperone_info.vrchap Looks like this now : { "collision_bounds" : [ [ ], [ ], [ ], [ ] ], credit https://steamcommunity.com/app/250820/discussions/0/1741101364297725743/ I wish Valve pulled their finger out and gave us a normal option tick box to disable the flaming thing!
  12. Could you possibly run this clarity test? https://forum.il2sturmovik.com/topic/35634-application-to-test-text-clarity-in-vr-hmds/
  13. I understand that IL2 had (has?) some native issues with WMR VR sets like the Samsung Odyssey, Dell Visor, Lenovo Explorer etc. Just wanted to make a thread that would keep track of updates in this regard. Is WMR still unplayable in IL2 or has there been a IPD mod that solved this? If yes, how satisfactory is the solution? How is the performance compared to Oculus/Vive?
  14. We are forgetting that with Jason becoming at the helm of the franchaise things have not had a lot of time to change. Previous direction I would agree with the topic starter was plain wrong with the said abscennce of training missions, generic campaign with action points, nothing being done to ROF mission editor complexity. THings will change a good amount for BoK and will change drastically for the Pacific where new engine will mean scraping old shortcomings from the get go.
×
×
  • Create New...