WipeUout
-
Posts
627 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by WipeUout
-
Great post @everest101, thanks for starting this. I have not tried with my 5k Super but will do eventually. As for my 8kX, the native OpenXR DCS support is providing even more performance compared to using opencomposite. I have gained 1ms in GPU frametime and 1.3ms in CPU frametime with my test track in Caucasus with the f-18. I set pitool at native resolution, 60hz, normal FOV with a bit of backlit increase. No compulsive smoothing whatsoever and no fix foveated rendering as it does not work in DCS from pitool. In OXRTK I use fix foveated rendering at 55/80/100 and the performance gain is really good. The Pimax HMD is the ideal VR headset to use fix foveated rendering because of the large FOV, but personal preferences may vary. I use also CAS sharpening at 80%, no modification of the resolution. 4k native is very nice and clear, I do not use MSAA anymore as the higher resolution is the best cure for aliasing. If you have the newer 8kX with 90 hz minimum refresh rate, you might still need some compulsive smoothing or to scale down some settings.
-
I paid 900$ for my refurbished Pimax 8kX directly from pimax. 4k per eye, 170 degree FOV... Not going back to tunnel vision!
-
You will not be able to lunch from Pitool but this does not prevent settings in pitool to apply. You can still set whatever setting you want in the "Common Settings" and they will apply. The "DCS.exe" shortcut with the command line arguments is required to run in OpenXR and this is well explain at the start of this topic. You still have to option to use opencomposite as before but by using the native OpenXR support within DCS, you will gain even more performance. I have gained 1ms in GPU frametime and 1.3ms in CPU frametime using native over opencomposite, this is quite significant. Make sure you use the latest versions of PimaxXR (0.3.0) and OpenXRToolkit (1.2.4) for this to work, and also very important, latest pitool version (1.0.1.284).
-
I don't think that rBAR is working in DCS. Did a bit of research and when a feature is working, in the game profile of nvidia profile inspector, the little gear beside the feature is green. If the feature is not working, the little gear icon stays blue. nullnull
-
fixed 2.8.1 still has serious issues with terrain objects shadows
WipeUout replied to some1's topic in Game Performance Bugs
Yes and No. We now have native OpenXR support in the latest OB. I gained quite a bit with about 1ms in GPU frametime and 1.3ms in CPU frametime. Of course, results vary depending on your particular hardware. Look here to see "how to": -
OMG, finally got OpenXR to work with DCS Native support from latest OB version. I did not have Pitool 284 installed and this was causing the issues. The results are stunning, I have a GPU frametime improvement of 1.0ms and even a CPU improvement of 1.3ms with same settings running my test track file.
-
When I downloaded it, I created a folder for OVGME and labelled it "OpenComposite 0.6.3"...
-
..or simply hide the HMD from the lighthouse for 1 second. BTW, one lighthouse is fine if you only do DCS or any VR in sitting position.
-
Have a look at your log if you can notice any error at the end. Since you say that single player works fine, then this is weird. Post a new bug with your dcs.log, dxdiag output and as much details as possible.
-
Yes, the OB 2.8.2.35759 only. Very confusing indeed but the first two post here are very clear and detailed: https://forum.dcs.world/topic/318004-dcs-now-supports-openxr-natively/
-
I use now the opencomposite dll to switch from OpenVR to openXR runtine and bypass DCS native OpenXR. This version (0.6.3) is the one that works fine with PimaxXR 0.2.8, it is attached and it goes in the dcs\bin folder, as you probably know. If I you want to use the DCS native openXR support, you do not need the opencomposite switcher but need to have PimaxXR 0.3.0 and OpenXRtoolkit 1.2.4, and add two arguments to the command line (see first subject in vr forum), but in my case, it does not work well. openvr_api.dll
-
I just switched the 8k+ for a refurbished 8kX by Pimax. Wow, what a difference! Running native 4k at 60hz with no repro or MSAA and the image is simply stunning. Resolution is the cure to aliassing, MSAA is not required anymore. Running at 60hz gives a lot of breathing room and I can use low shadows, normal clouds, medium water, high textures in any scenario without exceeding 16.7ms frame time. Of course there is always the exception such as missions created for DCS-liberation that eat up your CPU like crazy. But even in Syria, I am flying without need for any reprojection. Native 4k per eye is so beautiful! Unfortunately DCS Native OpenXR introduced with 2.8.2 does not work good for me though. I had to revert back to using opencomposite instead of the command line switch to force OpenXR. Even using Pimax XR 0.3.0 and OXRTK 1.2.4 did not help. The issues I had were two fold: 1. Stutters when moving my head up/down right/left. 2. Blurry image out of focus or having left/right image synch problem. Going back to PimaxXR 0.2.8, OXRTK 1.2.1 and opencomposite 0.6.3 solved the issues. Wonder if this only related to the 2075 serial number 8KX or also present in 2076 models?
-
If it is only in MP server mission that you have this issue, it might be related to your client not being ''pure''. Do you have any mods running that breaks IC? There is an icon that is either green (OK IC) or red (IC broken) on top of the server list. The other issue could be that you are missing a required/compulsory module to access the mission. This should show in the bottom left corner in the server description when the specific server you want is selected.
-
Difficult decision. I would tend to go with the 4070ti because of the new architecture and DLSS 3.0 support. Because it is faster than a 3090. Because its power draw is much less than the 3090 and depending on the power of your PSU, it might be necessary to upgrade it as well. Because used hardware has higher risk of defect, abuse or plain scam. There is also the option to wait and save a little more to get that 4080 or even the 4090 which will give you incredible performance for years to come. The G2 has a high resolution and being able to enjoy it to its full potential takes a lot of GPU power.
-
Found the culprit: Options.lua The file was corrupted by starting my steam version which was not the same as my non-steam version of DCS. When I replaced this file from my previous Savegame/DCS/config folder, the GUI did not start. Reverting back corrected the issue but I had to re-set most of my options. At least I did not lose my flight stick/throttle/pedal config.
-
Worked! Thanks @Flappie. Now, what can I copy back in the newly created DCS folder in order to get my settings back? The "config" folder? Obviously, the mission folder should be straight forward but would like to avoid file by file trial and error...
-
The GUI, either in 2D or VR, is failing to start. I tried to do a repair with no change. I tried to revert to 2.7.18 with no change. In VR I see the hangar with the MIG-29 but no GUI. In 2D, just a black screen. Tried also both SteamVR and OpenXR and no change. There is an error message in the log stating the GIU failed to load, but no idea what is causing it. Help! dcs.20230204-200407.crash dcs.20230204-200407.dmp dcs.log DxDiag.txt
-
Since DCS native support for OpenXR was introduced, I reverted back to OB 2.8. Unfortunately, running the sim with PimaxXR 0.3.0 and OXRTK 1.2.4, I started to have "convergence" issues and stutters as soon as I would start moving my head. Reverting back to use Opencomposite and PXR 0.2.8 and OXRTK 1.2.1 made the issues go away. What I labeled as "convergence" issue was causing the image to be blurry, slightly out of focus. It could also be a slight de-synch between the right and left images. As for the stutters, they were appearing just at the start of a head movement, one or twice, and then go away. My frametimes both for CPU and GPU were well below 16.7ms, not even close. I have the 60hz / 75hz Pimax 8KX (older) model and run the HMD at 60hz. I do not use motion re-projection and my resolution is 4k native. Sorry, I did not have the reflex to save my dcs.log file. @mbucchia, could this be related only to the older 8KX?
-
Difficult to assess if your performance is where it should be. What map, airplane, mission are you using? What are your DCS, NVCP, SteamVR (or OpenXR) settings? A lot of variables can influence performance. Also, are you monitoring your CPU/GPU frame-times? This can help tremendously to guide you, fpsVR for SteamVR is a good tool for that and if you are using OpenXR, there is an option to display this info as well.
-
Happy you had a good experience with a used(not much) GPU. I was not so lucky before getting the 4080 when I tried to get a cheap ''refrubished'' 3090Ti from eBay. The card was completely dead, not even fans turning when powering on. They did reimbursed 100% plus shipping cost to get it back but after this episode, I went for a new GPU. Did you noticed any image quality improvement over the AMD card?
-
No but I don't have your horsepower with my 4080. One thing I tried is flying with 120hz HMD refresh rate with reprojection on. I find that running 60 FPS on reprojection creates far less ghosting than 45 FPS when HMD's at 90hz or 37 FPS when my HMD's at 72hz. Granted that the Pimax is a different beast.
-
Thinking alone fails again. What is being simulated in MSFS, X Planer etc.. is much less demanding than a FULL COMBAT SANDBOX like DCS. Adding yet another dimension like weather modeling, would for sure be cool and increase realism but at a cost that would result in even less performance. It already takes a top rig to run DCS in VR, last thing we need is more stuff being simulated. DCS needs to first solve performance and then look at cranking additional realism or whatever the customer wants next.
-
I believe that DCS does much more as far as simulation of other stuff such as weapon, enemy AI, troop movement, radars, etc... Very different sims!
-
Just make sure you set power management to "prefer max power". You may also use profile inspector to check that rbar in section 5 is "enabled", by default it is disabled. Other settings leave to default.
-
Never mind, I found the lines in the 2.7.18 file version, they are the same but elsewhere. Even in 2.7.18 there is a noticeable improvement, I gained 3 FPS in the F-18. This is very good and almost gets me to go back to 2.8.1... Almost.
