Search the Community

Hello dear pilot friends, I'm posting here because I think I've discovered a rather disturbing problem on the viper, I haven't found any other post mentioning this but this may be explained by the fact that if other people have a similar problem, they haven't been able to establish the origin. As the title indicates, these stutters occur when the altimeter radar is active, this is easily reproducible when I perform a dive or roll climb below 5000 feets. (See Track files) I was flying Hornet and recently switched to Viper, so I can't know if this problem appeared with an update or something in my computer configuration or if this is reproducible to other people. What I can say with almost complete certainty after having looked into the problem for several weeks and having tested almost every possibility of adjustment, is that the problem only occurs on the Viper among the other planes that I own (Hornet, Mirage 2000, F-15 FC3..etc) I first started by completely reducing my graphics options, tested different nvidia settings, tried different power plans, with and without HAGS, disable full screen optimization, disable core parking, add exclusions to windows defender, set high performance options in windows display settings, repair DCS, Clear all shaders caches, game and direct X, Disable hot plug, disable usb selective suspension but nothing was able to remove these stutters. After trying all these solutions I looked into the various electronic systems of the Viper and that's where I was able to understand that deactivating this simple switch solved the problem. With my current settings I was able to eliminate 98% of stutters for which I was able to determine an origin, 1% still remaining unexplained to me but only very rarely occur randomly and do not constitute a serious problem, remaining 1% that I can with certainty attribute to the ALT Radar of the F-16C. I can reproduce the problem on each map that I have, whether in a quick mission or via the mission editor, but my most convincing tests are taken from "Free Flight" on the Gulf map, you will be able to see by looking at the track that I release my load to go to cat 1 and give more agility to our bird.(Sorry if there were pedestrians down there) It would be interesting to know if other people are able to reproduce these jerks under the same conditions as me to determine if this problem deserves a correction from the devs or if unfortunately only my configuration is responsible. I'm certainly forgetting things to add so don't hesitate to let me know. Otherwise please excuse my English google translate but unfortunately this is my only way of communicating with you Despite its 5 years, my PC configuration with my settings still holds up quite well on DCS Configuration : Windows 10 22H2, Intel I7 10700K, Asus Z490-E, DDR4 32Gb (2x16Gb) G.skill Trident Z 3600Mhz, Rog Strix 3060Ti, Nvme SSD Samsung 970 Evo plus 1Tb, SSD Samsung 860 Pro 1tb, SSD Samsung 850 PRo 256gb, Asus PG279QM 240hz G-Sync, Hotas TM Warthog + Viper TQS Throttle. Nvidia Drivers and Panel settings : -566.03 (Old driver but which works very well for me (I am one of those who do not update if it is not broken especially since Nvidia missed the latest drivers) -Low latency mode: ultra -Power management mode : Prefer maximum performances -G-SYNC : ON -V-SYNC : Use 3d setting and OFF in game (Better for me on DCS) -Shaders cache size : 10GB (unlimited tested too without any changes) Windows Settings : -High power plan -Game Mode : ON ( tested OFF also ) -Game bar : OFF -Hags : OFF -Full Screen optimizations : Unchecked Among the attached elements you will find the comparison between Radar Alt On and OFF, I have also attached the use of my processors on msi afterburner because I suspected that radar alt led to a more intensive use of the cores when activated but by comparing this does not ultimately seem the case, the two seem similar... (?) Thank you for reading, I look forward to your feedback ! ViperStuttersRDRaltON.trk ViperStuttersRDRaltOFF.trk dcsRDR_ALT_ON.log dcsRDR_ALT_OFF.log DxDiag.txt

I have been testing a 3090 and a 6900xt in the last weeks on my rig - was running a water cooled 1080ti before (the system itself is an Asus Z390 Maximus Gene with an overclocked 9900K and 32GB kit of DDR4-3600 with very tight timings). I tested both a Rift S and a Reverb G2. During my testing I made the following observation: Either letting the GPUs doing their job in the out-of-the-box configuration or alternatively overclocking the GPU manually created in both cases a tendency towards stuttering and very pronounced frame time spiking for both vendors though the green team doing significantly better here. This was very surprising for me since I used the identical graphics settings I had for my 1080ti which didn’t show any stuttering. I expected those settings to be a piece of cake for the flag ships cards of team green and red. So I started to play around. Fixing the clock rate by a defined voltage (aka undervolting) on the 3090 eliminated all frame time spiking and stutters. On the 6900xt it helped a lot to prevent the GPU from using the out-of-the-box efficiency behaviour (which is very aggressive on RDNA 2) by forcing it to stay within a defined clock rate speed (when the CPU struggles with filling the draw call pipeline Big Navy seems to drop into a short power saving sleep). The difference to the out-of-the-box behaviour is basically one thing: The GPU doesn’t boost anymore. And the boosting process itself seems to be counterproductive in DCS VR. Looking back to my old GPU this somehow confirms my observation: My 1080ti had several manually optimised voltage curves which I made for specific applications and saved as profiles in afterburner. One curve was exclusively for DCS and it definitely never let the GPU go into boost. Since I don’t want to generalise my experience I would like to hear some more voices here. Anybody here with a similar experience? Since heavily overclocked and maxed out GPUs are not uncommon for VR users - anybody with stutters in VR (and an overclocked GPU) willing to try an undervolting approach and report his results?

I was flying about one day and had to go into the map. When I got back into cockpit view I had a lag spike that wouldn’t go away. So I quit the game and restarted my PC. I started to open the frame counter and saw my frame time went from 22 all the way up into the 90’s. My frames go down from 35-45 in each eye, down to 5-8 and you bet it makes it unplayable in VR. I noticed this about 6 months ago and it happens nearly every time I go into the F10 map, with few exceptions. I’m not sure what kind of track files you’d want to start with, but I sure could use some help squashing this bug.