Jump to content

aceviper

Members
  • Posts

    713
  • Joined

  • Last visited

Posts posted by aceviper

  1. Hey Fisherman

    There are swap eyes.....mirror eyes...swap top and bottom projection....and reset values.

    For me I just mirrored left eye values.

    Slightly less blurred....maybe less crossed🤪..more relaxed.

    And not using any antialiasing.

    There is shimmer...but much much less when eyes are aligned properly.

    But much sharper near and far.

     

     

    • Thanks 1
  2. Just now, shadowborn said:

    Hey. OP here with some new findings, confirming some sort of memory leak it appears.

    HP shipped me the new cable. It looks JUST like the "old" cable that came with the Rev. B. headset, and also has the little "Rev. A" flag/sticker on it. But lo behold, it appears (pending further scientific testing) to resolve a lot of issues EXCEPT, sadly, for those with DCS 😞

    I don't own many VR titles. But the following worked flawlessly (apart from occasional view centering issues) now, and didn't before:

    - IL2 Sturmovik
    - Titanic VR Experience

    Currently still downloading Skyrim VR, which I just bought for more testing.

    HOWEVER DCS still crashes, and it is, as I suspected, seemingly a memory leak. Many times there is nothing at all in the event log, but one time I got this:

    Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: DCS.exe (9808) consumed 20684664832 bytes, dwm.exe (10372) consumed 1494360064 bytes, and vrcompositor.exe (3436) consumed 648605696 bytes.

    That's 20GB of RAM for dcs.exe, 15GB for dwm (Windows Display Manager), and negligible for vrcompositor.exe. My machine has 32GB, but this confirms to me that the Out-of-Memory killer mechanism is responsible for killing the various processes I observed being killed over the last days whenever DCS VR initializes.

    This is with DCS Open Beta 2.8.1.34667 and AH-64D. I have at times loaded successfully into the Viggen (twice), the KA-50 V3 (once) and the F-18 (once), but with various crashes in between. I will now keep trying with other aircraft to see if the new cable helps and maybe this is an AH-64 problem now.

    That dwm.exe is a known intel 630 memory leak.

    Certain version drivers are meant to fix that.

    Moved to win 11 recently and havent noticed it.

×
×
  • Create New...