MarcT-NL

Same problem here

Still.... WHY can we still input codes and fuse-settings on the MFD ?

From what I understand: The bombs only see the laser-code that was set while reamring. 1688 if you don't change it. Why we still have the option to change it in mid-flight on the screens, OR why we had the option working fine, while it was not the real thing, we'll never know...

Yeah, I had this too today. I don't do mods. I did a cleanup and repair. I was on a MP-server where they installed the dynamic spawning. DCS crashed 2 times before I could get airborne. When I eventually got airborne it crashed immediately after I armed the laser (I only use ATFLIR). Before I armed the laser, I set the code to 1555, which I always do.

I just measured 7.3 volt. I also measured that it's not the wiring, it's the controller that's not working. It being covered in glue and fabric doens't make it easier ! This is actually a good alternative. Still en few thousand percent of profit I think, but ok... Thanks.

Slowly all motors are dying from the JetPad . On the left, nothing works anymore. On the right one or two still work. Anybody knows of a solution for this ? If have looked into buying a new one, but 322 euro's plus taxes... that's rediculous.

Although the Apache works "fine" if you turn back most graphics, I do have the strong feeling that this model is graphically not optimized. When I jump into the cockpit, I see all layers build up one by one, layer over layer over layer.... seems extremely overdone. Just saying. Still Early Access, I know, but is there any work planned in that direction ?

I, and some other guys I fly with online, have the same problem. I never used any mods. Also: the other way around is also true. Fly in de FA-18 first, then switch to Apache and set your VID to TADS. Also crash.

Related topic:

Right. Luckyly I still had a button available on my stick. GFD, this will take some time getting used to !

Yeah, but this is still annoying if you have a 2-stage trigger, and you have Weapon release on the first detend and "Gun-trigger" on the second. Then you can't fire youtr AIM120's if there's a SAM painting you. This wasn't allways like this. Just since 1 or 2 updates...

I just bought the MAD campaign, but the INS is all over the place. I do a normal startup. At least I think I do.... I don't get flashing HUD or countdowns or so...

Don't forget axis's for the radio-volumes

Hi, The Ka-50 only has key-bindings to change the volume of the radio's. That's a pitty. Could we have a few axis's for this ? Is it even possible to create those axis's ourselves, by editing .lua-files maybe ? Because the volume-axis's are not my only wish... Regards, MarcT.

It is certainly a workable solution, but it totally conflicts with "Works as intended, num5 hardcoded to bla". Apparently it is NOT hardcoded. Getting fed up with reporting issues and just being dismissed. I'm glad there is a workaround. Especially in VR having a working numpad is essential.