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.

The picture is not very clear, but I know what you mean. This has been like that for years. It doesn't always do that though, so it's hard to reproduce. I only had that on MP-servers.

Remember, the AZ/EL also shows information from the datalink, not only your own radar. I'm not shure what they did in the Jan-25 update however. Now the AZ/EL only shows targets that are already locked by my own radar ! What use is that ? Ik have to investigate this further however. Maybe I'm doing something wrong. Or do you guys see this too ? -EDIT- Hmmm, seems alright afterall

Yeah, I finnished the mission now. I even forgot the NVG's so I couldn't see the sparkle. By pure luck I found the convoy so it went well. I do have voice attack, but without viacom

Ah yes. I found what I did wrong. I was holding over the island, circling in and out of the CAP-zone. So doing CAP over the city works. But then there is another issue.

Weird. I got a mission fail as soon as I started the CAP. I just arrived at WP2 and wanted to hold there until I was called in. Didn't say what I did wrong.

In the comms-menu

Got anything to say ?Say it. Don't be an ass

This is a very weird bug. Please believe me. Symptom: the aux (com2) channel-selector is randomly turning CCW. I only have this problem in this campaign. Never had it before. Not in singele player, not in multi player. Setup: The function is bound to 1 input only. So no keybind. It is bound to an Arduino Buttonbox. Most of the UFC is bound to this box, but only the Comm2ChannelSelectorCCW is affected. Everything else works fine. When I delete the bindings, the problem stops. So it is not a huge deal. I can still turn the knob with the mouse in VR. But could anyone come up with an explanation ?

It's still a bug, not a wish !

Thanks for your efforts Ramsay, but at the risk of jinxing it, I think I found the culprit. I have had a vague look in the BIOS. I don't realy understand all that, but I saw some numbers at places which looked like overclocking to me. So I set everything back to [AUTO]. Haven't had a problem since. I also noticed before that the GPU-temp went up to 85deg. celcius. That seemed a bit hot to me. This is now pretty stable at 70deg. My framerates have dropped a tiny bit, but I see less ghosting when I look sideways. So all in all very playable. Just one quick question though: As said before I bought and installed 2x 32GB of RAM. Probably unnessessary, but I'll keep it. This was RAM of 3600mHz. However, when I look in the taskmanager, ir says it's running at 2133mHz. Did I miss something ? I tried setting it to 3600 in the BIOS, but that resulted in a system-failure. PC doesn't start-up like that. So I turned that back to [AUTO] and it works fine, just too slow I think...