SmirkingGerbil

Yeah. For me, like an entirely new game, amazing. I created the post, because I suspect some folks are just letting DCS OB update, not reading any instructions (I am sure that never happens here), and launching "old" DCS by default. I did it at least three times, just on muscle memory. Had to wait, finished the logon process, get to loading screen, exit, then go to my MT shortcut. It was an agonizing 3 minutes to kill off old DCS, and run amazing stunning new DCS. I am not discounting some folks are having issues, but end-user machines, home built rigs, even store bought are like a "Box of Chocolates". Folks may insist their machine is the most pure stable machine in the universe and it is all the code's issue. 30+ years of experience tends to put me in the 60/40 crowd. 60% user machine stuff, 40% Code update stuff. That 40% includes people not reading directions and launching the old DCS.exe.

Few things. I have seen an amazing increase in performance. Seeing folks here report none, to very little. All could be true - but. What I am not seeing consistently is WHAT environment? My earlier post, mentioned I was a Pancake. Some posts not clarifying whether Pancake or VR. Also, I am using a shortcut to the MT bin folder MT launcher . . . are other folks just launching the old standard binary? I think it would be helpful for folks to list VR/Pancake, Resolution, Basic hardware and core count and an explicit reference to "Yes, I am launching the MT DCS.exe from the MT folder!" IMHO

Pancake player here, most settings high, ultra clouds. Fired up an A-10 in a known good scenario with pre recorded FPS points, +25 FPS in cockpit (on 12 cores) and 35+ FPS gains in F2 view, on Syria Map, flying around Ramat David and around busy town geography, I mean street level looking at windows in buildings. Basically I went from 45 FPS in cockpit on ground, to 65. In the air, low level flying over towns and cities on Syria averaging 75 to 80 FPS. High altitude 90 to 100 FPS. Look AT THIS MT!! Fantastic job ED!!!

All the: "I skipped a day from work for this", "I made plans around this", "I was waiting for this, put things off for this". One plans their life around software updates for Beta Simulation/Gaming/Emulation software? This is a thing? Well, snatch me bald headed and call me Spanky!

Dunno how it became a Steam vs. DCS thing. I found and became a DCS fan (2011) because of Steam. I think Steam is important to DCS for marketing reach. However, after a few years I switched to full standalone DCS to better support ED/TFC. I am still a Steam customer, it does have a lot of advantages. Not sure why a line has to be drawn in the sand over the Steam vs. DCS F-15E drop. Sure, some things don't show up in one vs. the other, discounts etc. But Steam is a great platform, and works for those that wish to stay with it for DCS. Pure DCS clients have advantages also, but those are very specific to a certain type of mindset and player, of which I am one. Mainly, maximize profit for a my favorite developer, and run the client in as pure a state as possible, especially Beta. But, not a day goes by that I am not launching a game from my Steam portal. Many of which I would never have bothered with if it were not for Steam.

Thank you. I was going to link the EULA which CLEARLY States, not all 3rd party developers will participate (or are required to), in the MILES program. But then I backed out and deleted it. Why? What is the point, some folks just want to exist in a state of perpetual grievance. However, all that notwithstanding. The EULA (if anyone takes the time to read it) clearly states how/when MILES can be used, under what circumstances, and that not every module or developer will always get the MILES bonus or be required to participate in it.

Silver speaks at least two languages, English is not native. Silver also donates a TON of time informing the community of DCS development cycles and history. Me, I just take the time to figure out the context and syntax Silver is trying to convey. I consider this community fortunate to have Silver's contributions (for years), and since I only speak one language vs. at least two or more like Silver, I figure it is on me to work through the meaning. The least I can do for someone taking the time to update us (tirelessly for years), and trying to convey information to an audience that is not their native tongue. IMHO, YMMV.

I am just here for the First World Drama and Rage. Long time customer of DCS, since 2011 ish. Went through the Luthier WWII birds scandal, and DCS/TFC picked it up and saved it. Waited I think 5 years for the P-47D, going on six or seven for the ME-262 as an original backer of the project. Y'all just need to relax. The projects are exceedingly complex, and DCS is working with multiple partners now, so a lot more links in the chain. You want consistency, fly the other sims - you want beautiful technical recreations of iconic War Birds and other aircraft, buckle up, and become one with patience. Don't wanna hear the "I am a paying customer!!!" - we all are, we all paid the same amount (or will pay). Anyway, popcorn ready.

I am just here for the sheer amount of information, and work that went into this write up.

Takes practice. I know it can be frustrating as a close to the ground operator. Different approach than fasties that just boom and zoom from afar. When we fly as a flight of A-10's and get coords for a target, we always pull up short and wagon wheel to spot and identify all targets before attacking. Couple of problems though. Wagon Wheel works great, if you know what type of threats you face. If you have manpads or short range SHORADs like a Strela, 18,000 feet will keep you safe. The greater the threat range though, the higher you need to go, which creates all kinds of logistical issues. So the other approach is with a general idea of where the enemy is, to pull up short and zig zag outside of a medium threat range at about 5 to 15K feet, but if I was in a chopper, much lower would work. That way we bait the enemy to reveal what they have, but are far enough out we can evade. Dunno if the AH has a RWR like the A-10, but two A-10s working together can triangulate RWR threats pretty well. We will fly low enough we can terrain mask if a larger threat like a SA-11 lets loose on us, I imagine in a Chopper terrain masking and zig zag pattern approaches would allow you to get a fix on targets before committing?? Just some random thoughts. Or work with a flight of A-10's, as a chopper. We will do that in our group. A-10's will wagon wheel and use their TADs to identify targets and call out locations and types to the rotor guys. If things get spicy, then we engage also. Full on group working has fasties doing CAP/SEAD, A-10's working CAS and target identification and spotting, with the chopper fellas working ground targets. That way everyone is covering everyone else's weakness and allows each airframe to flex their strengths.

Every AH-D pilot in their new shiny Apache, that has armor and neat tech - learning the stark realities of CAS, and danger close missions against infantry fighting vehicles and whatnot sporting 20mm and 30mm auto cannons - just like A-10 pilots learned. Brrrt, and titanium tub don't help when a few 30 mm shells rip through your engines or wing surfaces. 2 miles is the min safe distance for mounted heavy machine guns and cannons.

Opppph, the best I can do is, do the research. Everyone's system is different, settings can vary. For instance, I now run the Reshade app, and it doesn't improve FPS, but it improves visual quality as a post processor, there are so many things you can do. Even certain maps can change all that. 32 GB of RAM should be fine, remember DCS trends in the direction of better performance via optimization over time, but overall, you do need to upgrade hardware at some point to keep pace. Try these links, there is no one size fits all. I spent a lot of time with trial and error, also google for updated articles on this topic:

Same, noticed it the other day, confirmed since then a couple of times. DSP brightness doesn't raise or lower MFCD brightness as it did in the past.

Thanks. Been here since it was just the KA-50. That is why I love this product "devs spilling over into the isle's . . . " is the antithesis of something built with passion, and a labor of love. Which is why I am here flying ED/TFC products. I might still whine every now and again, but I certainly don't want to see it stop. Keep doing what you do. When we get the radio, will just be all that much more agog over it.

Yup.

FWIW I read somewhere from a SME or other contributor that if you are going to be maneuvering hard, as you egress/ingress to a target, you should set to "INR Area" vs. "Point". I have a habit now of switching to "INR Area" in the TGP after a target run, and setting up an ingress/egress run when I know I will be nosing over hard, or banking hard to do a short turnaround to come back in on a target. Once the maneuver is done, TMS up short to switch from "Area" to "Point" - works really well. I only still have issues on a hard nose over to get pipper on a target, and my angle of attack is very steep, like 35 deg or higher steep.

Sorry on the Ninja! Was driving me nuts first day on Beta drop, I was everywhere asking for help! My handle is literally decades old, and has a long storied history.

@QuiGon Go to the bottom of this thread. Found the fix on the Discord Channel - SRS has their own Discord Channel. Started having issues from first day of OB update. MIC switch still doesn't move in DCS Beta, but this will allow SRS to function. "Allow SRS Hotkeys Always" or something like that, in pic at bottom of thread.

IAD's continuing development. Continuing development of RCS, radar modes, missile behavior, and functionality of ECM/EWR and Electronic warfare. A-10 radios please! ARC 210. A-10 HMCS Air to Air modes.

Yes, sorry forgot to mention Mission 1. Will try it with just the Mode 3/A setting. Still not clear on order of operations for Stdby to Norm. I think you flip Norm before take off on Transponder, but still not clear on when you select Stdby in which sequence of that cold start.

Which is purely my issue, bad hearing. I cannot tell, or having a hell of a time determining if I am setting the modes to M-3/A first, then to M-C? No problem with MODE 3/A code, that is clear. Plus not clear if I am setting the master mode dial to STBY before all that or during/after. Many thanks in advance.

Hey no worries, I am glad you found it! I should have updated here also. The fix is to "Allow SRS Hotkeys" so that SRS can interact with the cockpit even if the control bindings are jacked due to the Beta Update.

See above - "Allow SRS Hotkeys", you should be good.

Found the fix on SRS Discord server. Ciribob had solution. HOTAS MIC button still doesn't work, but I can comms again!!

This is the fix, found it on Discord server via @Ciribob. My MIC switch still doesn't work in cockpit, but my comms do and that is all that matters!!!