Lace

As the title really - I assume wired connection and decent SSD, but what else helps? Do we still want a decent multi-core CPU? What about a GPU?

What are you regularly changing? I only change five numbers on program 1 & 2 during each startup, takes literally seconds while the INS is aligning. I set program 1 as anti ARH/BVR, and program 2 as a WVR anti IR dispense pattern. Sometimes I'll program 3 as a pre-emptive pop-up attack, longer duration pattern, but not always. Do you have optimised profiles for each specific threat? Quite interested in how others set it up.

I'm sure the long awaited DTC facility will offer this and more.

I will be replacing my Cougar. Not bothering with the panel as I fly VR, and I'm in the process of building more accurate panels for my pit anyway. £299 in the UK. Big selling points for me (above the Cougar) are the ICO/AB detents, and the additional couple of buttons for extra UI functionality.

Use a collective (or even throttle) with a 2-axis mini stick. That way you can use the mini-stick for the VIVIANE while maintaining helicopter control. It is also possible to fire the HOT3 on the move, so you don't actually need to hover. Run in, pop up, launch, maintain guidance, then break off the attack. Speed is life. No need for a second crew member or auto hover.

I'm really hoping there is a recce element to the dynamic campaign engine. It would be great if target information actually needed to be collected, rather than just presented.

I do a lot of my DCS flying when travelling overseas and use an XBox controller. With some clever mapping you can still do a lot of what is required even with a limited number of inputs. My approach is to not worry too much about the terminology used - this varies aircraft to aircraft, but the functionality is largely the same. Try to have as much commonality as you can between modules and it will help you remember what you need to press and when. For instance, all TGP have a zoom function, and designate/undesignate function. They will probably have polarity swap and other functions which are less commonly used - consider whether you actually need these mapped to the HOTAS. Try to keep it to the basic, essential functions only. Normally you'll need to fly through a few different scenarios to find out what you do actually need to use regularly via the HOTAS, and what you can setup prior to the merge/attack run. Use one modifier for non-aircraft functions, like changing views, zooming, etc, and keep it separate from the aircraft functions, and again, keep it common across all modules. Pre-made profiles mean you have to learn someone else's interpretation of the workflows and memorise their assignments. Develop your own and you will find them much easier to understand and recall when needed.

This is my CAS cheat sheet if it is any use to you.

Surely this question could be rephrased - "Did you grow up playing Falcon 3.0 or Strike Eagle II?" It's a tough one. If our Viper had the LANTIRN capability it would be a no-brainer, as I do like the TFR capability of the mud-hen, even if we don't have it available to us yet. The biggest negative for the mud hen is the two seat thing. I know it is possible to fly single-pilot, but I feel you do need a (human) back seater to get the best from it, and to operate it the way MD and the USAF intended. So at the moment, the Viper is slightly ahead.

I did not, thanks for point that out. I might give it a trial.

Happy Birthday

I'd go further and suggest a browser based stand-alone ME. Purely so I can sit at my desk at work mission building.

L-39 if you like ex-soviet avionics & instrumentation. C-101 if you prefer the western stuff. I have to say the L-39 module feels quite dated compared with the excellent MB-339. I don't have the C-101, but it is also 7-8 years old now.

I have created a spreadsheet which calculates TOT separation by inputting a dogleg offset to the attack run for a four-ship flight. You can play with the timings, desired final attack heading (relative). It may be of some use to some MP squadrons, so I thought I'd share it. Fill in the blue pen, read off the yellow boxes. Assumes turn away is +ve and turn back to target -ve. (doesn't matter if it is left or right). The example below shows a four ship splitting from the main attack axis at 30 second intervals and arriving over the target with 22 second and 30 degree separation. Attack Separation Geometry Calculator.xlsx

I use button 15 on the throttle (red front, LH pinkie). Seems like a fairly useless button on most modules, and easy to reach.

I don't think this is specific to the Gazelle, all module FMs are a bit fuzzy around the edges, as the data only exists within a defined performance envelope. I've said it before but realism is a two-way street, if you want the modules to behave in a realistic way, you need to operate them in a realistic way.

I have to say the FM changes have now knocked the Mi-8 off the top spot and the Gazelle is my favourite helicopter in DCS. Added to the fact I have learned the VIVIANE sight I'm now having a blast flying ultra-low level anti armour missions. Gotta love those HOT3 missiles. Well done @Polychop Simulations

Currently on 2.8.7.42718 and still not working in MT (not tried ST). I've tried mapping both L & R, just R, tried using modifiers with my controller, and using the in-built swap functions, and still can't get any control from the rear HCs. Front works just fine.

Just came on here to post the same. Everything mapped correctly for LH & RH WSO grips, but no function once in the sim. @falcon_120 Did you ever figure this out?

All of the above are correct. IAS is pitot static derived - what the instruments actually read CAS is IAS corrected for instrument errors - how fast the aircraft actually feels like it is flying TAS is CAS corrected for temperature/pressure and is the same as GS in zero winds conditions GS is the speed at which you are actually covering ground - useful for ensuring an accurate time-on-target At low level, there are lots of air molecules, so a fast indicated speed. As you get higher, your IAS/CAS will be lower, as the air is less dense, and there are fewer air molecules hitting the aircraft. The aircraft will feel 'mushy' even though you might be covering ground at a high speed. There are some online calculators is you google it, which can give you an understanding on how they are all related.

Here's a quick test. M2.1 for the Viper at FL450 ISA+0, M2.3 for the Mud Hen. Clean jets, full internal fuel. Tacview-20230709-093432-DCS-Vmax.zip.acmi

Go higher. I've seen over M2 in the F-16C & F-15E. Why did you pick FL360? Arbitrary or was there reasoning? What was the OAT? Also, you shouldn't need unlimited fuel, perhaps in DCS that does something funny to the gross weight? You will need to burn off that weight as you climb and accelerate, and probably run it down to nearly empty. Remember, as you said, these speeds are the very edge of the envelope and require everything to be perfectly optimised to reach. You will never see them in normal operations.

ZULU is standard for most ops. You could be coordinating with units outside the immediate area, or even within the AO. For example, Turkey is Z+2, Iraq Z+3, Iran Z+3.5. There is usually enough going on without wondering what time it is.

I didn't say it is the same, I said it is often the same - obviously it depends on local weather conditions, but it is generally within one or two mb of your departure field, because that is the pressure setting for that region. Over longer distances it can diverge further from your initial setting, but your final setting should again be quite close to your arrival QNH. I'm not sure where you fly, but in the UK we don't use quadrantals, it is a semi-circular rule for VFR deconfliction, with 000-179MTrack being odd+500, and 180-359 even+500. However, IME most people don't use it and compliance is not mandatory. I'm sure some readers might find this interesting, but we are drifting well away from the OP question now.

Yeah, it's in no way meant as a criticism, just my personal taste. We are obviously massively constrained by the game in ways we would not be in real life, and there is a need to cater to all types of players and their own expectations.