Jump to content

WipeUout

Members
  • Posts

    627
  • Joined

  • Last visited

Everything posted by WipeUout

  1. Presently, it seems that results vary a lot depending on hardware. With a Pimax, OXR + MT is really bad in term of stability and quality of visuals compared to SVR. I get my best results with OVR + ST version, the image is clear, crisp and stable over time. I will admit the performance wise, OXR is a bit better, until it starts wobbling. Nevertheless the image is not as nice and clear. We are still in the early stage but as of now, I prefer OVR which seems much more mature and stable. Will OXR reach this? It take resources...
  2. Well OXR is pretty good performance wise but very unstable with a Pimax, I have to turn on OXRTK turbo mode and limit FPS at my refresh rate to get rid of wobbles and stutters and still very unstable. OpenVR is working well but only in ST, MT is good but not possible to use Reshade with it. We are at the early stages of MT implementation... Looking forward to get DLSS implemented, I think this will come before Vulkan.
  3. Yup. With the last iteration I was seeing no more that 0.5ms of frame time improvement and that was with 2.7.18.
  4. What do you want to use it for? VR Shader no longer provide added performance and for the other stuff such as haze reduction, there are alternatives as indicated above.
  5. I think it is still not implemented in DCS. If you enable it, the little gear next to the feature in nvidia inspector remains blue. If a feature is enable, the gear should turn green.
  6. With the settings you mention probably yes, I can with my 4080. But the real beauty with the 8kX is running at native resolution which gives a very detailed view and minimize shimmering to a tolerable level without resorting to MSAA. Of course the view is even better with MSAA, almost perfect. I keep my refresh rate at 60hz to avoid any upscaling and can even afford MSAA 2x without problem on busy multiplayer missions with plenty of headroom. The 8kX at native resolution is really shinning.
  7. Reshade is not compatible with the OpenXR runtime. Reshade will not work with MT using SteamVR runtime either. Only possibility to make it work is ST with SteamVR runtime.
  8. Yup, MT working in SteamVR but can't use re-shaders. Performance wise, it is similar OpenXR CPU frametime.
  9. I disagree, Pimax is not a plug and play but no worse than G2 and the extra WMR layer and miriad of possible settings. Speaking from experience. The state of things in VR is that there is no standard, every manufacturer have their own approach and it takes time and effort to optimize any HMD nowaday. There is also the PC in the equation, which have endless combination of hardware and requires tweeking and testing to get the best VR results possible. If it is a bigger sweet spot you want, then Pimax has that. Unfotunately, it might be difficult to get one, except the refurbished units on pimax.com. Cost is also something to consider because Pimax cost significantly more than a G2 considering you need a lighthouse and maybe controlers.
  10. Reshade substitutes a DLL (dxgi.dll) in the DCS\bin folder and adds a "Reshade" folder with some other files and folders inside. It will only work with the ST version, not the MT even if you copy the files in the DCS\bin-mt folder. For now.
  11. The only Reshade mod working with DCS that I found is ''VRToolkit Reshade'' (https://github.com/retroluxfilm/reshade-vrtoolkit) and it only works in SteamVR. Seems that OpenXR is not playing well with any post-processing mods, might be because it does its own post-processing and uses the same DLL. In any case, DCS-MT with Pimax and OXRTK/PimaxXR is not working very well and very unstable. I use DCS-ST with SteamVR with Pitool's Foveated Rendering (now working) along with VRToolkit Reshade, it is very stable and offer very good performance.
  12. You are right, this is another solution. But there are also issues with SteamVR. Very glad you ask that question because it is not a bad option now! First, when using the MT version, the Pitool Fixed Foveated Rendering (FFR) does not work. FFR is a powerful feature that can improve performance significantly without sacrificing too much quality. With the wide FOV of the Pimax HMD, it is the ideal HMD to use with this feature. Unfortunately I tried many times, including today, and it will not work with SteamVR. On the other hand, it does work with the ST version which is new and welcomed as it lower GPU frametime considerably. From my testing, I have found a 1.0ms reduction in GPU frametime. This is using the balanced setting. This feature in Pitool is as good as the one found in OXRTK giving very similar results in improved performance. Second problem is the loss of sharpening with MT. The CAS sharpening option in OXRTK was very useful as the default VR view in DCS is very blurry. There are no sharpening options in SteamVR unfortunately but some mods can help. I tried many re-shaders and none seems to work with MT. On the positive side, I found that VRToolkit Reshade works perfectly with the ST version. This is also very welcomed. You just have to find the sweet spot as too much sharpening can make the FFR circles visible. In all, the ST version using SteamVR is pretty good and on par with using ST with PimaxXR/OXRTK as far as performance. I also noticed that SteamVR seems more stable with less random stutters. I still need to do more testing but so far so good, this is what I will be using going forward until MT is fixed.
  13. Do you have his contact info?
  14. I run my Pimax 8kX at 60hz in order to get native resolution, 90hz is not achievable without scarifying image quality too much (for me). My 4080 is pretty good and the i9-13900KF is smoking fast but we are not there yet and I doubt very much I could drive my 8kX at 90hz even with a 4090 at the same level of details going multiplayer in Syria. MT is not the determining factor for me, my CPU is pretty powerful. But if you play dynamic campaign like DCS-Liberation or fly on enigma server, then MT is making a difference.
  15. I just tried also and it solves the problem but not 100%. Occasionally, the lag/wobbles will start but will not last very long, it will go away as soon as you start rolling the aircraft. Another way around is to use PimaxXR 0.2.4 instead of the latest 0.3.2. This will remove the lag/wobbles but may introduce some micro stutters which was what I experienced. The previous workaround is better for me. I used 61 FPS for frame rate throttling (since my HMD refresh rate is set to 60) along with turbo mode "ON". I did notice a slight loss in performance of about 0.5ms increased GPU frame time though. Not a huge problem. @mbucchia (author of PimaxXR) commented on github that he will not able to get back to his PimaxXR project before May, we will have to be patient for a more elegant solution.
  16. Sad but relieved to learn that it's not only me. I have installed OXRTK 1.3.0 and it did not correct the issue, on the contrary I got back the wobble/lag in the menus again! I can't rule out either PimaxXR or OXRTK for causing the issue, this is puzzling. I'm thinking about rolling back to Pitool 1.0.1.281, since this is the stated "better" option for compatibility with PimaxXR 0.3.2 according to the wiki on github, and see what happens.
  17. Instable experience so far. Not sure what is causing it but when using PimaxXR and OXRTK with the MT version, I get what looks like HMD tracking issue with image lag and wobbles as soon as I move my head. This starts when I switch view from cockpit to map but not all the time. The wobbles and lag goes away after a while but not always. I haven't found what is causing this nor how to stop it. This issue was also present in menus prior to the latest OB but not anymore since OB 2.8.3.38090. I have to try OXRTK 1.3.0 to see if this will correct the issue, I am still using 1.2.4. When my "tracking" problem is not happening, my performance is great with MT. My CPU frame time dropped dramatically from 8.2ms down to 3.3ms. On the GPU frame time, there is also a good drop from 12.9ms to 11.6ms. This is GPU performance that is even better than what I had with DCS 2.7.18. As a result, I can now use MSAA 2x and maintain 60 FPS and 100% native resolution in any situation including flying in Syria over Aleppo at 1000ft. I'm using same settings in OXRTK with fixed foveated at 55/80/100 and nothing else. In Pitool, I increased backlit and brightness to compensate my gamma setting in DCS. I now use a DCS gamma setting of 1.3 which effectively reduce haze quite a bit but requires higher level of brightness/backlit. I do not use smoothing or reprojection, nor fixed foveated in Pitool as it does not work. I keep same settings in DCS with clouds normal, flat shadow with blur off, no anisotropic filtering, vis. range ultra and now MSAA 2x.
  18. I have this problem and use the ST version with SteamVR to minimize the problem. The worst is with OpenXR with MT, stutters and wobbles come and go all the time and very sickening. Even MT with SteamVR is bad with stutters every 2-3 seconds. Not sure if it is pimax related but one thing for sure, we are still in beta for MT...
  19. Last DCS update corrected the menu issue but now I have instability in-game every now and then. The tracking becomes lagy when I switch to map or external and stabilized a while after, very annoying and difficult to reproduce. Any having these issues? I am back to SteamVR with the ST version for now.
  20. For me there is a significant improvement, close to 1ms GPU frametime decrease. This might be very different depending on hardware. Unfortunately, PimaxXR is not working well in MT with the menus but ok once in the cockpit. Test I ran using MT with native DCS OpenXR support brought me back to 2.7.18 performance at the same level of details and settings!
  21. Firmware update with Pimax needs a bit of polishing. I did it with three different HMDs and none worked on the first attempt! Fortunately, it did work on the second try and guess I was lucky. Seems that some issues with Pimax are persistent even if you reboot, I had to completely unplug all cables and wait a minute, replug and restart the PC for issues to go away. There is a price to pay for this wide field of view...
  22. Lots of rationalization and anecdotic facts here. Pimax 8kX is the ultimate immersion experience, tried many other HMD and tunnel vision is not good in flight sim. Try a well optimized 8kX setup at native resolution and you will be blown away. Will not speak about the Crystal until I try one but right off the bat, its FOV is not as good as the 8kX. ...speaking from experience
  23. New MT compatible version was uploaded. Go here:
  24. It s a balancing act. When the simulation spends time recording and saving input (head movement, keyboard, joystick, etc.) it takes resources away from the main task: Simulate! The reason why tracks are not 100% accurate is probably because the capture frequency (or sampling rate) is not keeping up and you end up loosing input. To solve this you need to bump up sampling rate and consequently you redirect resources that should simulate instead of doing telemetry. So the other solution is to re-design the capture engine, lots of work. Make a track, keep it short and that will do the job. Just don't use the F-14, it is broken as far as track recording.
  25. A DCS track is an automatic recording of keystrokes and controllers input captured while flying a mission. In order to fly a mission, you need the map and the aircraft module. If I understand what you propose, you would have community members creating the tracks with all possible combinations of airframe/map/mission type, and then have those tracks selectable as part of a benchmark? Not simple nor easy. Everyone has the liberty to create tracks that are relevant to their gameplay, more easy and flexible!
×
×
  • Create New...