Jump to content

edmuss

Members
 View Profile  See their activity

  • Posts

    1740

  • Joined

  • Last visited

 Content Type 

Everything posted by edmuss

  1. edmuss
    Assuming that you don't use it for anything else then yes. I also run dirt rally 2 and Ellie dangerous via open composite and as neither of those are every likely to gain native openxr support I'll be keeping it. Worthwhile making sure you have the native setup all running happily before you delete it.
  2. edmuss
    Unless you have an Aero and still wish to use OXRTK. Ah yes, that bit sucks To be fair I've yet to get toolkit working reliably yet, as soon as I apply upscaling it falls over on mission load. Only spent 20 minutes or so looking into it though and it was 1am so I'll probably get better results with a fresher head!
  3. edmuss
    I think that's mostly personal preference, it doesn't impact performance so you can set it to what you want. You can just ignore open composite for the purposes of DCS now, if you still have it present on your system and you start up DCS in steamvr mode (openvr) then it will still translate it to openxr unless you set it otherwise in the open composite switcher.
  4. edmuss
    The oxrtk resolution overrides all other resolutions, they're not cumulative so you're running 75% resolution which would be about 2700 I would guess. Running 105% resolution with 75% NIS upscaling is my current setup which results in 10-15ms frametimes.
  5. edmuss
    You could unlock the reprojection and it should stick to 45fps with theoretically less artifacts. We're going off topic here though
  6. edmuss
    Locking the reprojection to 30Hz means that you have up to around 28ms GPU frametime to play with but suffer the artifacts and blurring. Short of view distance, 4x MSAA and the SSxx options I run the same and get 10-15ms which keeps me fairly comfortably above 60Hz. Regarding switching 60 to 90, I can do either instantly but then I've been using WMR at 60Hz for a couple of years now. It's largely situational as to whether you see them, helo rotors and prop disks can be bad. If you're in a static airframe and high up you'll likely see less artifacting.
  7. edmuss
    GPU bound is what you want really, tune your settings to keep it around 13-14ms or better (75-70ish fps, that should give you a nice buffer before you hit the 16.6ms refresh rate and then it will get less smooth. You may find that in a couple of days you simply can't see the flicker unless you switch back and forth from 90 to 60, tweaking the other post processing options in openxr toolkit may give some more flicker relief.
  8. edmuss
    Welcome to above refresh rate VR, this is what it's meant to be like, reprojection is horrific once you've flown above refresh rate! I haven't been going on about 60Hz for ages for my health you know
  9. edmuss
    So looking 3-9 out of the cockpit and it's not a slideshow with <60fps @60hz? That's properly weird, it looks dreadful for me - how personal perception changes things! Presume nvcpl vsync is default?
  10. edmuss
    The beauty of 60hz is that it's relatively easy (with decent hardware) to get above refresh rate in DCS and because it's all synced up there is zero stutter from the VR compositor, of course if you have other I/O issues that can cause stutter. That's mental Is this high level or down low? I'm generally below 100m so the relative differential speed of objects is quite high even if airspeed is low. What vsync settings do you use?
  11. edmuss
    I don't think that he's WMR specifically, more the openxr side of things (which in some way will be intrinsically linked no doubt). Good to hear that he's still able to do what he does
  12. edmuss
    Some people can't stand it at all some can, the flicker has never affected me; noticeable but never the cause of any discomfort. I have only ever used 60hz displays though so it might be that I've not ruined myself with high refresh rate monitors Brighter displays show the flicker up more so the sunglasses filter in openxr toolkit post processing can help take the edge off.
  13. edmuss
    See the instant I drop below 60 it's stutter city for me on 60hz, where as on 90hz it's nowhere near as bad. 90hz at 55fps locked seems to be a weird sweetspot that works nicely - just that touch smoother than 45 or 89 it anything else in between. 55fps at 60hz is uncomfortable for me. I think perhaps my eyes compensate the 55fps easier or it's purely placebo but I'm not the only person to witness it. Not at 60hz, it will be perfectly smooth and image clarity without reprojection is a fair bit better. That's if you can handle the refresh rate flicker although there are things you can do to alleviate it. It may be possible to force yourself to get used to it, @speed-of-heatmanaged it as less than 12 months ago he couldn't run 60hz.
  14. edmuss
    The only caveat I find to 60Hz is that if you miss the 60fps vsync then it gets very stuttery, far more than you see on 90Hz. I can pull 95-65 fps reliably*, I'm very rarely CPU bound and the smoothness of refresh rate is just so much better - on testing 55fps locked I was finding I was getting tired eyes very quickly although for short term this was ok. *Running 3300 wide resolution override with NIS@75%.
  15. edmuss
    Ignore the HP instructions to route it outside, over the top of the left hand frame, every time you pivot the hinge it kinks the cable. I run mine inside and below the left frame the radius it bends to is much less ; the solution by @-Dagger- is nice as well as it isolates the movement of the cable. Check the plug is fully seated into its socket, there is a little indented spot on the top face of the plug, this should be conincident with the casing, if it's no then the plug isn't fully home.
  16. edmuss
    That's odd, everyone else seems to have largely the opposite result in DCS. For productivity tasks where you need high clock speed and core count then yes but for DCS (and MSFS) currently it's about as good as you can get
  17. edmuss
    Yes, I think that will just leave the mouse cursor slaved to the centre of your vision with a cross, I don't think it will hide itself. You can still bind mouse controls to hotas
  18. edmuss
    Undervolted on both, -27mv on the CPU and 975mv on the GPU running at 2040Mhz clock. Unrealistic CPU loads like prime95 small FFTs smash it straight up to 90°C but it's still stable and there is no normal usage that will cause such a load; on the other sections of prime95 testing the CPU sits at about 60-65°C. A 10 minute cinebenchR23 run gets it up to around 72-75°C with no thermal throttling.
  19. edmuss
    Not moving to centre but I used to use joy2key for moving the mouse with the warthog slew stick (along with a modifier key binding) but I could only bind it as a fixed speed digital motion. I now use joystick gremlin which has more utility and allows proportional speed of the cursor as well as using modifiers from another device (which I couldn't get to work in joy2key). I have warthog pinky paddle as a general modifier key bound in DCS, in joystick gremlin I have the slew stick bound to mouse movement with the pinky paddle being the conditional activator for it. In DCS UI layer I bind pinky paddle + CMS hat to mouse button functions (left/right & mwheel up/down). This way, whilst still HOTAS, I can move the mouse cursor independantly of my head if required to reposition it or leave it slaved and activate all controls. Additionally I can manipulate the F10 map and menus using the slew stick which is impossible with the headset slaved cursor. The only caveat of the above setting is that you need to bind pinky paddle + slew stick to a couple of redundant view axis bindings otherwise when you move the mouse cursor it slews your TGP etc
  20. edmuss
    My CPU is air cooled sucking cool air downwards and exhausting onto the backplate of the GPU, my GPU is air cooled and vents hot air out of the side and radiates off the backplate up to the CPU. I don't have a case, it's just a motherboard tray and rear panel screwed to the wall, completely open to ambient. In DCS the 5800x3D sits at around 65-70°C and the GPU sits at 55-65°C with an ambient of around 24-28°C. On 100% load testing the CPU hits 75°C and the GPU hits around 80°C.
  21. edmuss
    I've also seen a reduction in CPU and GPU frametimes from disabling the canopy shadows, getting on to 1ms on both which can help quite a bit!
  22. edmuss
    Not quite, find the clock speeds and voltage that you're achieving on stock settings, lower the entire curve as much as possible (using the core clock slider) and then use the curve editor to drag the same clock speed up at a lower voltage. So if you're achieving 1950mhz @1050mv on stock settings, lower the entire cuve and then select the curve point at 950mv and drag it back up to 1950mhz, hit apply and then it should flatten the curve after 950mv. Test it, if it's stable and you're happy with the temps/power then try increasing the clock speeds by dragging the same voltage point up by 15-20mhz. Rinse and repeat till you find the sweetspot balance of power, heat and performance. My asus 3080ti TUF on stock clocks boosts up to about 1800-1850mhz whilst pumping up to 1080mv into it, with a 975mv undervolt I can set the clocks to 2040mhz and it sits there pretty consistently and temps are around 65°C.
  23. edmuss
    I'd not tested that myself yet but I did notice I was getting good performance last night during quick testing. Will try to corroborate tonight
  24. edmuss
    Tested last night, kills the odd low resolution reflections in the KA50 glass (with line 87/88 commented out) and gives clear glass. Might tweak the 0.2 value yet but it does exactly what it says on the tin
  25. edmuss
    See my mouse cursor is pretty stable when it's slaved to the headset, perhaps it's a physiological thing?
×
×
  • Create New...