audiman

Same issue for me, using the thumb min-stick on the stick of an X56 Hotas. Tried using the mini-stick on the throttle and same issue occurs.

Also have this issue. Although it's not EVERY time, it normally happens on the ground when I press "Route 1 setup" after adding waypoints. It has crashed at this exact step many times. I also had it crash yesterday after shooting down an Mi-28 on Rotorheads with an APKWS. Got the BDA and DCS crashed to Desktop. I've had random DCS crashes in the Kiowa from either navigation menu stuff or just randomly flying and DCS crashing to desktop. the worst is when I fly 15-20 minutes to an area and shortly after I start to search for targets or engage them, DCS crashes to desktop. essentially wasting half an hour for nothing. Having said that, the Kiowa is by far the most fun module in DCS for me right now, aside from these game crashes lol

I'd also HIGHLY recommend the OH-58D Kiowa. It's like a very small and much simpler Apache, except it flies like an absolute DREAM compared to the Apache. I love the Apache, don't get me wrong, but Polychop absolutely knocked the Kiowa out of the park and the overall flight model, and ESPECIALLY specifically the AI Pilot, feel far superior to the Apache. I say that with no real life helicopter experience...so take it for what it is. But the Apache currently requires VERY smooth inputs and you basically need to be in a very stable/trimmed Hover before engaging Attitude hold. And even then, sometimes it will wander and float around(sometimes violently) for a few seconds before it stabilizes. Also if you use Altitude hold, make sure you do not move the collective at all, as it will sometimes disengage the hold mode even with the slightest drift of collective input from pushing buttons. This is my biggest problem, I have a Logitech X56 Hotas and the throttle(collective in this case) does not have enough friction to hold it still while I press buttons to operate various systems.

Same issue for me, though I'm on the Steam version. the past month or two it has been SUPER slow to get past the splash screen when first launching. It currently takes 2-4 minutes to launch to the menu which is outrageous. A year or so ago I found a thread mentioning that you could omit DCS from Windows Firewall and it would load faster, which I found to be true. DCS would load in under a minute normally. But now it's back to being SUPER slow to launch and I double checked the Windows Firewall settings too. DCS, for me, is on a 1TB NVME M.2 drive, a Samsung 980 Pro.

I have the same thing on my left and right monitors. I believe it is the outline of, what would be, the visor when it is down. Look in controls, search for the visor to find the keybind(RALT+F i think...), activate the visor, and you'll notice that those graphical marks on the left and right monitors roughly coincide with the edge of the visor. I'm sure it's just a small graphical error that will be patched.

+1

Do you happen to have pictures of how you mounted the MIP to the Track racer frame? And how you modified the seat for center stick? I have the TR120 frame(non-motion) with VRS DFP pedals and a VRS DFP Direct Drive wheelbase for sim racing, but have spent the majority of the last year using the rig for DCS... I think I can add some aluminum extrusion to the Wheelbase mount and clamp the MIP stuff to the extra extrusion. My HOTAS is currently side mounted and would have to cut out the center of the seat a bit. (i have the GT style seat with the surrounding headrests) The arm rest is the best additon ever to be honest

+1

One thing that was discussed is the potential of the GPU not having the required power. For reference, I have an Asus TUF Gaming OC RTX3080 and the Power Supply is a Corsair RM850. The GPU is given power via two separate 8-pin connectors/cables. I made sure to use two separate cables rather than the single cable with the extra 8-pin "splitter." Rest of the specs are in my signature for reference as well. Nothing super crazy

yes, when I set up the sim rig with the triples, I color calibrated all 3 monitors and made sure they all had identical settings with no power saving modes enabled. But that is a good thought.

Small update. I submitted a ticket. Troubleshooting still ongoing. It is not "fixed", per-say, but I think I have a workaround for now. To re-cap the ticket troubleshooting: I was asked to change the name of my Saved Games DCS folder to "Backup". Then to verify the integrity of the files (I'm on Steam). This created a new Saved Games DCS folder with completely default settings. As in no mods at all like SRS, all key binds were reset to default (don't freak out, your key binds are still in the original folder now called "Backup" under an input folder), default graphic settings (for me that is going from triple screens to a single screen). Then I was told to launch the game and try to recreate the issue. I simply bound the throttles and the stick Axis' so I could fly around. I flew around for 10-15 minutes at night in the pitch black and could not recreate the issue. I then changed one graphic setting by going back to triple screens and tried flying again. Immediately began having the darkness bug where I couldn't see anything which was a bummer. So, for me at least, if I want to fly at night I need to change back to a single screen as a work around. Granted, I didn't spend a ton of time flying in single screen to see if it still happened after extended periods of time, but changing back to triples makes the issue occur within a minute or two. So it seems like Single screen is more advantageous at night for me. Not the end of the world, just slightly less immersive. Also, several of my buddies who have experienced the same issue I'm describing play on single screens or in VR. So I have asked them to submit tickets with track files and log files for additional data as well. My ticket Rep has also asked if my friends have submitted tickets. Hoping to provide as much data as possible. Thanks again for all the input I've received on this post.

here is a track file. towards the end of the flight the screen went very dark and stayed that way for me. pitch black f18 darkness bug.trk

well damn...I assumed all tracks were saved automatically. I'll figure this stuff out eventually. thanks for the clarification. I'll try and get another track and post it, possibly this afternoon. Will be out of town this weekend starting tomorrow though.

Alright, so here is a short video I chopped together really quick. I took the track file that Flappie gave me and edited it to put me in an F-18C where I spend most of my time, and therefore notice it the most. I flew around for about 9 minutes and shortened the video to the most obvious clips of it occurring. Posted it on YouTube for troubleshooting purposes. For some reason I can't find MY track file for this flight though. Makes me feel dumb. but hopefully this is a better example for everyone. And before anyone says anything about it being G-lock, it is not. I just happened to be yanking and banking on a few of the examples because I was just flying around waiting for it to happen enough times. it happened at the start of the video when I was on Downwind for a practice landing, too close to the airfield but I digress... Thank you all for your comments so far

Ah, true, I'll do that.