Smashy

@MAXsenna it's at the UI layer so it's pretty slick. Set in once and use it everywhere. Like the F-keys, these command menu binds will also take precedence when the command menu is open so you don't have to worry about clobbering any existing binds or dedicating specific hat/buttons for comms.

Fingers crossed the patch scheduled for today (Aug 9) will unbreak C-Scope. edit - got to check out the patch and yay, C-Scope is back! Also, RMAP is pretty cool. Nice job guys.

Well, I appreciate your insight and think the majority of people here do as well. While I get the frustration and wouldn't blame you for bailing, I hope you stick around. It's pretty awesome how a few people can ruin a good thing for everyone else.

Getting the same along with Afghanistan. Is Crowdstrike down again LOL. Come on, ED get it together.

If you're still looking for more info, crack the manual open that ships with the module and search for "MTT".

Macrium is awesome. I used it for my last upgrade too. If you're paranoid like me, I'd suggest creating an image and putting it on an external or to-be-disconnected internal drive before the clone. That way if anything goes wrong, you'll have a copy of your C drive to revert from. Hardware is replaceable, data isn't. If there's a way to <profanity> things up, I'd find a way.

Use the CP/G George AI and constantly command him to sweep the area around you. He's inhumanly good at picking out infantry from a distance.

I change graphic settings outside the game multiple times a day to switch between my desktop monitor (edit/create missions) and my simpit TV (play the game). I've automated this with a simple script. Once the kinks have been worked out of the new launcher, I'll start using that feature there.

I'm getting something very similar with missions generated by Digital Crew Chief and Briefing Room. I was able to reproduce it using Apache/Hellfire (SAL and RF) and Hornet/Maverick (IR and laser). I found a message in the BF Discord that suggests the fix is on ED's side of things. https://discord.com/channels/809863694678491157/809863695198453812/1262677003417681951 Hopefully the issue can be identified and fixed sometime soon.

Not exactly your issue but posting in case it'll help in any way... I completely rebuilt my rig and added a TCL TV (144Hz, Freesync) and 3 WinWing MFDs and fought with some pretty bad stuttering for awhile. I'm no display expert but I think the problem was caused by the different refresh rates of my displays. I learned that the WW MFDs default to 60Hz with the DisplayLink software and there's no way to change that. After hours of trial and error, I found a method that got rid of that awful stutter. 1. Turn off all displays. The MFDs are connected to a USB hub that has switches for each port so this is easy. 2. Turn on TV, wait for Windows desktop to be displayed. 3. Power all 3 MFDs on. Make sure Windows recognizes all displays, then start DCS. That does the trick every time for me. I'm not at the pit r/n so I don't know if Freesync is still enabled but those horrible frametime spikes disappeared using these 3 steps so whatever. I'm also not using SimApp to manage the displays, I just manually created a multimonitor LUA instead.

Thanks @AdrianL. I did do a brief search before posting but failed to see that thread.

Has anyone else notice the launcher enabling the "easy communications" option despite disabling this during the last session? Similarly, the option to "hide stick" always gets disabled when using the launcher. Disabling the launcher makes both of these options stick for me.

Good find @Grindmetal. Bumping from 1000Hz to 500Hz worked for me too.

When using the mouse for anything in a 3D context (in game, ME loadout page, encyclopedia), I notice that frame rate will tank to about 30% of normal with huge spikes in frame time. For anyone curious, try this. Hop into the game, open the in-game FPS counter and move the mouse around. If it's not happening to anyone else, maybe it's me. The only change to my system or DCS was today's patch. I can try to capture a video if needed, I don't think a trackfile will capture the problem. Edit - it happens all the time, not just when 3D elements are on the screen. For example, frame rate and frame time spikes occur with mouse movement on the main menu; it's not noticeable to the eye.

Today's patch (2.9.6.57650) notes indicate "ACQ Bump" in the Hornet has been added. I haven't had a chance to check this out yet.

Holy <profanity> that was fast. I was just looking at the Data.lua changes and figured I'd look here to see if anyone noticed the discrepancies yet. Thanks @Quaggles!

I can clearly see the stutter in the rotor animation. You could try capturing a video with the framerate counter open and expanded. Hopefully the stutters will show as frametime spikes in the counter window and show folks what to look for. FWIW, I'm not seeing anything like this on my system and I've been spending a ton of time with the Apache the last few months. Weird problem for sure, hope you get it sorted.

I excluded my DCS folder from Windows native antivirus and first load of the day was quick and painless. Yay!

Firewall or antivirus?

Same here. Also, @freehand why exclude the entire drive? Seems like overkill.

Same thing here. Taking a look at the log as the first load of the day is happening, my system seems to get hung up trying to do the following: 2024-07-03 12:32:00.615 INFO SOUND (Main): Added sound path: ./CoreMods/aircraft/F-4E/Sounds 2024-07-03 12:32:00.700 INFO SOUND (Main): Added sound path: ./CoreMods/aircraft/F14/Sounds 2024-07-03 12:32:01.596 INFO SOUND (Main): Added sound path: ./Mods/aircraft/F-4E/Sounds 2024-07-03 12:32:02.765 INFO SOUND (Main): Added sound path: ./Mods/aircraft/F14/Sounds The timestamps of these logfile entries don't reflect the wallclock time that passes between each log file entry write time. It takes over 30 seconds to write the F14 entry after the F-4E entry has been recorded. The directories are larger than other modules but nothing crazy, esp in the CoreMods dirs. I'm not sure if this is the cause or it's just me.

lmao...thought so

I'm not following your thinking. Why is it bad? Whether you pre order or buy it the second it is available, you get it at the exact same time, late or not. Delays impact everyone whether they pre-order or not. The only difference is you get a bigger discount when you pre order.

Will the manual be updated along with the module? I'm one of those weirdos that like to read the manuals cover-to-cover and it can be confusing when things don't work in the sim as they're described in the manual.