nikoel

Yeah, us Ausies got shafted with the supplies of these and I was lucky to get one a full week after they launched I have a Noctua D15S inside a Fractal Torrent case - Not that cooling matters with this processor. She is locked and stock is all that we are going to get. Even the ram speed no longer matters as much as it's used to due to the cache I'll see if I can mess with PBO and under-volt to maybe let it boost slightly higher. But it may be a waste of time - There is a guy on youtube who OC'd his to 4.8 but the steps he had to take were ridiculous and my motherboard does not have such functionality. There is talk of AMD unlocking some OC options in the future

Alright so my uplift coming from a 3900X at 4.5gHZ OC on a 6900XT @3.9Ghz and 64GB 3200/CL16 Ram to 5800X Stock All recordings were made with OpenXR using OpenXRToolkit Inbuilt frame timing overlay I used supercarier population with full crew and all aircraft slots on deck, multiple aircraft taxiing and taking off and additionally some flying. Very punishing, borderline artificially heavy CPU limited scenario. This is setup looking directly at the street/six pack where there was the most amount of action. The reading was taken after ~10seconds of waiting for things to settle down in exact the same spot without moving inside the F/A-18 3900X - ~30ms - (Red CPU Penalty 9ms) 5800X3D - ~19ms = Uplift of 61% (No CPU limitation message) Apache on Syria Hotstart (Not a static test, taking off and doing a loop around the airfield) 3900X - 13-24ms 5800X3D - 9-16ms This was a test of consistency rather than performance. What these figures don't show is how "locked" and smooth the experience was in comparison. The occasional stutter I had was gone I am impressed. Anyone on AMD with a AM4 1k, 2k, 3k system looking for an upgrade this is a complete no-brainer. If you're on intel the proposition is a difficult one as AM4 is now dead end platform. I am glad that AMD released this last hurrah especially for DCS where the uplift has been better than I initially hoped for Additionally the uplift looks extreme. But this is because the readings come from a very CPU limited scenario. Under normal conditions the uplift will be anywhere between 0 (Fully GPU bound) and that 60%+ figure I yet to test multiplayer

Link is now live fellas. We get an other 24hrs/1GB. Get in whilst it's still fresh

64

The guide links directly (Page 1 Post 1) - but the download quota for the day has been exceeded

openvr_api.dllHere is the per app .dll that fearlessfrog was able to snatch before the show ground to a halt This is not .exe - this is the per app install I would recommend waiting a few hours for the quota to be reset but I know some of you wanted to install it this way

Alright so bad news. We have blown up the OpenComposite server and exceeded the limit for the day. So on first launch the DLL's are not fetching. I believe it refreshes at 0-GMT and we get our download quota back

This is outdated (skips steps) it links back to to here and should not be used -------------------------------- Alright fam just confirming that everyone is on the same page with this There are two places where you can get the .exe and I think there may be confusion which. You want the version with Jabbah's face on it - the /tree/openxr The master version does not work https://gitlab.com/znixian/OpenOVR/-/tree/master - Not this one https://gitlab.com/znixian/OpenOVR/-/tree/openxr - This One! And to update to the new version the old OpenComposite (0.6.3) must be gone (Full clean/repair and extra file check)

Yeah that was my bad. I replaced the wrong links. Two wrongs don't make a right. It should be all working now

Thank you. One second @Sr. plz try again

New Instructions are now live

If you haven't updated and would like to help can you please do the following 1) Clean your entire DCS folder thoroughly using the skatezilla utility (make sure to check for extra files). Old OpenComposite should no longer exist (not even the ini), start with a clean install 2) Download this: https://znix.xyz/OpenComposite/runtimeswitcher.php?branch=openxr - Then run OpenComposite.exe 3) Set runtime from SteamVR to OpenComposite (Which connects to OpenXR) 4) Delete/Rename your D3DCompiler_47.dll inside the bin folder (eg D3DCompiler_47dll.orig) 5) Launch! 6) From now on only create an .ini if you have a specific purpose for it. I have attached mine - in the past it has helped me with VR controllers and mouse On startup, OpenComposite searches for a file named opencomposite.ini, first next to the openvr_api.dll file, and if it can't find that, then it looks in the working directory (usually in the same folder as the EXE). If no file is found, that's fine and all the default values are used I Have tested the above with and without this specific .ini and both work great. Also the application has a built-in update utility so no more manual installs and updates. Neat! (Except for when DCS updates and restores D3DCompiler_47.dll) opencomposite.ini

Heya Yes I will definitely update the guide and have a few extra additions that people have been asking to add (eg. The DCS eye tool for Oculus users who are experiencing the fishbowl effect). I started this already, however I am holding off now because there is a significant difference in the way people are installing the new version. The way I did it, seems to be an outlier (if you did it my way please yell out if it worked for you). So I rather wait and be 100% sure that the instructions are correct rather than updating asap I also want to add that 0.6.3 currently is equal to the new version. All the new version does is merge Jabbah's changes to the official branch. If it's working for you, you gain nothing from updating to the new OpenComposite main fork. However your sacrifice is appreciated because it helps to iron out the kinks

Perhaps it's 62 pages because you keep reminding us how you don't run any mods every page of this thread. The start guide is all entailed in the first page The reason it didn't work for you is because you a) Failed to follow instructions b) Complained about it - by saying that I was assuming everyone is a programmer (ignoring that literally thousands of people were successful before you) c) When you finally got it work, you instantly gave up because of colour saturation even though you could have easily dialled it up with 4 keypresses like everyone else d) Cranky, set in your ways and stubborn This is not for everyone. Real issues with compatibility exist and being actively worked on. We are helping each other - however there is a strong correlation between competence and success. If you dedicated even half of your effort towards OpenXR that you do repeating the ol' phrase above you would had it running beautifully Jabbah, Mbuccia and so many other people have given up their time to help us. They are hugely talented and their time is infinitely valuable and they have spent it on helping us. M Bucchia works for Microsoft and his team in the early stages released a version for DCS. He didn't have to do this This thread would not be 62 pages long if it was some useless piece of bloatware. If you look at any Hoggit VR post recently for WMR headsets, you will find OpenXR in there somewhere. Here I literally found one by not even scrolling the front page You're entitled to your opinion, but your opinion is crapping upon the people who have helped us. This is not right

Wut? I cleaned DCS super thoroughly as always Downloaded the standalone OpenXR installer. Unpacked and activated across the entire system Dropped the extra file that is above into the folder and that was that (I guess you can use the standalone [per game] installer as well) Why would I use Oculus? The D3D file above is the exact the same as the one provided by Jabbah in the latest release of his fork of OpenComposite

I have the latest everything (OpenXR, Toolkit etc) and it works I no longer use Jabbah's fork, and instead utilised the official install of OpenComponsite above Not sure what your %PATH% is so can not help you. The file goes into the bin folder as always

You still need Jabbah's original D3DCompiler_47.dll to make the installation work D3DCompiler_47.dll

Update 25/4/22 OpenComposite Official Branch has been now been merged with Jabbah's New installation incoming, but for those who can not wait, you can find the official documentation and instructions here: https://gitlab.com/znixian/OpenOVR/-/tree/openxr Note you can install globally (all SteamVR-based games will use it automatically) or via individual installs (per game) Also! For those of you who are into witchcraft you are undoubtedly using bundled VR controllers whilst flying inside of VR. You might be getting the random vibration activations. Haptics can be disabled via the following line in the .ini to disable the sex toy mode (not tested by me) haptics = off

Update 25/4/22 OpenComposite Official Branch has been now been merged with Jabbah's New installation incoming, but for those who can not wait, you can find the official documentation and instructions here: https://gitlab.com/znixian/OpenOVR/-/tree/openxr Note you can install globally (all SteamVR-based games will use it automatically) or via individual installs (per game) Also! For those of you who are into witchcraft you are undoubtedly using bundled VR controllers whilst flying inside of VR. You might be getting the random vibration activations. Haptics can be disabled via the following line in the .ini to disable the sex toy mode (not tested by me) haptics = off (My bad meant to post this on the other thread)

He has motion vector on so the test and report is very limited in it's usefulness When this is enabled the excess frames are discarded. This means there is no difference between rendering 46FPS or 89FPS. The system will always render one artificial frame followed by one real one The only difference he will see is on occasions where his frames may have fallen below 45. If he had SteamVR he would have seen a stark decrease in fluidity and frames which theoretically could have been eliminated by the new processor; if OpenXR then a decrease to a 30FPS Reprojection, which is a little more difficult to spot The stronger processor will enable him to crank settings harder since there is no advantage in rendering say 70 or 80fps over 50 other than additional overhead or as you've said in multiplayer servers where the extra overhead can be used towards that

Does a bear crap in the woods? Don't expect any graphs from SteamVR. I am using the same settings and options as in my OpenXR thread, I will try to get some graphs from AMD logging utility and OpenXR Toolkit though

A Christmas miracle (in Australia). I actually was able to get one that was in stock Review incoming (soonish)

This is for the combined performance across many titles. But DCS is unlike any of those titles tested. It's one of the very few remaining games out there that can be still CPU limited [chocked] even at 4K or 7.5K (in VR) Best is to wait for early adopters to get their paws on it and see the performance gains (or god forbid losses) - I’m going to be one of them Out of all the benchmarks, Assetto Corsa is most similar to DCS as it only utilises 2 Threads. The SiNgLe ThReAd PeRfOrMaNcE iS kInG comments are kind of thin though. 5800X3D with lower clocks and IPC beats 12900K there by over 20% - additionally with the latter running one of the fastest DDR5 kits that cost more than 5800X3D On the other hand Cities Skylines which is also single threaded had the 5800X3D trailing 12900K by 5%. I suspect this is the case because Skylines is fairly simple and requires a lot of compute rather than memory storage to Brrrt frames at you Many simulator style games are limited by draw calls and this bottleneck is significantly helped by the extra cache. In VR - Consistency is king. I strongly suspect there are bottlenecks within bandwidth for DCS. I am hopeful that I will be correct, but only time will tell. Aka tomorrow (or maybe day after? Since in Australia we seem to get things a day late)

A bit of progress for those who are on the #strugglebus Nvidea graphic card holders disable hardware-assisted GPU scheduling. This is especially the case if you run OpenKneeboard or any of the additional non-standard addons. Failure to do this can in some instances give you a penalty of around ~20FPS. The issue stems around multiple processes using Direct3D/2D concurrently