跳转到帖子

JayRoc

Members
  • 帖子数

    221
  • 注册日期

  • 上次访问

最新回复 发布由 JayRoc

  1. 1 hour ago, Dunx said:

    I'm using vrperfkit with my Reverb G2. Fholger's github page did say Oculus and OpenVR so I tested anyway.

    The normal features appear to work well (fsr, nis, cas (new), sharpen, radius, etc.) however, I didn't see much difference with the fixed foveated enabled or disabled on my 3090. More testing tonight.

     

    Please read what peole write:

    From his Github
     

    Quote

    Planned mods:

    • "Fixed foveated" rendering (render fewer pixels at the edges of the screen)
      • Radial Density Masking (all GPUs, but works only with a handful of games)
    • Force hidden area mask: don't render pixels at the edges that are not visible in the headset. Many games already use this mask, but not all. This mod will allow you to force its usage.

     

  2. Dont get me wrong. What Leap Motion does is awesome...but aslong as i am way faster with looking at it and clicking my mouse i dont see a point in using it.
    The Leap Motion Demo works also way better than the DCS integration. It will get there and it will be good. But its not there yet - its a nice gimic atm. imho.

  3. I have to report that this error occurs again.

    When i join the Blueflag 80ies Server and go to F10 the Problem occurs instantly and repeatedly.
    Will do some more testing when it occurs...but havent had this problem since November. And with one older AMD driver.

     

    EDIT: Its specific to the Blueflag 80ies Syria Server and occurs as soon as you zoom in and out.

    image.png

    Win11 - DCS 2.7.9.18080 - AMD 22.1.1 Driver on RX6800XT

    • Like 1
  4. Yeah thats way past my budget, aswell. But give it a couple of years and it might be in Consumer range.

    My brother just got the Leap Motion thing because booth of us were excited about it.
    But its pretty much work in progress and due to positioning the device has a hard time tracking you hand properly when you reach to mfd´s.
    The whole tracking is lagging a little bit. 
    My guess is that the Ultra Motion 170 is way better suited...but its also a bit pricey.

    I had the same idea as you do. But i switch airframes a lot, so a small fake cockpit wouldnt suit me.

  5. If you want to get rid of the jitters on the AMD...go to

    SteamLibrary\steamapps\common\MixedRealityVRDriver\bin\win64OpenVRSettingsUX.exe

    image.png

    And turn on the Reprojection in Steam.

    There are a lot of people saying its the same settings and it would make no difference...but they obviously never tried it and have no clue what they´re talking about.

    • Like 1
    • Thanks 1
  6. There are several reasons not to:

    -No official SteamVR support
    -Possible driver problems
    -Recent MS updates with resulting blue screens and bricked OS

    The new Startmenu is "unfortunate" and they furthermore seperated OS settings to different places.

  7. 8 hours ago, speed-of-heat said:

    has anyone tried up sampling directly in the MOD rather than in SS e.g. render scale of 1.2 or whatever 

    using 1.2 in FSR and 65 or 75 in SteamVR SS - you get problems with the clouds...but some kind of antialiasing.
    With higher SteamVR SS the performance hit is too high for me.

    FSR@0.83, SteamVR SS 100% and for game 84% with ReShade gives me good results for multiplayer.

  8. Steam SS 100%
    Steam per App SS 100%

        "enabled": true,
        "renderScale": 0.68,
        "sharpness": 0.9,
        "radius": 0.75,
        "applyMIPBias": true,
        "debugMode": false

    AMD FSR without ReShade

    image.png

    Nvidia NIS without Reshade

    image.png

    The instruments look more crisp with Nvidia NIS but the distant, clouds and flimmering/genral qualitiy looks better to me in FSR.
    AMD FSR seems to be slightly faster on AMD RX6800XT, but its so marginal that my decision would base on the quality you get for your setup

  9. I use AMD FSR as my antialaising which works pretty well in DCS, together with ReShade i get a crisp image.

    Steam SS 100%
    Steam per App SS 65%

        "enabled": true,
        "renderScale": 1.18,
        "sharpness": 0.9,
        "radius": 0.75,
        "applyMIPBias": true,
        "debugMode": false

    Here is FSR vs NIS for this case. But the antialaising works better with AMD FSR - means with this settings FSR looks better for me.

    AMD FSR with Reshade 12.8ms

    image.png

    AMD FSR without ReShade 12.2ms

    image.png

    Nvidia NIS with Reshade 13.0ms

    image.png

    Nvidia NIS without ReShade 12.5ms

    image.png

    Testet with 21.40 beta driver. I feel like the sideways head movement works more fluent with FSR? But might be me.

×
×
  • 创建新的...