YSIAD_RIP

I was flying around Syria all last night.. was really happy with the optimization and performance in the map. No stutter or lags when flying low between buildings.

@John Paesanoand @frostycab: Have you tried any of the Troubleshooting steps found on the first page of this thread? I had to use it once a year ago. See below for summary: Troubleshooting: -In the event the App's Config File is Corrupted, You Can Delete it by Deleting the Following Folder: /<Username>/Appdata/Local/Skate_Zilla_Graphics_Stud/ -In the Event the App Starts Up, but is off the Screen (Corrupted Position) Right Click The System Tray Icon fo SZGS Updater, Choose "Restore Application Window" Option

@TWC_Alamo upgrade if you can.. The new JetPads are really nice! I just got mine a few weeks ago and the fabric and quality is fantastic. Vibration is stronger than I expected too! Good luck.

Can you add a "Fictional" building that is Covid-19 related? That way we can bomb it and release our frustrations?

Crosswind certainly can be a very important factor. Don't forget about the rotational torque of the engine. For Example: Try flying straight and level at low RPM near 200 MPH. Slowly increase throttle and and see how plane starts to float to the left. Try the same by quickly increasing the throttle. (This probably explains why you don't want to be playing with the throttle when going in for a kill on a target. ) BUT: @burncpt since you mention it, maybe the Spitfire is pulling more to the left than it was last month.. Cheers.

Thanks for the quick reply @pet333r. I have tried deleting the shader cashes, fresh video driver installs and DCS full repair. So far the only thing that is consistent with good results is increasing the value of ExportScript.Config.ExportInterval I will try some other things and eventually install the better i7 Processor in hopes that it will help make a difference. Cheers.

Just played all the new sounds with VLC... Can't wait to download this weekend. I see the Mod moved over to WAV files and some crisper and more lively sounds. I even saw new seat height adjustment sounds -- lol nice!. Actually looking forward to see how the PlaneSpeedbrakeWind.wav file works because it is sitting outside of the Sounds\Effects\Aircrafts folder and I did not see a sdef file for it..

Yep.... already added my key-bind change to the new version of the default.lua Cheers and thanks @Particleman

Yes - look in the download file. ChangeLog_v1.0.1.txt

Hi @Taz1004, I have seen this behavior a few times with the latest Shader Mods: It even took 30 and up to 40 minutes on my poor 4 core i5-3570K.. lol. What I do when I know my system has to rebuild the shader cache is open up the fxo folder in saved games and watch the files being slowly added. At the same time I watch DCS YouTube Videos on my other monitor. \Saved Games\DCS.openbeta\fxo - As long as new files with current Date modified time stamps are being added I know DCS did not hang. Cheers.

Hello @Blueleaderand @pet333r: There is likely something more to this performance problem then the DCS UFC Export scripts. I was able to duplicate the performance and stuttering issues described. (Sadly) In summary: Last year, when upgrading from Windows 10 build version 1909, to 2004 I noticed DCS performance issues with FPS and stutter. I tired to trouble shoot a few things but backed out of the update because I was happy with the previous performance. Windows Build 1909 is end of life next month. I had little choice but to update to the latest Current OS Build 20H2. Before the update I have been running all versions of the DCS UFC scripts since last year with no performance problems. Other Observations: At the time of the Windows Updates my DCS Menu screens were running at 170 FPS or more. After updating to either Windows 10 2004 or 20H2 the FPS dropped to 64 FPS. (I am running Free-sync with no other framerate limiters used in the drivers and vsync is off in DCS) Frame drop at the DCS menu screens happened with or without DCS UFC or any other export scripts running. Try this: Today, as part of my trouble shooting I was able to get back most if not all of the performance and stutter free stability by changing the the export interval from 0.05 to 0.55. < Excerpt from : Saved Games\DCS.openbeta\Scripts\pw-def_script\Config.lua > -- Other ExportScript.Config.ExportInterval = 0.55 -- export every 0.05 seconds -trouble shooting- was 0.05 - trying 0.55 or higher was an improvement! ExportScript.Config.ExportLowTickInterval = 0.1 -- export every 0.x seconds For me this is just an interesting result because it tells me that DCS, Windows and my AMD Graphics driver are having trouble with the small workload created by exporting date every 0.05 seconds. Other Comments: I am only running a 4 Core i5-3570K on my DCS machine. Maybe when I get "un lazy" I will install my spare i7-3770K. Perhaps the extra 4 threads can help Windows and AMD provide better GPU performance. The best thing to do would be a Fresh Windows 10 Install of Windows 10 20H2 and DCS to see if the problem still exists. (This is not an option for me at this time) Windows 10 21H1 is due for release in May. Maybe that update will solve whatever internal issues have caused this problem since Windows Build 2004 for me. Maybe @pet333rcan make some changes to the lua or scripts than can work around the DCS and Windows problem. Cheers.

Have you tried reducing the resolution in the DCS Settings screen to something less than you primary display? For example I run DCS of of a 1440p Display. In the past if I selected 1920x1200 and deselected run in full Screen. I recall getting a window. I even remember doing an experiment where I ran DCS 2.5.6 and DCS 2.5 in windows side by side just to see if I could. Cheers

Fantastic.. good luck with the update - I will download and install for sure when it arrives.

V11 looks glorious! lol Thanks Sir!

WOW such a fantastic addition to DCS. The VNAO_T45 did not disappoint. Thanks team! If anyone is interested I managed to add an additional KEYBIND for the SpeedBrake. (It can be especially useful for anyone that has an X55/X56 Throttle and likes to use that Thumb Switch Slider for the SpeedBrake). I don't like to use the Logitech Provided software - if I can avoid it I will. All I did was make a backup of the original default.lua and add this extra line in the --- Throttle section of the lua. C:\Users\YOURNAME\Saved Games\DCS.openbeta\Mods\aircraft\VNAO_T45\Input\joystick Once all is working you will find an additional keybind in the Controls for the T45 named: " Speed Brake SLIDER Closed/Open " Sample of SpeedBrake binding code I added: {down = EFM_commands.SpeedBrakeSwitch, up = EFM_commands.SpeedBrakeSwitch, value_down = -1.0, value_up = 1.0, name = _('Speed Brake SLIDER Closed/Open'), category = _('Throttle Grip')}, -- for Slider Switch on X56/X55 or any 2 Position Switch |UP = Pressed & DOWN = Released| Thanks again VNAO team.

I just did a quick test using the "NEW T45". Similar to what was mentioned earlier for the M2000 vs MB-339 the following situation gave accurate feedback in the T45 for me. You may get similar results with other planes as well: For me: I loaded SimShaker for Aviators. I ran a mission that used the A-4E-C and Simshaker working as designed. Exit that mission or choose another slot if both planes are in same mission. Loading the T45 and you will see Simshaker for Aviators detect the Current aircraft: T45 as the A-4E-C using the Model: A-4E-C Module.. I even saw it detect as A-10C once.. Interesting.. Cheers.

Thanks to this handy FORUM and and a quick GOOGLE Search I am back in. I just ran a WINDOWS 10 Debloating script and it obviously changed the time without me noticing. Saved me from opening up a ticket and wasting ED's time.. Cheers.

You have a Hind? Brand new set of Textures? You cooking up something Barthek? This mod is a Caucasus Must have.. Thanks.

The original I-16 propeller was already very well done. An updated propeller using virtualization technology will just make the I-16 look even better. Thanks Plexus!

So far I am absolutely enjoying the latest 2.7 updates. I just installed 2.7.0.51180 this afternoon and performance is exactly where I expect it to be now. Initially, and in the all the past updates, I noticed 30% or more FPS drops stuttering and Crash to Desktop when starting missions after an update. I also noticed the same behavior when testing out some of the most popular VR and Custom Shader Mods. Some or most of my issues may have been caused by the "Potato" Core i5 3570K struggling to recreate FXO and Meta2 files after an update while at the same time trying to start a new mission. I have noticed that the FXO Pre-Compiled Shaders Folder could take up to 10 minutes and on a many occasions over 30 minutes to finish compiling when loading a map for the first time. Nothing I am writing here is new news and has been mentioned before many times, but I can't help but wonder how many strange stutters or issues are being caused by DCS letting a mission start while trying desperately to compile new Shaders in the background, not to mention any corruption or missing files that may result. I recently created 6 Pre-Compile Shaders Tracks using Instant Action Missions for each map. Going forward when updating DCS or testing Shader Mods I plan to Monitor the FXO folder and run the short replay tracks for each map before I starting stressing about performance impact and FPS loss. Happy Flying!

@firmekthanks for your latest update in 2.7. I have similar experiences and comments as @Hiob. I felt that FOV of 90 was the best compromise overall for me. However for some Warbirds I experimented with going as low as a FOV of 70. If I had a ULTRA ULTRA Wide or 3 Screen setup a 60 FOV would probably be outstanding. I recently tried one of the popular Race Car Simulators and not surprising the FOV Calculators recommend 55 to 60 degrees for my Resolution, Monitor Size and Distance to screen. Not really a surprise. Thanks again.. Cheers.

If the beautiful map makes it's early access debut in a "reasonably" optimized state consider it SOLD!

Thank you @f4l0 : I just got the excellent JetPad from Andre last week. DCS and Simshaker for Aviators was the first thing I tried. After 30 years of computer simulation and dead feeling feedback, this has been a nice change for me and DCS. I now have a new Hobby - "Tweaking and experimenting with the SimShaker for Aviator Settings on all the DCS Modules I own.. LOL I realize that everyone's chairs, motors and preferences are different. Since it is so easy to backup via the File Import Settings and Export Settings I would not mind seeing how others have their settings for the defaults and or various Planes and Helicopters. Is there a link or a part of this 139 page thread that I missed where I can see how you or others have experimented? I did find this helpful YouTube Video from YodaNZ Cheers.

I came back to DCS, after being away from it for over 5 years. The MB-339 was the first plane I learned to taxi take off and land consistently with. This 2nd Generation Italian Canadian, can't wait for the MB339 to be back in DCS where it belongs. - Sooner the better now that we have reached the 2.7 Clouds Milestone! I managed to update the Input Joystick default.lua to allow for my X-56 Thumb switch Slider to accurately Toggle Speed Brake On and Off. I hope the same trick works in the New MB-339 or that we will have a few different options for speed brake extend and retract. {down = iCommandPlaneAirBrake, up = iCommandPlaneAirBrake, name = _('Airbrake Slider OUT/IN'), category = _('Systems')}, -- Airbrake Slider Switch Mod Cheers.