Lange_666

and i'll second that...

This time measured with FRAPS (couldn't get the FPS Min,Max, etc not to show on MSI Afterburner for some reason): On my settings: Stable 2.7.6: Frames: 5917 - Time: 60000ms - Avg: 98.617 - Min: 87 - Max: 108 OB 2.7.8: Frames: 5154 - Time: 60000ms - Avg: 85.900 - Min: 74 - Max: 93

Same here, running with impalor's settings copied over into my options.lua (i normally run a 2560x1440 screen) i still have the same performance difference between Stable 2.7.6 and OB 2.7.8. So with his settings on my monitor i now ran the test in sort of a small window. At first there was no difference but the FPS didn't fluctuated anymore, not even a little bit, 119FPS for both. Then it occurred to me that G-Sync played a roll and with the monitor refresh set to 120 Hz it was spot on that G-Sync played a limiting role, limiting the FPS in DCS to 119. Next step was to disable G-Sync and put the monitors refresh rate back to default which is 144 Hz (i set this to 120Hz because of TrackIR). When this was done, FPS could go unlimlited (above the clouds in Stable it hit 200 briefly). Result (don't look at the CPU 1-4 values, they jump up and down all the time): Stable 2.7.6 Open Beta 2.7.8

Just ran impalor's test track, played the Pause game. Results for me are the same as before, quite a drop in OB performance, both run from the same SSD. Shots +/- taken at the same moment, when the F-18 dives under the clouds and levels out on the coast line. But the difference is there throughout the entire track. Pancake mode. Stable 2.7.6 Open Beta 2.7.8 One thing: when running someone else's track, does it run with my settings or with the creators settings? If it runs with my settings, i would like to retest with impalor's settings but i can't find these (the google drive link doesn't show these or do i miss something?).

Is there a way to get TrackIR back to work after a re-scan of input devices? Otherwise a re-scan is useless if you need TrackIR working.

No it's not, it doesn't really matter where it's located. There should be no difference when located on HD or SSD (or NVMe for that matter). It will only load faster from SSD and that count also from stuff thats need to be sideloaded when a mission is already running (which is only minor). It should not have influence on overall FPS. There is also no need to run a very complex mission to see difference in FPS delivery, just fly around alone is more then enough (in that case there is no sideload at all...).

Full screen behavior changed since the 2.7 release: I'm still looking for a decent way to see if DCS is running Full Screen or Windows Borderless Mode. I can only tell the difference if i click anywhere on my second monitor and DCS minimizes. If i press Alt-Enter, the screen flickers briefly but i can't really tell if i'm on Full Screen or Borderless.

Spot on, just a little bit more now and the topic gets locked which in my opinion just proves our point.

That's a bit of bullshit. Loosing performance and then bring it back with multithread/Vulcan to end on the same level again as were we left off (if multithread/Vulcan will even deliver that "upgrade" which i personally don't believe). And would it bring that extra, just think of the gain if there was no loss to start with...

This bugs me since they changed the Full Screen behaviour a few patches ago. How on earth does one see the difference between real full screen and borderless (if real full screen even exist since then)?

Yup, straight impossible if you ask me which gives me the creepy feeling the loss in performance will stay. I even wonder who at ED's still runs anything older then 2.7.7 since that's the latest "stable" version already with the performance loss in it (compared to 2.7.6). I'll keep my stable at 2.7.6, won't upgrade to anything higher just to keep a reference.

This script is not for assigning keystrokes to various buttons but for assigning DX outputs to every button/switch/trigger combined with longpress and layer actions. If you want to generate keystrokes, the standard scripting (like in the TARGET manual) is what you are looking for. If you want more then 32 DX outputs available on a combined device (when a script runs it combines throttle and stick into one single device) you need to look for the standard 120DX file which replaces the default target.tmh file and start from there (the tmh files are not for editing in general, you should create/write a script with a tmc extention, not tmh, at least for starters). Also, since you are trying to generate keyboard outputs I might be wrong but I don't think you understand what DX outputs are. targetdx120.tmh

Quick Q: 240 or 360 AIO, what are these numbers referring to?

My data (shots and requested files) is in the original thread, i see no need to repeat it again in another individual thread.

OTT user here. ODT comes with chinese (read not understandable) settings like: - Pixels per display pixel override... - Force Mipmap Generation on all layers... - Offset Mipmap Bias on all layers... - Pose Injection... - etc....

Same problem here. And it's also happening in MSFS. Getting the • (an arrow in MSFS) to move over the overlay to press a button or something can be trial and error. For the comms menu, moving the • off screen to the right at the menu location and then back helps.

Never been an issue here with any of my controllers (currently a TM Warthog). The only device that turns windows back on after putting it to sleep or even turning it back on is my Garmin Edge 810 cycling computer when hooked up on USB.

I delivered the requested files and posted some comparison screenshots so that should be enough from my side. I didn't notice a problem at first since i cap my FPS and on 2.7.7 it didn't go below that capped value so there was nothing negative to see. After uncapping the FPS, the difference is what i posted. I'll keep stable at 2.7.6.13436 as a reference because once updated, there is nothing to compare anymore.

According to Spooky over at the BuddySpike Discord the difference comes from a cold start at an airport and a hot start on a road base. From Spooky: Because they start hot started which includes the procedure of adding 5 degrees of nose up trim. You have to trim it back down after gear and flaps up. So that's sorted.

Report: Flew with various aircraft (F-16C etc....) + the UH-1H (i don't have the Hind): Take-off from Boulder City and overflew the coördinates given, no crash, not in any module. Ran the track provided by Avernus in the first post, DCS installed Mi-24P module before running because that was missing to run the track. Track runs fine, tried a few times, track plays through to the end and asks then to "refly", no crash at all.

Left-CTRL + Pause works fine here.

Same here, no improvement at all.

Pointing out to an introduced problem (which you also encountered) is not really dogpiling. You just changed settings "outside" DCS to get it back to an enjoyable level. I don't call that a solution, just some sort of workaround to get you playing again (which is OK for the time being, just don't let loose of the rope, because you'll loose in the end if you do).

Did you do the same with 2.7.6 to see if you wouldn't gain any extra also there? I already had the feeling Marianas got some optimalisation because i used this map as first test after upgrading to 2.7.7.14727 and it ran smoother then on the previous build. So i then thought... nice upgrade, even more so because i ran it with a capped FPS. I removed the FPS cap after reading this topic only to notice that the other maps took quite a dive, compared to 2.7.6.