Nealius

Found the issue: Bastion Heliport also must be blue for the chocks to be removed. From observing AI and ATC behavior on Afghanistan map, there seems to be issues with the airbase/heliport combination where the AI, ATC, and now ground crew, cannot differentiate between the airbase and the heliport.

It used to. After the recent updates there's been an issue where one of them acts inverted but actually isn't. E.g. press right toe brake and everything works normally. Press left toe brake and DCS reads 100% on at first before snapping to actual input %. This is a major ergonomic issue with flight sim hardware, since pressing toe brakes on the pedal that's shifted aft is much more difficult than pressing those on the pedal that's shifted forward, and buttons don't give enough granularity for making turns.

In general I find custom flare programs on the Viper to be really effective. For me typically a burst of 3 flares with a salvo of 2 or 3 with half-second salvo spacing is good against everything from MANPADS to R-60s.

Same in VR and 2D. Switching to the Airboss view also causes such a massive stutter that while hosting MP, my jet warps up to 30 meters, catching on fire, and then going back to it's orignal position. Deck crew also vanish, reappearing one at a time over a course of a few minutes.

Works for me if the canopy is open, however the A-10C-II is the odd one out with this. F-16, for example, doesn't require the canopy to be open in order to communicate with ground chief.

There's usually a specific guns defense maneuver for situations like that, e.g. in the Tomcat it's to change your roll attitude to give the bandit a slimmer target to hit. If you're about to get gunned, you're most likely out of all the energy you need to exceed airframe G limits anyway.

Theoretically, you could slot into the Airboss role, set lighting as desired, then slot into an aircraft. The lights stay set as desired even after leaving the Airboss role, but since the mouse cursor doesn't work in VR I haven't been able to test if the light setting continues to be honored when a client aircraft is moving around.

Or fixing AI CASE I departures, or fixing CASE II comms in CASE III weather, or fixing multiplayer CASE III comms when aircraft are in the same group, or fixing CATCC getting clients' modexes mixed up, or fixing Tomcat delayed to start with 9 open spawn points in multiplayer, or giving us recovery window/turn into wind features in-house instead of having to rely on lua scripting...

I guess the heliports in DCS world need to redesign their taxiways. Everything is a tight 90. At this point I have better luck with hover taxis, but they didn't do that operationally, did they?

Did this from day 0 and it still refuses to taxi in the direction I want it. I can be turning, set the knob to center, and the turn continues at a faster pace instead of straightening out. I never turn the knob any further than 50% left or right.

Arrogant take.

Not sure why we need canopy open/ICS for chock removal when there are hand signals for chocks.

Strangely these commands don't work in replay tracks, though the station commands (1~6) do work.

For screenshots in this case, it would be better to use the track file. Open it in the mission editor, enable all the views, save, then replay the track. Now the external views are all unlocked.

Free trial would be the only thing letting me know if I would enjoy this more than the other helos I already have.

There's also less demand for WW2 because there is an already well established competitor that, while lacking in clickable cockpit and systems fidelity, has superior gameplay and damage model. DCS has no competitors for helos and post-WW2.

I experience this all the time, but in my own single player missions. Occasionally with other modules. Even mouse clicks on some switches do this. It's like DCS sometimes detects a single input twice in rapid succession. Drives me nuts.

Wait for the SEC light. It's often still on when RPM is stable at 20%.

Navy didn't fly Mustangs.

Was there anything done operationally to lighten them for the hot weather in Afghanistan? I've been building an Afghanistan sandbox mission and set the weather as close to current real weather as possible: 40C, 29.43 or thereabouts. At DCS Afghanistan's elevation that gives an actual mission temp of 33C, but my friends in their Kiowas can't get them off the ground without lowering the mission temp to the 20s or teens.

Residual heat from reentry; that was clearly implied. Reentry occurs at the Karman line, which is around about 300,000ft. At 50,000ft any heatshield glow is going to be residual. Which is besides the point of the claim that air resistance at 50,000ft would cause so much friction when, as pointed out above, a literal human being hurled himself from 128,000ft and didn't glow from friction caused by the air resistance at any point between 128,000ft and whenever he popped his chute (likely below 10k). You can even look at the shuttle's reentry profile. Maximum heating is marked at around 70km altitude, which is 230,000ft. The glowing plasma phase, and associated radio blackout, end at around 55km altitude; 180,000ft. By 50,000ft I'm not sure that it would even be glowing. Hot, yes. Glowing, perhaps not. Point is, the rebuttal about air resistance at 50,000ft is off by 130,000ft.

15-30ft initial holy <profanity>.

Overcast and Rain 3 is the closest thing to IMC we can get, but there are weird clear pockets that move with the wind. We need a true Overcast and Rain preset that is 100% IMC everywhere.

Can't speak for the rest, but 1,000ft initial would strictly be a Navy thing. USAAF fighters came over the field at treetop level for the break.

That's residual heat. The U-2 doesn't glow when it routinely cruises at 50k-70k. Felix Baumgartner didn't glow when he jumped from a balloon at 128,000ft.