Nealius

A few updates ago the way the jammer works changed and I haven't figured it out myself. Sometimes I can get it on and sometimes I can't. Previously it would work with the switch in any position 1-3 and CMDS knob in MAN, but now it seems to only work in SEMI or AUTO modes. I'm probably describing it poorly as I can't recall the switch names; my spatial memory focuses on where they are not what they're called

No idea. All I know is I had JTACs that I specifically had to adjust because trees were blocking their LOS when I first built the mission. I tested them all before the hotfixes, they all worked. I tested them after the hotfixes and they immediately called "no further tasking." Upon investigating in the ME, there was now a forest or orchard blocking their LOS that wasn't there during the pre-patch testing. Here's one from my older mission build where trees seem to have been added. The JTAC had a clear LOS to that target when I placed the units. The orchard to the southeast of the target wasn't there before. The trees to the east were there, but they didn't extend so far southwest as to interfere with LOS. In this one, I don't recall if the trees were there before, but I do recall playtesting this task and JTAC had no issues due to the 80+ft elevation over the target. Now for whatever reason these trees interfere with LOS, whereas before they did not. Barring new trees sprouting up, the only other reason I can think of is some JTAC logic change where it's targeting a different unit than it was before. Especially in the first pic, there's a narrow LOS window to a couple units in the middle that they could have been targeting instead.

I've had to do many dead-stick landings after a MANPADS hit shredded my fuel tanks. Insta-kills seem to be for anything larger than a MANPADS warhead.

Will the introduction of the Sniper XR remove the LITENING from the module entirely, or will we still be able to equip it to simulate non-US users like how we can simulate non-US Hornets with the option of LITENING as well?

I haven't been able to reproduce the crosswind, but I have seen similarly odd wind speed and direction shifts on the same approach. It seems like it happens when the 33ft and 6600ft winds are set to the same direction. If you set them 180 off from each other the wind direction/speed is more consistent.

Per -34, when auto-lasing the laser should automatically stop lasing 4 seconds after estimated impact time. In attached track you can see the laser continues to fire for up to 30 seconds after estimated impact time, only stopping when approaching the pod's masking area. The only way to stop the auto-lase is to cycle the laser switch off and on, which is not listed as a procedure item in the DCS F-16 manual for LGB employment. Other modules utilizing LITENING also have laser auto-off after x-seconds of estimated impact time. Looking at up to 2 years of YouTube tutorials, this seems to have been a long-standing issue. Perhaps it was just never added after the auto-lase feature was rolled out? Auto-lase-time.trk

Recent hotfixes added more trees to areas of the map; didn't see it mentioned in the changelogs. Any mission builders out there should double check your JTAC placement, as I had a couple whose LOS became interrupted by those new trees.

Both the airfield AND the heliport must be blue for the ground crew to work. Same at Kandahar. It seems to be an Afghanistan issue, since the ATC/AI traffic also has issues with the combined airfields and heliports. They're treated separately in the ME, but the ATC/AI treats them as one.

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.