Derfel75

Thanks for the reply, I already have the GPU scheduling off (same experience of yours), and I use OTT only to easely control FOV multiplier avoiding to put everytime figures in ODT. What I don't understand is why, when I use "half refresh ASW Off" everything in game starts to judder. For me have 36hz/fps and no ASW will be the best option everything should be smooth thanks to my system's average 65fps performance. I was wondering if my main monitor refresh (144hz) can affect in some way the ASW when I set "half refresh ASW Off". I think it's not a matter of OTT ageing as ODT is quite old as well and the former just act on ODT to apply settings. In the end from my point of view it seems to be a matter of synchronization between Q3 and DCS, but I dunno if there is some other "things" I'm not caring about and that are crucial to solve the issue.

Hi all, I'm using a Quest 3, link cable connected, together with OTT to play DCS with the following settings: SS in OTT = 1.7 Resolution in Meta app = 1.0 @72hz Bitrate = 850 Ingame PD =1.0 I've installed Mbucchia QVFR No AA, texture med, terrain low, shadows flat, clouds std, vis range med, LOD 0.4, grass 0, forest vis 100%, all the rest set to off. My PC specs are below into the segnature. In Syria into instant action free flight with F18, I have a smooth experience @72fps with some stutter now and then (which I can easely ignore). The experience become less pleasant with more stuttering (due to an fps fluctuation between 65 and 72 fps) for example with mission 1 of the single player campaign Operation Cerberus North (both when taxing to runway, and especially when fly over Adana city), or into F4's instant action cold start or free flight over big cities always over Syria. I know that there Is an OTT option to force half fps with ASW disabled (It should be something like "45fps-asw disabled"). So that I decided to disable Quad Views from DCS options and set Turbo mode = 0 in settings.cfg file of MBucchia QVFR in order tonavoid conflicts, and set 45fps-disabled by using the key bindings in OTT. The result is very strange: if I keep my gaze fixed forward the experience is very smooth, but when I look sideways or I roll the plane, everything become confusing, as if the frames are doubling for each object rendered. I tried to google for a solution, but It seems that nobody had my experience. It could be a bug of OTT? Maybe my monitor refresh rate interferes in some way with the Q3/OTT settings in cutting the frames to half? Is Better tò use VD instead of OTT? The same happens also of I set "45fps ASW enable" except that the experience get worse. Can anyone help me please to understand why It happens and how to solve? Thanks!!!

Thank you both for the precious advices. I'm not too worried to buy a platform nearly at the end of its commercial life, cause I generally update my system every 4/5 years. As howie said, I think that the engine is the real problem, but with MT introduction, after many years of waiting and tons of patience, we're almost there and the right machine upgrade can make the difference lighten our expectation. I will have a look at the AMD 7800x3D as suggested by Tiny Dancer (even if I'm more Intel oriented, but we must be flexible ) and decide if upgrade or wait 'till next year, hoping that meanwhile ED will make some additional progresses into engine improvement/development. I don' t understand if Vulkan development and implementation, can really be a game changer in terms of engine performances or not (especially in VR). Is anybody be so kind to briefly explain why Vulkan implementation seems to be so important? Thanks again

Hi all, apologize for asking, but I really need help...I'm trying to figure out how to improve my pc build for DCS VR purposes (mainly F18 and A10C modules). My current build is: - i7 9700k - MB Gigabyte Aorus Elite Z390 - DDR4 32GB 3200Mhz - RTX 3090 - SSD Samsung 860 EVO - HP Reverb G2 My settings: OpenXR - 100% of render scale - motion reprojection disabled DCS - 1.0 pixel density - VR graphic preset with the exception of DDI resolution set to 1024 everyframe With G2 set @60Hz (rather than play 90hz with motion reprojection activated I prefer to play 60hz without motion reprojection at all), everything run quite smoothly with all the single campaigns I've played 'till now (Serpent's head 1&2, Raven One). On a crowded super carrier deck, crowded airfield, or where there are many units on the battlefield, the game stutters quite a lot. Compare to the past, the recent intro of MT had helped a lot, but I would like to ask for some advice how I can improve my build to avoid stutters in crowded scenarios, enjoy MT as best as possible, and maybe move from 60hz to 90hz with more or less same graphic settings I have right now. I think that the bottleneck is the 9700k, do you think is worth to buy a used 11700k or is better to move on a more recent (but expensive) CPU like 13600k? Regarding the SSD, is worth to buy a more recent PCIe 3.0/4.0? Would it help to improve ingame performances and reducing stutters? Thanks a lot!!!!

Thanks a lot! I'm sure now it's going to work, infact I didn't change the format of coordinates!

Hi all, I'm in the middle of this very enjoyable campagn, but I have some troubles to hit the very last Hangar in Mission 5. After receiving the precise coordinates, I created a custom waypoint and combined it with TOO feature to slave my last JSow to this target. After I missed a first time, I tried again a couple of times missing It again for few meters During my last try, I noticed that after designeted as target my custom waypoint (by using the wpdsg ddi button), the coordinates of the JSow and the custom waypoint, don't match. My question Is: Is normal that coordinates don't match? Or where I'm doing wrong? Should I use JSow PP mode rather than TOO to complete this task?

Hi, is there any news for A10C II update? I haven't found nothing on Maple site on this regard (except for the Basic campaign released in 2021). Thanks!

@speed-of-heatthanks a lot for the precious hints, I'll try them and start my VR training again

Hi all, After numberous of test&try sessions, I found a combinations of graphical DCS settings that let me happy with my Reverb G2 (both in terms of visuals and fps counter, which is between 70 and 90 FPS depending on the scenery, with Motion Vector disabled). I thought that with the above fps values, after manually set an fps max limit of 60 through the DCS autoexec.cfg file (or graphics.lua, I tried both), the game should run smoothly in most of the cases, without any need to activate Motion Vector (which I don't like at all). Unfortunately I discovered that, after set the fps limit to 60, the game massively stutters. So I tried with another solution by reducing my G2 refresh rate to 60 (through Windows 10 dedicated settings) and without set any fps limit or change visual settings. The game runs smoothly at 60fps without stutters at all. I thought that the first logic of set an fps limit into DCS graphics configuration files, should work correctly, but there is something missing in my way of thinking likely. Of course reducing G2 refresh rate can be a solution but is quite annoing and my eyes gets easely tired. Could anybody help me to understand where I'm wrong and how to find a solution? Thanks!!