nephilimborn

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!

I also experience these PimaxCL stutters and also feel it may be CPU bound headset tracking related (re-centering does not seem to make a difference). I have set the appropriate process priorities in PLasso (win10) and have set 120hz at 60capped. However have not tested turning off other CPU consuming upscaling such as DLSS/DLAA/QV. Will try tonight and see if that makes a difference. I even printed up some QRCode tracking sheets and placed these in front and on the sides - that i think was a waste of time and made no noticeable difference for me either.

ah, i must be doing something wrong or my DCS hardware/software environment must be an issue as, no matter what i tried, i could not get the TCS vid to show. Not a big deal as the RIO does the targeting and as such i was able to complete the missions.

The mission restart has always fixed this for me (VR + MT); however it can present an issue for a few missions in the Speed & Angels Campaign. This issue is that the last 6 missions start with an 'a' mission (intro to mission) and as such cannot restart the 'b' mission (or at least i don't know how to within the campaign). This means that you will not be able to view the camera which point tracks laser guided ground targets (ships in this case) or helps identify air targets, etc.

NOTE: This post is for humour purpose...understood that this is a DCS game engine issue and not a campaign bug. Was playing mission 15 and happened to gaze (VR) up and to my right...a new helo parking area?

There is what i think is a HB F-14 bug in VR that is only avoidable if you re-start a mission; the issue is that Television Camera Set (TCS) feed does not display. This issue with this mission is that you always start with 12a (intro to mission) and as such cannot restart 12b (or at least i don't know how to within the campaign). This means that you cannot view the camera which point tracks the targeted ship. I guess not a big deal as the LANTIRN pod digital overlay still displays and guides you to the target. BTW i love the 'jolly ranchers' bit - i used to buy those back in the late seventies from 7-Eleven when walking home from school - nice touch RefSim! Too bad that candy company got acquired by those a-holes at Hershey in the 90s

I was experiencing very similar A2A outcomes within this mission; i eat a missile every-time, usually after successfully defending against the first. I got pretty frustrated and decided to instead put the Flanker on the defensive first; crank hard left and launch sparrow early at around 15nm (guaranteed miss - although on another playthrough it did actually hit) whilst retaining at least 2000feet above the target, full afterburner and close the distance to no more than 3nm or before the flanker re-commits within LAR, launch both sidewinders staggered by a couple of seconds I repeated this 3 times successfully just to make sure it was not a fluke, worked on all three retries.

Took your advice and had another crack at this; with smart smoothing on and dlss 4 quality (preset j) this worked alot better - had alot of jitter before that was not related to cpu nor gpu frametimes. For me, this works really well with slower airframes like the AH-64D, however i still have a bit jitter present with high speed low to the ground such as with the F-14 and esp on the Syria map even with good frametimes. That being said, overall this is a much better experience than trying to chase a consistent 72hz. Thank you!

tangential to this topic; however i found this buildzoid vid interesting as it relates to both - still no shunt resistors on the 12V HP connector

recently the same for me...dcs seems to recognised and effectively use the appropriate resources e.g. 13th gen i7... 2025-01-29 12:56:05.712 INFO EDCORE (Main): common cores: {8, 9, 10, 11, 12, 13, 14, 15} 2025-01-29 12:56:05.712 INFO EDCORE (Main): render cores: {0, 1, 2, 3, 4, 5, 6, 7} 2025-01-29 12:56:05.712 INFO EDCORE (Main): IO cores: {16, 17, 18, 19, 20, 21, 22, 23} Although i still use PL to prioritise processes and unpark cores e.g.

Thank you @Panzerlang, 'high freq image jitter' perfectly describes what i am also experiencing

Hi, was wondering what negative experience you had with 120hz/half-frames? I ask as i have recently been try this setting for other reasons, noticed it eliminated the stutters i was experiencing on syria map + ah-64d however for some reason seems a blurry experience for me.

For a separate reason (BSOD) i recently have tried 120hz locked to 60 (no smoothing); it definitely removed the stuttering esp from 20degress+ left/right in ah-64d on the syria map, however it appears a bit blurry for some reason that i cannot technically explain. Normally i can achieve a fairly smooth experience with other airframes on the syria map, however not with the ah-64.

This week I began also experiencing pretty much the same issue as described in this thread ('the dreaded "DX device removed" error') along with windows BSOD bugchecks as analyzed by windebug below • 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred. • FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function • MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys Followed the advise here as well as updating to the latest Nvidia drivers (NVCleanstall). Sofar so good, however i also noticed much less crazy spikes (the resulted in BSOD-bugcheck) on mission load by also following your advice PP 120/half-frame-rate (although it seems as if moving terrain is now a bit blurry - might be me imagining that)