NeMoGas

Now with 2.9 when using binoculars in a ground unit you can no longer steer, accelerate or brake. Before you could still drive the tank as if you were the commander issuing commands.

I have had the modifiers disappear for me also. What I do to avoid this is click rescan and then click cancel (the rescan will still happen). If you click on ok it will save the controls and sometimes it saves them without your modifiers or completely unbound.

Cargo view no longer works for me as well

Np, thanks for the advice.

The only issue is, it's mounted outside the aircraft on the tail

This bug happens to me all the time with all modules. It seems to be caused by my joystick or pedals (both VirPil) however I know others who have had this issue with other brands of hardware. The quick fix for me is to unplug either of those 2 peripherals after I boot the game up if I experience this and need to change keybinds. Obviously if the control you want to change is the one causing the issues you're kinda SOL. No other game has ever had this issue so I would assume it's a DCS bug and not an issue with my peripherals. Also if you notice it start to bog down when you open the controls menu immediately click cancel and if you are fast enough you can back out before it fully locks up. I have also noticed if you can switch to the axis assignment section from the drop down fast enough it seems to also not freeze. Perhaps there is some bug when on the default "all but axis" page in the controls menu.

Wipers on the Hind remove rain.

The laser in MP updates at a very slow rate. This is not just an Apache issue, it's an issue when buddy lasing in anything. Me and another player have tested this a lot and even when lasing from an A10 for an Apache the laser skips around and does not smoothly track the target. This is visible if the player in the A10 has both the designator and IR pointer on at the same time and the Apache pilot is under NVGs. Videos and tracks were provided to the appropriate people as far as I know.

+1 Immersion ruined!

Thanks I will have to see about using that instead of joy2key. I would still love to see this as a native option in DCS though.

I would like to request the option to assign the triggers on the left and right handgrips to be assignable to an axis such as the triggers on an Xbox controller. If we could have this option it would remove the requirement to run a 3rd party program like joy2key. This would also allow both the first and second stage detents to be used without the strange behavior you see in joy2key when you release and it fires the first detent again shooting another missile. This request was already asked for but that thread seems to have disappeared and searching through all my previous posts did not find it. Thanks

Nothing, I usually have SRS up and am also in a discord voice chat. I don't use a microphone so text is how I communicate with my team and crew. Sometimes I'll throw a little robot voice in there to spice it up but text chat is more convenient for me.

In multiplayer we can already select from "all" chat or "allies" chat when we open the chat window. I would like to request a third option for use when playing in multicrew aircraft with a friend. This could perhaps be labeled "Crew" and maybe the text chat would appear green or something along those lines. This way when I'm using the text chat channel I'm not clogging up my teams text chat box. Not a super important thing but one that would be a nice quality of life thing for me and others who use text chat in MC often. Thanks for your consideration.

Cycle the MAWS power switch to off and then either all the way to bit and then on or just back to on once your CPG joins. Once you do this they will hear the MAWS sounds. This is part of the startup that me and my friend do to fix the desync and it works every time. You will even hear and see some radar missiles on the ASE such as 120C but you still won't see any emitters other than AI baked into the mission like E2 or E3. Any dynamically spawned radars and of course player aircraft will still only be seen by the Pilot.

One way to possibly see if this is the issue is to have a friend in something like an A10 lase a moving target at night. Have that player set the TPOD to both so it shoots a designator and IR pointer. Then you can observe their laser under NVGs and see how well it tracks. As far as does the lase pass through a unit, well when the unit is static it certainly does not. I have lased tanks and such silhouetted on a ridge aiming at the hull or turret area and still get valid laser ranges and impacts. You can also set the ACQ to seeker in the Apache and have a friend buddy lase a moving target and the cross indicating where the seeker is looking will also jump around as if the update rate of the laser is lower and not smoothly tracking.

It might be a global DCS issue with off board lasers and moving targets. After having a player flown A10 lase a moving target the Hellfires still miss. We also lased a moving target with the Apache and had the A10 shoot a laser mav at it and it also missed. It seems like other clients lasers only update at a much lower rate compared to your own which is why when you have the cross hairs over the target the missile lands beyond and also somewhat behind the moving vehicle. I assume this is an issue in the Apache because each cockpit is treated like a separate client? Not sure just a guess. This might also be why IAT was pushed back because ED realized this and has to fix that before they can give us IAT, also just a guess.

I always only seem to get E2 or E3 and in some servers with AI fighters I have seen those a few times also. I basically never see other real player radars, and this is when I am a client.

So when I test this in my game the VCR and ADF knobs can indeed be pulled out and pushed in. Knobs that have this functionality can't be mouse clicked and dragged. None of the top comm panel radio volume knobs can be mouse clicked and dragged for me either because they instead are pulled with right click and pushed back in with left click. Perhaps ED can do something to make these switch types function with click and drag but this is currently how these work.

Can't these knobs be pulled and pushed with right and left click? You can't drag the ones that can because the right click pulls and the left click pushes.

No the laser stops at 9999m, that is the issue.

Yeah it was fixed in the sense that a mission made in the ME with all SAMs pre loaded would no longer appear on MFDs or ABRIS (at least back when I tested it after the initial fix). However in a server that uses triggers or scripts to load units into a mission dynamically the option does not work even when the flag for hidden on MFD is on. Now that the Apache has threat rings and preloads radar equipped SAMS we get 8+ wonderful pages of targets automatically preloaded into the coords page on DDCS just like the KA50. Well maybe not quite as OP as the KA50. The KA50 will show not only SAMS or AAA systems with radars like the Apache but it will also show MANPADS, Avengers, Linebackers, ZU23 equipped vehicles like the new technicals or any other non radar system. The only one I noticed that didn't appear on ABRIS is the Flak 88 so I guess that is the defacto KA50 killer. This is a bigger issue than just knowing where the enemy anti aircraft systems are, it also allows you to find hidden convoys if someone built anti aircraft units to defend that convoy. You can just use the ABRIS cursor and info button to get the exact location of any (except the Flak 88) anti aircraft unit and then send a JSOW or SLAM-ER at it, or give the coords to a friend for termination. Basically there is no need for reconnaissance in these PVP servers anymore, just hop in a KA50 for like 5 minutes and turn the ABRIS on.

It would be nice to be able to designate for someones else's weapons or LST outside of the 9999m software limit.

Do you mean the dcs.log-long-number.zip? looks like I have 2 of those from around the time of the crash.

Selecting a coord as ACQ source sometimes immediately crashes the game. I have had this happen several times over the last few days and twice tonight. The first time it happened tonight I had used the TADS to mark a point on the ground as T01 while in another players Apache. The intent was to shoot at a target marked by JTAC smoke and a laser so I dropped the target point on the smoke and set the Hellfire to Hi LOAL. Then the second I went to the coords page and selected T01 as my ACQ source the game locked up and eventually crashed. The second time I had this happen tonight was about 10 minutes ago. I was in a solo Apache landed on the ground. I got a friendly MGRS grid and entered it into the aircraft via the point page. I then setup the Hellfire for a Hi LOAL shot since my friend was going to lase the target for me. Again the very second I went to the coords page and selected the point as my ACQ source the game crashed. Unfortunately I don't have a track file for this as both times it was well past an hour into a multiplayer session and tracks never survive missions this long or full of units (I actually disable track writing when in MP to save HDD space).

Yeah this option does not sync between the 2 cockpits which is very unfortunate since it also likes to turn itself on when in MC automatically. Trying to untick this option for your pilot as he attempts to regain control is useless and only causes a desync between the two cockpits.