mad.mad.mad

Here is the multiplayer track replay file of the issue: Thank you Persian_Foothold_v69d-20250219-113957.trk

I'm getting an issue on certain multiplayer servers where I'm unable to create new waypoints when loading in after a hot start. I know for sure it happens the Return Pre-Contact multiplayer servers, I think it has happened on others but don't have proof. This issue is not present in single player hot-start missions. Issue: When I go to create a new waypoint, the LSK 7R key that usually reads "?X" now reads "?-1" and I get the "CDU INPUT ERR" message when trying to create. I have not seen mention of this in the ED A-10CII or Chuck's Guide manuals, though I'm working my way through them again with a finer comb. INS is aligned and I've tried everything I can think of inside the CDU. All preloaded waypoints in both the flight plan and mission plan work. Creating markpoints also works as intended. I'm having zero navigation issues other than this. I have attached some screenshots showing the issue. I'm not sure if it has something to do with the new dynamic flightplan creation overlay that was introduced to DCS recently. I had another issue where my flight plan was not loaded into the CDU on hot-start but that seemed to be a one-time issue. nullnull

@BIGNEWY Is there any update on the Link16 incorporation with the A-10CII? This post is quite old. I'm hoping to finally see AWCACS declared contacts on our SADL/TAD/Scorpion. Thanks!

@Hawke81 Thanks for the tip! This seems to have sorted the issue - great catch! Apparently, I had opted into beta when I set up QuadViews. @Flappie Yes, rolling back the beta drivers seems to have solved the issue. Thanks for your help! Is there a way to disable VR if something like this happens again? It tries to launch DCS in VR whether I pick VR or Desktop in the new launcher.

Thank you for the reply! This unfortunately didn't solve the issue. Unsubscribe to beta drivers in the Oculus Desktop app? If I'm subscribed I didn't realise. Is there any way to roll back the drivers? I'm relatively new to Oculus. Searching it up right now. Thanks for the input!

Hi, DCS suddenly started crashing on start-up after rebooting my PC. Before that, I was having zero issues - I hadn't experienced any problems since the last update until now. I cannot get the game to launch. I only get the small NVIDIA & DCS splash screens before crash. It doesn't actually launch and start loading the blue progress bar. Windows 10 is updated. I have run the PowerShell cleanup and repairs. I also ran cleanup and repair through the new launcher for redundancy, though I doubt it's any different. Neither seems to find any issue. I have tried launching from the new launcher both in flat screen and VR. I have tried launching from bin in Windows Explorer without the launcher. I have no mods installed currently. I have cleared my FXO and metashader folders. I ran a cleanup and repair after clearing these out. DCS is updated, and I'm logged in and connected for authentication. I have some custom liveries and knee boards but none of these have ever caused an issue. They were working fine before the reboot today. I trialed and downloaded the Afghanistan terrain. I have not run the map yet and the game was running fine after downloading. DCS is allowed in Windows Defender I'm running "Check all files (slow)" repair now. Crash logs are attached - I am not sure which are required. I appreciate any input. Hardware Edit: Quest Pro via Link Cable Windows 10 Ryzen 7 7800X3D RTX 4090 64 GB DDR5 NVMe m.2 SSD I was prompted to update the Oculus desktop app but this was after the issue started. I updated thinking it could be the culprit but no joy on that front. Found this error in my crash log: "MSCTF.dll" Tried following the related topic listed in this troubleshooting guide. Have tried removing anything relating to voice recognition - windows, voice attack, srs, ect. But there are many files associated and I may have missed some. Edit 2: The check all files (slow) repair took all night but it seems to have fixed the issue. I'm going to reinstall voice attack and SRS, hopefully the issue doesn't replicate itself. dcs.20240716-043312.log dxdiag.txt dcs.20240716-043312.crash dcs.20240716-043312.dmp

I've been playing VR only for the last two years but recently wanted to start using head tracking again. I have a Grass Monkey IR puck with a PS3 Webcam. Whenever I load into DCS with OpenTrack running, I get double images. One stays still and the other tracks with the tracking software. It's a huge flickering mess. I remember I used to get this issue from time to time, and there was an easy fix, but I cannot remember what it was. Everything is tracking perfectly fine in the OpenTrack preview window and it looks like all view controls are correctly bound inside of DCS. I also get this issue in MSFS. I have not seen any mention of this as I searched around the web. Any ideas?

I've never purchased or installed the MB.339

I just downloaded this to try it out. The program crashes every time I try to create a custom kneeboard. Crashes to desktop, no error message or anything. Does anyone else have this issue?

So you're saying there are issues with the open beta update specifically in regards to playing in VR? Not that there are issues with SimShaker and VR after the update? Just want to make sure I understood your first comment correctly. I heard about the switch to OpenXR. I've already been using via OpenComposite so I'm hoping there won't be many issues for me. What dos "NIS" mean? I'm must be out of the loop. Thanks!

Dang, I play exclusively in VR. What are the known issues with VR and this software? I'm trying to make it through all 187 pages of this post but I'm not quite there yet.

Hi all. My transducers for my homemade sim shaker showed up yesterday and I just purchased a License for Andre's SimShaker Sound Module. I'm pretty new to this topic I did have a question though, is there any issues with the most recent beta Simshaker Sound Module and the DCS open beta update that Eagle Dynamics dropped yesterday? I'm sure there will be a lot of trouble shooting on my end in the coming days because I don't know anything about this software. Just wanted to check if updating DCS to 2.8.1.34667.2 was okay before setting everything up. Thanks.

I've been trying to learn the F-16 recently. I just spent 2 hours trying to figure out what I was doing wrong with the ILS system and why I couldn't manage to set up such a ridiculously simple task. It's frustrating the amount of bugs that have been know for years in DCS but never fixed. None of the videos I watched or documents I read mentioned this bug. ILS approaches are such a core fundamental of flight, especially in the military application. I feel like this bug should be a high priority.

Hey everyone. I'm not sure what happened. DCS used to run buttery smooth for me, now I'm getting huge stutters and freezes every couple minutes. DCS FPS counter says I'm in the 60-90FPS range depending on map and conditions but it will freeze up momentarily out of nowhere. Its making precision flying like A/A refueling pretty difficult. Is anyone else having issues? Recently updated to the current beta build. Not sure if this is the issue. 1440p at mostly high settings. This is happening in Single player, I haven't tried multiplayer. I lowered visible range and shadows but that didn't seem to help anything. i9-10850k RTX 3070 32GB DDR4 DCS loaded on its own NVMe M.2 SSD EDIT: Added a screenshot of my settings and the FPS counter. My FPS is good but my frametime seems insanely high?