dtpilot247

It's been reported but has it been remembered? Four years have passed, and many of the much more important things have now been implemented on the ED Viper since that time. I think it's fair to consider this a report of value now.

Hello, all. I have noticed that the landing gear speed on the Viper is very slow and has a couple of characteristics that are off about it. There are a couple of points that I would like to direct attention to through the video above. - This landing gear animation speed differs from even the animations shown in the landing gear video Eagle Dynamics posted pre-Viper release - The in-game door opening speed is roughly two times slower than that of the real Viper. Other videos can be located on YouTube for exact Block 50 comparisons if desired, but they have the same speed as those on the Block 20 MLUs shown in the video above. Example: https://youtu.be/XrmC864AqXU?t=86 - Upon retraction, the real Viper's landing gear system shows a sudden slow down of the mains movement about halfway through. This is where the wheels will lock/stop rotation. This is not just a ground/maintenance characteristic, as seen here during an aerial photography session: https://www.instagram.com/p/Crv7JL9goiK/ - In DCS, the Viper's main landing gear retracts much slower than the nose wheel. In real life, the main landing gear, including its doors, either retract at the same speed as the nose wheel or faster by roughly about 1/2 a second - The current speed of the in-game Viper's landing gear retraction as a whole seems to be comparable to the real jet, but if there was a force greater than +1G applied immediately after takeoff. If the same is applied to the in-game Viper, the gear retraction speed slows down even longer than shown in the video. No modifications have been made to my in-game Viper and recorded footage from current version 2.9.4.53990 are of a clean DCS installation.

So a friend of mine had helped out last night, and finally my DCS is running smooth. No more stutters/major hitches. He had noticed very high response times on the C drive when the game froze. What he recommended to me was two things: Disabling page files and changing the power plan. You would go to "This PC", right click anywhere in the white space below the displayed drives and hit properties, then go to the Advanced tab, Settings under Performance, go to the second Advanced tab, click Change under virtual memory, then bubble in "no paging file" and click Set and OK. Afterward, search "Power & Sleep" in the Windows search bar, open Additional Power Settings on the right, and change from Power Saver to High Performance. Here's the kicker. The second portion wasn't even present on the first install of Windows. I had checked this exact same location three times to make sure I wasn't going crazy while trying to fix the issue. The second time I installed Windows I hadn't checked but the third time, all of a sudden, it was there. Both reinstallations were booted from the same USB flash drive with all partitions wiped. Another friend of mine has recommended switching back on page files to see if it was only the power plan change to have affected the game. I will post an update on that momentarily. For now, it's safe to say that the game's been fixed. Thank you @peanuts0441, @AstonMartinDBS and others who had aided in trying to find a solution to this aggravating issue.

Disabled overclocking, still stutters. But I will try downclocking once I get the chance to. Just rolled back to the last one pushed out in 2022 and it has no effect.

I have followed your post step by step, I followed instructions on both WinAeroTweaker and Windows 10 Debloater. I have done three tests (current version multi-thread, single-thread, and roll back to 2.8.1.34667.2) to see if any of these things took effect. On a clean DCS install with a simple AI TF-51 orbiting over the Caucasus, the stutters are still happening. Now I really question why this game has this problem which all of my other games don't. This only started when I first installed DCS onto my new rig (parts noted in the first post.) I have played Falcon BMS, Microsoft FS, Squad, Insurgency Sandstorm and more, and not a single game has had this issue once. I guess the main goal is to simply stop that red "CPU Bound Main Thread" thing from popping up on the framerate counter but I'm dumbfounded as to how.

This unfortunately did not work for me.

I'm not seeing anything that is linear/frequent with the stutters. I can send you my log file if you would like to review it? I did find these lines during the seconds the game had stuttered: Would you think that any of these have direct linkage to them? Note: Before I ran this specific test, I have uninstalled GeForce Experience. I have also disabled NVIDIA Telemetry after the fact, as apparently that used to be an issue to some a while ago.

I have applied both and the stutters still happen. The stutters are continuing at the lower res and MSAA turned off.

Yes to the first part. Here is a recording of the disk activity. I do not see anything out of the ordinary. Also, for what it's worth, I do not have this problem on any other games. This seems to be something only specific to when I fly in DCS.

I recently tried logging into a multiplayer server (4YA Aerobatics Online US) to see if the behavior of stutters would change. They in fact grow in occurrence and I do not have to be flying for them to happen.

Unfortunately, that has not worked. Other methods I have tried are: disabling Windows power service, turning on Hardware-Accelerated GPU Scheduling, capping the FPS to 60 with both v-sync off and on through the NVIDIA Control Panel, enabling CPU auto-overclock through AMD Ryzen Master, and enabling the higher XMP-Profile in the MSI Click BIOS 5. I still get stutters on slow-repaired and non-mod DCS, regardless of aircraft or terrain.

Hello, everyone. This problem has been present since I moved to my new rig just yesterday. The game (both multi-thread and single-thread) seems to stutter for a fraction of a second at random intervals. This happens on all maps, in all aircraft that I own, usually anywhere around 2 to 20 seconds between each other. One way I can increase its occurrence is by maneuvering the aircraft. I have tried everything to my knowledge, with the help of a couple of other friends, to fix this issue, but to no avail. My graphics options are: My specs are: MSI B550-A Pro AM4 ATX Motherboard NVIDIA GeForce GTX 1080Ti 12GB GDDR5X AMD Ryzen 9 5900X 3.7GHz 12-Core Processor Corsair Vengeance LPX 64 GB (2 x 32 GB) DDR4-3200 CL16 Memory M.2 2TB SSD Corsair RM850X 850W 80+ Gold Power Supply I play with TrackIR on a flat screen with a 239.760Hz refresh rate. Attached is my dcs.log . All I did was spawn in, and after a few seconds, the game stuttered. Also attached is a regular speed and slow-motion recording of what one of these stutters looks like with the additional statistics. (This was done in MT, but does the exact same in ST) When it comes to solution methods, I have done everything from hardware stress tests, to BIOS updating, from repairing/cleaning out DCS, to following multiple video tutorials on how to optimize DCS through the NVIDIA Control Panel. So far, nothing has worked. Help would be much appreciated! dcs.log Framerate Spike Slow Motion Data.mp4 DCS Stutter.mp4

Almost forgot that the WARNING HUD symbology is missing as well. Good catch! Because of that, I'd like to add these video references because it goes hand in hand with the low speed tone and Betty WARNING sound. Hopefully it's not too late for these to be considered!

The Viper is missing Betty's "WARNING WARNING" part of the Low Speed tone/audible indication. From what I have observed, WARNING is said four times with a short pause between the second and third. It comes after eight beeps on the Low Speed Tone. Afterwards, the beeps continue until the aircraft is out of the parameters for it to sound. Here are three quick examples: Here is the tone in DCS:

This aircraft has been very fun to paint recently! I've been working on an old Thunderbirds livery used from 1953-1955 before they transitioned to the F-84F Thunderstreaks. It's been turning out quite alright so far!