MarcT-NL

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...

Right. Formatted all drives Reinstalled W10 Updated everything Redownloaded DCS and all modules Tuned down the pre-load radius Turned grass off Textures to medium or low. Don't even know anymore. Set the Windows pagefile-size to 16 or 32Gb Set GEN3 in the BIOS Installed MemCleaner And now, in a final act of desperation I bought 320 euro's worth of memory to upgrade to 64Gb of RAM ! So do you think I did enough to get this to work ? Started the Marianna's mission for the AH-64, punched in all the freakin coordinates (why can't this be done in the mission editor ?), and I flew off. 5 minutes...BSOD. Mind you, this ONLY happens in the AH-64D and since the update of may-2022 also the Gazelle does this. I fly around hour after hour in the FA-18, P-51, F-5, Mosquito, and a few more. Also Huey, Ka-50 and Mi-8 are fine (before you think it is a chopper-problem). So in the local\temp-folder I found the LastMissionTrack. Download here if you want to have a look... http://www.marctelkamp.nl/LastMissionTrack.trk BTW: this doesn't happen always ! I have been CP/G on MP-servers for hours. Seems to work fine. I just don't get it.

BTW, this doesn't work in multi-player. There you always will be the pilot if you are alone.

Saying nothing about insanity, but I just tested it and it works fine by me in the Caucasus-map. What map and where are you testing it ? Maybe upload the mission too.

Thnanks very much. Since I don't really understand what this page-filesize does, is it better to set it to 16gb or to 32gb, in my case ? I have set it to 16 now. Let's try a bit of flying.

Oh yes, before y'all suggest it might be my PC. Well sure, that would be best case scenario actually, but why do I still have this problem with ONLY the Apache and Gazelle ? Are there simularities in their coding ? I fly hours and hours without any problem: FA-18 P-51 Ka-50 F-5 Mi-8 Mosquito A-10C-2 Huey In all maps. Supercarrier, Combined Arms, WW2-assets are installed.

I have never had memory-problems. That is, until the Apache came out. All other airframes work fine, but when I'm in the Apache, most of the time it end with a BSOD. I posted this in the Apache-bugs, and there was a bit of improvement, but it's still walking on eggs with this. Since the DCS-update of mid-may 2022, the Gazelle now has the same problem ! I get a BSOD after flying it for 15-30 minutes. SP or MP. So what's going on here ? 32GB should be enough to run DCS I hope ? Anybody else experiencing this ? Intel i7 8700k 3.7 Asus MAXIMUS X HERO-mb-ATX Intel Z370-chipset, socket 1151 32gb DDR4 (4x8gb) MSI GForce RTX 2080 Gaming X 8gb 500gb SSD for Windows + another 500GB SSD for DCS Powersupply 750W (usage is not higher than 500w) HP Reverb G2