obious

Any update on this at all?

Ha got it. Thanks

Overall, I have to agree with the sentiment here; perf with MT has definitely improved. In ST I’m getting a GPU frame time of around 8ms whereas in MT I’m getting 5/6ms (this is just a free flight mission in the PG map). I suggest deleting the original install and downloading a new copy. I will however say that I’m getting pretty evident microstutters in MT that aren’t present in the ST version. The only way around this is to use Turbo Mode but that has its own issues

Got it, thanks

Simply put, do I still need the --force_enable_VR --force_OpenXR switches for the desktop shortcut or can I do without them?

I’m not necessarily talking about increasing the amount of memory I have, just the speed

Given that we've had MT for a while now and most of the bugs people saw early on have been quasahed, I'm wondering if RAM speed still plays an important role in VR? I currenlty have 32GB of Corsiair Dominator RAM (CAS16, 3600Mhz) and given where RAM prices are at the moment, I wonder if it'll add much to my experience if I switch to a kit running at 4000Mhz (current limit of my mobo). Overall, my Quest Pro VR experience with multi-threading has been positive but I suffer from what only can be described as micro-stuttering from flying even simple quick start missions (NTTR F-18 Free Flight mission for example) and am trying to think of what hardware changes I can make to improve things (GPU frametimes are siting about the 5ms that mission). I'm already running Tubo Mode from the OpenXR Toolkit which has definitly helped but the seemingly random micro pauses are detracting from the overall experience andw enjoyment. Thanks

Is that the frame rate throttling setting? @mbucchia Does the OXRTK Companian App in-game pop up save the setting values to a file anywhere? I'd be great if I could change the settings via a file rather than the pop-up

Nope, I've checked under aircraft specific settings as well as under General

For the life of me, I'm unable to change the default cockpit FOV when playting in pancake/2D mode. I've changed the external FOV setting, has no effect. I've also changed the default snapview setting via RCTRL+NUM0 and it still doesn't take effect. Anyone else have this problem? Thanks

Where are you capping the frame rates?

Could possible be due to Turbo Mode being on? I had the same experience

+1

Can confirm that ED have done something to break this setting (shadows=5). All my settings are reverted to default if I open up the settings menu without touching anything.

Turbo mode is off Will try that Yes, the outline of a rectangle is what I mean. I've also tried the PG map and I can see it their also. Thanks

Ok, so after playing around with this for the past few hours I thought I'd provide my 2 cents. The performance improvement is immediately apparent. After runnning a simple NTTR F-18 free flight mission (with Broken Clouds 7 on Ultra, 2x MSAA) that struggled, the same mission becomes instantly playable. I'm finding it difficult to dial in my settings (to take account of the additional system resources I now have. Prior to DFR, I was seeing around 30% headroom being reported via the OTT HUD Performance view but when using DFR, that number jumps to 98%. I'm not entirely sure its accurate as after changing some settings to utilize the system headroom (MSAA now at 4x, render scalling in the OTT at 1.2), that 98% headroom figure doesn't really change. The only impact I see is that the Quest Pro I'm using drops down to 45PFS from 90FPS (which I rearly experienced before). After closing DCS and starting it again (to change an OTT setting etc), DCS hangs (white box; see attached image). Anyone else experienced this? Not sure if this is a DFR thing or not but the sound is very 'choppy'. I'm using an encode resolution of 3664 and an Encode Bitrate of 960 but I'm not entirely sure if these settings are correct? When using DFR, I notice what I can only describe as a 'box' that follows my line of sight/my eyes and is viewable only in the periphery (I'm assuming this is the 'fully' rendered image vs. the lower-res part of the quad-view). Its only noticible when looking at parts of the rendered image that span high brightness/contrast levels (like when I look back at the wings of my F-18 and I can see both the sea and the sky in the saame image. Not sure if I need to tune the settings.cfg here somewhat/somehow. Whilst the instructions are great and perfectly clear, I think using DFR with the Quest Pro may not be for everyone. I had to setup a Meta developer account (which required a credit card and home address) and toggle a bunch of settings deep in the bowls of the Oculus software.

I’m only asking as you mention it your change log but is DVF with the QP compatible with SteamVR, I thought it wasn’t?

Thanks for the replies all, will defo give it a go

Bump. Why disable it if it’s causing no harm?

I’ve skim read the 12ish pages of this thread but am at a loss as to whether or not there is a performance gain to be had for those with 4090 GPUs. is it only mid-tier/older gen cards that benefit from using DFR and mbucchia’s mod?

ED, please take note and allow the Ultra setting @BIGNEWY

I use Leo Bodnar interface boards so there’s no need for resistors/diodes etc except for the LEDs

Agreed on the high barrier to entry for OH

I remember reading a little while ago that one of the product features of the Supercarrier was the ability for players to take command of the ship (ie set course and heading, speed etc). Anyone know if it’s still planned?

So I think I’m finally getting around to finishing this project. Here’s the latest design changes, I’ve modelled as closely as I can based upon reference images.