nephilimborn

similar setup, also use L/R buttons for differential brakes - once i unbound the parking brake control from any input, differential braking was more manageable

confirming that snap rotation does not seem to make it worse with my setup. i still get mico-stutters (looking left or right) with or without smoothing and no frame rate drops, however that seems to be separate vr issue i have with DCS. At the moment i seem to have a somewhat liveable experience with 120hz locked to half frame rate and smart smoothing turned off, XRNeckSafer snap turns configured. I have to use XRNeckSafer as it literally saves my neck (limited neck articulation as a result of previous injury)

i feel this is a simulation main thread performance issue with this module; its damage model and collision logic seems to be running wild for nearby objects (non-static map objects); introducing frametime cpu bottlenecks. My GPU is not stressed at all during these spikes, however the main thread pool is. The log file is littered with thousands of damage model info messages. F4U’s FM/damage? model seems to scale badly when nearby dynamic assets. [update] a few hours after i posted the above message i tried setting 'clutter' to zero in settings; this made a huge difference...i still have spikes here and there however it is at least now playable in VR now

@DrDetroit you are doing better than me at this (i am struggling with very similar challenges - too fast or too slow and uncontrolled yaw at the last few seconds); i am lucky to get 3 wire hooks in 50 tries. Many thanks for the advice @Saxman, looking forward to trying out these techniques and generally reducing the amount of extreme profanity i have been uttering lately.

Thank you @Mr_sukebe, i have previously leveraged this post in the past to assist with VR perf challenges and found it very helpful . I am pretty confident that i have all bases covered with my DCS environment and as such I am convinced this is a DCS module introduced behaviour. I can sim with this module as long i don't get near a map that has units (carrier based operations over the water only), for any other warbird scenarios i am back to the p47 as the performance spike stutters (every second) with the F4U is not workable.

Experiencing the same performance issues - also do not have these issues with the p47 over the same terrain, conditions, units etc. The canopy reflection helped alot - THANK YOU, however i still experience wild and frequent spikes when units are resolved near the F4U and over any map (excepting caucuses). The dcs log file has thousands of these entries and they seem to correspond to when the spikes occur 2025-08-04 15:22:38.030 WARNING LOG (11288): 1 duplicate message(s) skipped. 2025-08-04 15:22:38.030 INFO F4U_FlightModel (Main): Damage, element[98] : 1.000000 Later today will try the following and see if things improve disable_write_log = true in autoexec (if IO issue related) - probably unlikely? test with invincibility on (if damage system is triggering crazy unnecessary? or collision model artifact when F4U is near AI, certain terrain, or carrier, etc?) cockpit global Illum off (i think i already have that off but will check) [Update] None of the above made any difference...

Also not sure if this is beneficial for PCL; at the moment i just use the quality setting along with XRNeckSafer.

Many Thanks @Floyd1212 and @admiki; i should have first went to the live range and did some testing before creating this noise on the forums. I was having issues that i did not normally have; turns out this weird issue is contained to a BriefingRoom mission i had played before on the cold war map; have not experience this in any other mission since so all good

Has the conditions under which the pilot seat is able to fire on a FCR acquired target changed? I don't seem to be able to fire a radar guided missile on a FCR acquired target any longer.

this worked for me too however not during case 3 landings (ctd occurs)

same here

with all the nvidia driver issues over the past 4 months i have stayed with 566.36 and had no plans on upgrading anytime soon (4090), just use dlsswapper for the latest dlss dlls; curious as to what new issues are avoided by installing the latest driver?

Recently i have been experiencing a lot of immersion-breaking artefact-flickering happening in the PCL (120 locked to 60 w/ SSmothing, QViews set to Quality) when flying lower altitudes in the new Marianas WWII map as a result of wild performance spikes; i was only able to significantly reduce this by doing the opposite of what i posted; specifically setting DCS.exe affinity to all P-cores except Core 0 and excluding the E-Cores. I had noticed that core 0 (and core 2) as well as all the E Cores were running at 100% (the only way i could influence DCS to load up the other P-Cores was to exclude core 0) However no matter what i do i constantly get artefact flickering in PCL while not in game (main menu, mission editor, etc.); this does not happen in any other VR game. [EDIT] Smart Smoothing introduced INCREDIBLY immersion breaking visual artefacts if CPU or GPU starved - with the Marianas map load spikes this is incredibly jarring - i was able to partially minimise this with PLasso & LOD settings however it still happens too frequently. I have turned off SS as i feel it is an ASW implementation that is still not yet mature enough for such scenarios.

Same here - i spent weeks messing about with this and XRFrametools data - half frame rate in the pimax client was the ONLY option that minimised stutters

Many thanks for this Tom. I recently discovered your content on youtube (e.g. MAD campaign) - I am new to the AH-64 module and found your videos incredibly helpful, esp what tactics to employ in the different campaign missions. Great commentary and love the fact that you edit out the uneventful footage (e.g. travel to WPs). I was struggling with Boat Qualifications and came across this mission - this is exactly what i needed! Again, huge thank you for your youtube and training content!