Hoirtel

Every system has a "bottleneck" at some point. I.e it all goes as fast aas the slowest component/process. If this wasn't the cse then we would all have unlimited fps. The trick is to balance your settings to make the best available of your resources as discussed by @Dangerzone Also really, really important in DCS VR to make sure that you reduce background load on the CPU. All those updaters and background apps really can affect DCS. If you haven't killed these off then do so, you have gains to make as your description clearly shows you were/are CPU bound. I have seen VR improvements over the last 2-3 years. The game has also been updated considerably in this time too, which has also requires more resources so its a balancing act but ultimately, with all performance PC stuff the hardware doesn't actually get much older in 2-3 years. The software just gets newer.

I think we need to remember that everytime we buy a module you also pay a bit for the base game. Thats how it works. With the all work that goes into all components of this platform, I'm ok with spending a bit on it. It's a much preferable option to a subscription.

It does really. It's the in game sounds. I used to use Sim shaker and also found it a little inconsistent. Just using the game sound is very consistent. The newer modules are definitely better than the older ones for the low frequency noises.

You should prioritize flying really.. NVCP effects are mostly mild both in effect and impact. Use it for fine tuning if you need to, but just start on default.

Ok sounds like we do have the same thing set, I thought you had the mouse cursor locked to the centre of your view. You must mean about dragging the mouse slightly off when moving you head, Yeah, I suppose that can be an issue. Possibly just takes a little time to get used to. I really like being able to manage the mouse with both and i don't find it a problem. Complete detachment isn't really possible as the mouse is still really a 2D entity and has to be on the screen so when you move you head and change what is displaying on the screens the mouse has to match. Other options are lock it completely or use the VR controllers. Neither of those I like. Good luck.

I can't remember exactly but I play in VR and do not have the mouse locked to head movements. I have seen others that do (they even rebind the mouse buttons to a hotas). I personally wouldn't like it. The cursor is mostly free to move anywhere, however on extreme head movements it does drag it to the general area but can go anywhere that is on the 2D screen/mirror. I think DCS has the best VR mouse implementation I have used. Something about xplane and MSFS that just isn't as nice. Might be "confine cursor to window"?

Fair enough. I guess you gotta do whatever it takes. I've yet to switch to win 11. I had read oculus didn't like it much, however the latest v41 has a note about increased win11 support. You think it's better than 10 for oculus DCS?

It is very doable. It's an option in the VR tab.

Is there a comparison between all of this modding and just running it normally. I'm still not convinced the oculus needs to be modded like WMR headsets.

I don't use OTT anymore. Adaptive ASW means it will switch this on and off when you need it. It will nearly always be on. The 45/30/18 really means ASW for half, one third and one quarter frame rate. The actual numbers are only relevant for 90hz. As I don't use OTT I never set these. I just leave it on auto and let it do what it wants. Oculus doesn't need too much under the bonnet tweaking these days. You will probably get better visuals setting resolution yourself as you will go higher, but it will cost a bit of performance. On your hardware I would expect you to be able to go higher than default. Default values are low so that nearly anyone can plug it in and it will be smooth from the get go.

I think it always recommends 72, I guess that will always been the best performance. It does on my system 3090+9900ks I set that slider to max. I can run it but any more would be too much. Ignore the 1.X values they are meaningless and have nothing to do with the resolutions. Set this manually, working your way up. At 72hr I would expect you could max it, and tweak performance in the game settings.

Hi, I think many posts about the Q2 are relevant here now that the rift is quite old. I use Q2 with ASW at 80Hrz. Lower will be easier to for your computer to run. I personally find 72 uncomfortable on my eyes so I go with 80. To me airlink and link perform the same. Airlink success depends on your home network set-up. I use link for extended battery life (I have Internal battery only) For settings you should find some in the thread. I very much doubt any two will be the same. Keep your PC background tasks and applications to the bare minimum.

I currently run a q2 on a 3090 with 9900k and the graphics are fine. It runs well, the cpu can get bogged down in heavy scenarios but nothing too bad. I play engima in VR no worries! However I want more! so I will be changing to next gen AMD or Intel, reviews depending. So you could just upgrade your GPU and wait. I'm very interested in this thread and the cache improvements that AMD are bringing so it may may AM5 a good choice even if the 3D chips do not come in first release. Then of course there is the 40 series Nvidia coming too..... Overall I would wait completely.

Hi, really enjoying the server. Great work, I may have just missed it it but is there a list of nav frequencies for airfields and farps? I find it really difficult to keep checking on f10 in VR. If they are somewhere I can make a kneeboard for them. I'm mostly in f5 or hind (never in the same session!) Thanks

Interesting this seems to hit the GPU times hard. I bet Aleppo hits CPU more still.

I can't get the link to the paintkit to work at all, very very slow then fails. Anyone got a good copy? Its the same link on the Razbam website

Hmm, I used to switch off GPU scaling but I really couldn't tell any difference so decided that it probably wasn't scaling all that much if at all. I also used to change bitrate and encode width, then I read that oculus sets encode width automatically off bitrate so I left this at default. Again no perceivable change in any direction. The bitrate definitely used need setting manually setting but I also read that 500 was a bit over the top, I set at 300 - no change and now again at default, no change. I have occasionally re-tested these but I really don't ever see any differences. I also used to lock ASW at half (40 for me) as It does go to 80 at altitude and the switching was jarring, again they seem to fix this and I just can't tell for the most part. What do you mean when you say kept ASW? Lock it to half only or allow it to auto on/off. I know where the distortions are its not something I find a problem in DCS, just one of those things. Unlike the civilian sim which I think ASW is horrible in, but that's a separate story. I didn't realise ED had updated their guidance but its kind of minimal. I should also add that I always run on the cable, keeps the battery topped up. Airlink appears to be indentical performance but I actually don't have that much DCS hours using it. It is great for shooting zombies though!

Its a shame considering that the kneeboard is pretty difficult to work with anyway, this just makes it harder and on a map that really benefits from good information.

I only change FOV these days. Everything else is at default so I don't mind.

For me runs great everywhere, but towns are suprisingly hard, like small bit of the marianas. This is suprising as I can fly over cities in Syria with minimal problem and Vega/Dubai with no issues and they appear much bigger with more objects than any of these towns. It could be that this will change with updates.

Well I've been running oculus since the rift s days. Not an oculus fan really but they just been the best for me (personal preference) advice would be ditch all VR management mods. Just use the main applications and the debug tool.

Maybe. I run FOV at 0.9 but it isn't great to start with I've tried lower and it's really, really small. But each to thier own. Yes I suppose that will allow you run high res and cut them off at the sides. Still unsure why you would go modding DSC to run a headset it supports anyway (or using steamvr?) Always runs great for me as it is. Even on older hardware it was one of the benefits.

Yeah I know what super sampling is. My point was that you are running it at max res and then 0.1 extra on top this is really hard to do even on a big card. You will be much better off not running this high and you wont need so much compensation elsewhere. Sampling 0.1 of it a max res is a large increase as it's relative to the base resolution. Also yeah I know oculus supports open xr but you do not need to mod DCS to run it as DCS runs oculus natively which is the cleanest. I guess you want to use the toolkit, but again you likely only need this because you are slamming too many pixels at the card in the first place. It's just a bit misleading as the Q2 is very simple to set up on any machine.

So many variables. I'm surprised people see any gains using an open XR mod over the native support for the base oculus software. 2060 is going to be a difficult card to run a q2 on. I have a 3090 and it will not run full oculus resolution and 1.1 supersampling as you have done above. This is a massive amount of pixels and you are clearly compensating for this with a large reduction on FOV and low textures. I don't think there is much gain on the Q2 in supersampling once you are at max res anyway, there is a limit to what the screens are physically capable of.

Good example of how awesome the new flir is.