Jump to content

zberry7

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by zberry7

  1. I also posted about this in another thread but the issue for me is much more noticeable than it is in those screenshots. For reference im running the Quest 2, resolution set to 1.4x in the Oculus App, 1.0 in DCS. I had both MSAA and conventional AA enabled when I was running 2.8, after reverting to 2.7 with no settings changed it was immediately noticeable. I didn’t play around with settings enough, because I actually wanted to be able to see the screens so I just reverted to stable. But for me, thin lines are totally eaten into by the black background, and the thicker lines look thin, everything is dull. I agree it looks like an anti-aliasing algorithm getting angry and just dulling everything, and since it fixes when zoomed in, it’s obviously resolution dependent. Maybe some changes to the rendering of the cockpit are the cause, just speculating of course, but it’s strange that this is only being reported in the A-10C II Normally, the details on the screens are already small and difficult to read because of the limitations of VR, but this just makes it so I can’t even make out larger details like my flight plan on the TAD, etc..
  2. Yes! I reverted back to stable because of it, and the difference is VERY noticeable. I’ve been looking around to see if a bug report was submitted, because I don’t have the time to myself. But I did back to back testing between 2.7 and 2.8 (identical settings) and in 2.8 the lines on the MFDs appear thinner, more jagged, blurry and hard to read. In 2.8 I couldn’t even make heads or tails of the TAD page. After reverting to stable, I could immediately notice a substantial difference, I no longer needed to zoom in to make out the TAD. For me, the MFDs were already difficult to read compared to other jets, this update made them unusable without zooming every time. It’s nearly game-breaking for me, which is why I reverted back to 2.7 If anyone else had any luck with solving the issue please let me know, I haven’t tried clearing caches or anything, I don’t really want to update to 2.8 until I know I can fix the issue.
×
×
  • Create New...