nikoel

Are you running re-re-reprojection?

I would rate MSAA somewhere between drinking orange juice after brushing your teeth and enabling Reprojection One undeniable fact of life however, is that It serves a purpose. But then again at what cost? Well the cost turns out to be over 50% of additional resolution, which at 6K+ is absolute bonkers. It additionally gives a blurrier image. So people are running a x4 blur filter over their images, to then try to sharpen it again via filters and mods. Each step taking more resources Many are trying to derive ways to reduce shimmer without the massive performance hit and are coming up with ways to do so None of them can touch MSAA in the shimmer reduction - but going from 100 to 150% still makes it better! - it's something we need to bear with until a better implementation comes along The other thing to keep in mind is that the guy running 150% has a significantly more detailed and sharper image than anyone with MSAA smear So what do you get? Well, guys with 1080ti cards who have accepted shimmer and a 10% reduction of resolution are now within a stone throw away from 3090's running MSAAx4. Proving that even I can outrun Usain Bolt if he is tied to a ball and chain An other thing to keep in mind is that OpenXR at least in my case has reduced shimmer significantly even with MSAA off (compared to the same settings in SVR) I am hoping FSR can be fixed and I can run my 200% resolution with 0.75 FSR to almost equal MSAAx4 SVR For the record I am running MSAAx2 (but this is because even after dialing up settings, I still had a heap of overhead left - so, I decided, why not?)

https://www.youtube.com/watch?app=desktop&v=tgWg3S4pR1U This is a good resource. A person who came to the same conclusion and made a video to correct this. He gets it right in the end The TL/DR version was pointed a few comments above yours

This 100% DCS is still DCS. Multiplayer complaints are for the lack of CPU utilisation which I highlighted a few times. Even Wags during an interview not too long ago has said that he expects much more performance uplift from multi threading implementations than from Vulcan. Man got a point. I can not name an other game which is CPU limited after I render over 7K combined resolution So you installed Open XR, but nothing has changed, you still only have a couple of threads which are now supersaturated driving your eye candy. This is because you can actually take advantage of the connection between DCS and your headset. Now you gotta slog multiplayer shenanigans on top. Not an ideal metaphor, but if this is not making sense - Before with SteamVR you had a bottleneck which "helped" the multiplayer performance in the same way a closing of a few lanes of the motorway "helps" the merging traffic flow after the roadworks. Now that the roadworks is gone, for people joining the traffic flow downstream it has gotten more difficult

Yes* As long as your overall steam settings were at 100% as well. Otherwise you're applying multiplications on top of multiplications Eg. Default Steam setting 50%, per app setting of 200% = 100% OpenXR gives you the final output in the second tab of OpenXR Tools

So hypothetically speaking. If I were in a F-14 and came by a black looking F5 with a red star on it I proceeded to do some manurers which would leave me in a low energy state, upside down but yet somehow directly above him, Would the guy see me giving him the finger or is this feature visible to the player only?

No friggin idea, but we are the lucky ones. I lost this "feature bug" when I was trying to recreate some of the issues that people were having to come up with solutions Today I got it back and I aint touchin' nothing! The apache is amazeballs like that

Double click Click next a couple of times Click Finish (It's openXR Toolkit that was updated - Not OpenXR itself)

I see. Sorry nothing much else I can add, however I can be as certain as one could possibly be when I say it's everything to do with the headset and windows mixed reality portal and nothing with DCS and whatever else you're running. In fact the torch doesn't even have an API and is completely inaccessible unless launched manually via WMR. I know this because I wanted the pass-through when I was still learning my winwing panel switch layout and couldn't quite get them by touch Unless it happens again I wouldn't worry about it. You'll be chasing ghosts and rainbows

Yeah this! The voice commands are a windows mixed reality for HP Reverb feature. Nothing to do with DCS. You can turn off this feature by disabling voice commands inside WMR. Can't recall which buttons to press, but if you google or just start flipping through various audio/mic tabs you will eventually find it. Just be careful going nuclear on these options otherwise you will find that your mic will be completely turned off https://forums.flightsimulator.com/t/flashlight-torch-effect-with-wms-and-hp-reverb-g2/359693

Make sure that Use VR Headset tick box is enabled inside the DCS Settings

Bruh! Seriously? ---------------- Anyway If you are using the EVGA Precision X1 software make sure to NOT upgrade to the 3/28 version. This is causing issues with OpenXR Toolkit. If you already installed it, you can delete the following file to solve the problem: C:\Windows\System32\FW1FontWrapper.dll. If the EVGA software is set to auto update make sure to disable that too

I would 100% agree with you except, you yourself have said you are getting stutters when you're looking at 9/3 o clock. I do not. Whilst our systems can exchange punches so to speak, both are overlocked to the tits, but you undoubtably, still have a more powerful system 3090/12700K vs 6900XT/3900X I can load up Syria and even global warming causing Marianas and get smooth performance looking all the way around. This is with repro off. No adult toys. I am going to try to capture this via the DCS mirror. Don't get me wrong reprojection makes the experience smoother still but this is because you're locked at 90FPS

Something fishy is going on. Time to start flipping toggles and shaking trees. See what will fall out There will always be performance differences. But the deltas between people with identical hardware is too high. Something is causing this One thing I noticed is that so far all 6900XT owners across the board saw improvements. Are there NVIDEA specific things that anyone can think of that could be affecting this

Yes

@speed-of-heat mate are you able to do me favor. I had a friend with a 3090 where I finally was able to replicate the sub-optimal performance that some have been experiencing. By your replies it leads me to believe that this might be the case for you. It turned out that somehow he had a version of old OpenXR installed. It refused to update. I removed all three apps and installed OpenXR Developer tools. Then navigated to the right most tab inside the Tools App which gave me a link to install the OpenXR Runtime via the Windows Store (something that I could not find by searching the store alone) - I installed that, didn't bother with the toolkit and got instantly the performance that I was used to with my 6900XT - (reprojection was off) The difference in frametime consistency and textures (clarity) was so night and day for me that I did not need any apps to tell me what was going on. I can see the individual bits of fluff on the F-16 seats. Fingerprints and scuffs on the MFD screens of F-18. In the F-14 I can read the Test Panel Switch (Bottom far right). This was impossible no matter the % in SteamVR. If it doesn't make you go 'wow' it's not working properly

By spending 3500 big green ones on a 3090TI AMD supports FFR only on DX12 and above

In case everyone is wondering what a mess VR currently is and why OpenXR must be the future and needs to be as quickly as possible Here is a diagram made by Mbucchia This is why this works so well for some headsets and other such as *cough Pimax cough* are not getting a single cent of my money

Updated the guide to include V0.6.3 Jabbah has reverted to using shader to do inverted copy as using FOV trick isn't working for all runtimes or with the OXR Toolkit. This should solve issues with those who are using this guide on headsets that are not WMR compliant (aka Oculus) If the mod is working for you at the moment, I would recommend not updating from 0.6.2 to the new version as it will do nothing for you

Chanel your inner owl boys

This looks to me like a reshade/shader issue. Tell me, you're not running or have been running the clearwater or any other reshaders have you? If the answer is yes, can you please use the Skatezilla utility to check for additional files (not repair) make sure you tick the box which says thorough check (I am paraphrasing, can't remember what it actually says) - I suspect you have legacy files hiding which were messing with the water Willkommen. Der antwort fuer deine frage ist hier https://forum.dcs.world/topic/295123-update-293-v062-openxr-quickstart-guide-for-g2-g1-and-other-headsets/?do=findComment&comment=4932461

This is an issue with wrong UAC settings See here https://github.com/mbucchia/OpenXR-Toolkit/issues/136 Don’t forget to thank Mbucchia

To answer your questions - its agnostic to updates. In a nutshell Jabbah has created a translator file that talks to OpenXR, this is what the file does primarily. However it's likely that the future update may overwrite/clean the files you have replaced inside the bin folder. I encourage you to back them up and after DCS completes the update pop the three files back in afterwards This will continue to be the case until the implementation of Vulkan. Unfortunately then it's likely we may lose this mod

Thank you for the kind offer, but the real MVP is Jabbah and mbuccia for they are the ones who took time to develop and explain everything to us. He is the one who deserves the praise and the beer. Hit him up with your success; I'm sure he will appreciate it I'm glad it's working for you so well

The Reprojection bug for DCS has been identified and is being actively worked on Whilst it's possible - I am just going to say it to you straight to save you suffering and disappointment. At this current time, this will not be implemented by DCS. DCS developers are working on Vulkan implementation. OpenXR on WMR does not currently support Vulkan. Therefore it would be wasteful for them to put devtime into this, especially since multicore has been in discussion since 2009. This will change in time. But at the moment this is the best there is. In just over a week, Jabbah, Mbucchia and the community have solved almost all issues. You have seen some people who have been - lets say critical - of it's value come around You have two options - save your virgin vanilla DCS for marriage, (oooof, Sweeeeet home, Aaaalabamaaa! Maybe a bad analogy. According to Wikipedia DCS is 14 years old) or just drag and drop three files into the bin folder let your hair out and have some fun. (Okay a really bad analogy - but the point still stands) Ironically you would not have any issues because your install doesn't suffer from left over junk I have been updating the guide almost every day to make it more and more water tight - errors have been worked out. The issues you see are from people not reading, taking shortcuts with OVGME or simply not doing steps that I've spelled out eg. Setting PD to 1.0