sleighzy

OpenKneeboard covers the majority of the use cases so all good there. The one in particular which was raised externally was the Vaicom kneeboard page however. This uses a bunch of lua code, although is displayed as another tab within the standard kneeboard, so not static content. Don't think OpenKneeboard handles that one unfortunately. I'll do some further testing around that one.

Attach your DCS log file in case it highlights any issues. I'd also recommend using https://github.com/fredemmott/XRFrameTools vs. fpsVR to test this out. You can export the results to a CSV file and then for the frame timings it will show other things happening at the same time which may identify the cause of the increase in those.

You referring to using the Custom option for example in the PimaxPlay software? Have you tried the solution posted here, a lot of people prefer Mbucchia's Quad-Views-Foveated, and using Tallymouse companion app to configure the multipliers and focal areas. Note that you don't have to switch to using Mbucchia's Pimax OpenXR runtime for this and can continue to use PimaxPlay as the runtime, just ensure you disable Quad Views in PimaxPlay if doing so.

This is likely unrelated based on your symptoms in comparison to the original post. Can you please raise a new post of your own. Include information indicating which plane, which frequencies, are you tuned to the right freq, are you using the right keybind for the right radio, easy comms on/off etc. The keybind that works for ground crew will be a different keybind than the one you use for your actual radios.

You have a number of mods, of which at least one has errors. In addition to this you're also running an out-of-date version of SRS. Recommend removing your mods and running a slow repair of the game. Then also update SRS. Try again and then drop another log. You also have some settings which are a little high for your system. I can provide feedback from the DCS log analyzer for these recommendation, although won't be applicable to solving the problem you have here.

Please attach your DCS log for review. Note that the F-10 Map is a well known issue in VR. This can largely be due to VRAM overflow....and you only have an 8Gb 3060Ti (and low specs in general for a larger MP server). Current workarounds (aside from lowering textures to reduce VRAM usage...which may still not help): Alt-tab out of the game, and then alt-tab back in again after a few seconds. This can help clear VRAM. Ensure you center and zoom back in on your plane on the map prior to jumping back into the cockpit again Use OpenKneeboard along with the DCW Web Editor Moving Map (as a web dashboard tab). This will display a dynamic map with a lot of the F-10 map functionality. This can help with not even needing to use the F-10 map, depending on your usage.

I reported this in the ED Discord as well. Latest update is that they’ve replicated the issue, it’s been reported, and they’ll be looking into it.

I’ve raised this issue in the ED Discord and attached the news.lua file that was attached in the thread on this post. They’ve replicated the issue and are looking into it.

Had another user also encounter this issue with the DCS Kneeboard being transparent, just the tabs etc. displayed. Would be good to know if and how other folk who've hit this managed to resolve it, if at all.

@Wexler Can you please attach your current `Saved Games\DCS\MissionEditor\news.lua` file to this ticket. If you have already renamed Saved Games\DCS or MissionEditor then grab the news.lua file from that backup and attach here. Needing to get more copies of the bad news.lua file causing issues from people.

Common error in the log being experienced by other users as well. Renaming Saved Games\DCS to Saved Games\DCS.bak as mentioned above will achieve the same result as just renaming Saved Games\DCS\MissionEditor to MissionEditor.old which is the current workaround for this error. 2025-09-23 07:07:40.857 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_news.lua"]:146: bad argument #2 to 'date' (number expected, got string) GUI debug.traceback: stack traceback: [C]: ? [C]: in function 'date' [string "./MissionEditor/modules/me_news.lua"]:146: in function 'showNews' [string "./MissionEditor/modules/me_news.lua"]:259: in function 'funCallBack' [string "./MissionEditor/modules/me_waitDsbweb.lua"]:90: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40> I believe directly deleting the `news.lua` file in that folder has also solved for folk (which would also be the same as renaming the MissionEditor folder). I've tested this myself and that file gets recreated on next startup so seems to be safe.

If you're running DCS from the bin-mt folder (I'm assuming this based on your mention of "multithread" so please correct me if I'm wrong) then you should switch to using the bin folder. They are both multithreaded now and are identical, and the bin-mt folder will be removed in the future.

Yeah Dashomat may have a completely different problem as well, e.g. same problem as you but different problem than the original poster of this thread. They were asked for logs and not supplied them so we don't know if the problem is the same as yours. The part of your error re: "Could not resolve hostname" could entirely be due to the fact that you've turned your network off. Don't know why you're doing that though. Sounds like an easy solution then Have you tried turning on the offline mode of the game?

This log file is just from starting up the launcher, and not the game. Will need a log file from when the actual crash occurs, the log file gets overwritten every time you start the game so get the log before restarting DCS. You can also check in that Logs folder to see if you have recent ones with a name like dcs-log-<timestamp>.zip as this will contain a log and extra information when crashes occur. If so then attach one of those as well.

Thanks for the input, this is however not a GPU driver issue so is unrelated to your problem.

Can you also confirm whether or not you are running any VPN software. Have any firewall changes been made? The error in the log appears to be network related. If not currently using a VPN then can you please try with one. 2025-09-20 12:09:16.069 ERROR ASYNCNET (Main): HTTP request dcs:logout failed with error 99: Unrecoverable error in select/poll 2025-09-20 12:09:16.069 ERROR ASYNCNET (Main): Logout failed: -99

Yeah different issue from this one, initial eyeball this looks to be a network issue. I've dropped some responses on the post you raised.

You have a large number of mods, some with errors. Can you remove these and run the repair again. Can you additionally rename Saved Games\DCS to Saved Games\DCS.old and start DCS again. Whilst this is not guaranteed to resolve the issue at least it rules out any issues with potential corruption in Saved Games\DCS. Looks like you're also running DCS from the bin-mt folder. Can you instead use the one in the bin folder. Both executables are identical and use multithreading, the bin-mt folder will be removed in the future.

Your issue is different so may need to raise your own post. This is the error in your log. Maybe check what the DNS is configured on your system, and update it to use 1.1.1.1 or 8.8.8.8. Are you using aa VPN or anything of that nature? Recommend raising your own post. 2025-09-20 16:01:49.063 ERROR ASYNCNET (11232): HTTP request dcs:modules failed with error 6: Could not resolve hostname 2025-09-20 16:01:50.488 INFO ASYNCNET (Main): login was cancelled. 2025-09-20 16:01:50.498 ERROR ASYNCNET (11232): HTTP request master:en/export/newsletters/ failed with error 6: Could not resolve hostname 2025-09-20 16:01:50.552 ALERT LUACOMMON (Main): Error: GUI Error: [string "Scripts/JSON.lua"]:525: [string "Scripts/JSON.lua"]:240: can't parse JSON at char 1 of: Could not resolve hostname

I believe this is running the DCS.exe in the bin-mt folder and you should instead be using the one in the bin folder instead. They're both multithreaded now and bin-mt will be removed in the future.

Please attach your DCS log file. This issue may be unrelated, or have a different resolution, but need a log file.

Your log is showing the below error message which has caused issues for a number of users. Can you rename your Saved Games\DCS\MissionEditor folder to MissionEditor.old and start DCS again. If this still fails then attach another log file. 2025-09-20 00:44:27.794 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_news.lua"]:146: bad argument #2 to 'date' (number expected, got string) GUI debug.traceback: stack traceback: [C]: ? [C]: in function 'date' [string "./MissionEditor/modules/me_news.lua"]:146: in function 'showNews' [string "./MissionEditor/modules/me_news.lua"]:259: in function 'funCallBack' [string "./MissionEditor/modules/me_waitDsbweb.lua"]:90: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40>

You have some files which could (possibly corrupted) potentially be a cause. The below stacktrace has been identified from a number of issues raised by people: 2025-09-19 13:39:59.035 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_news.lua"]:146: bad argument #2 to 'date' (number expected, got string) GUI debug.traceback: stack traceback: [C]: ? [C]: in function 'date' [string "./MissionEditor/modules/me_news.lua"]:146: in function 'showNews' [string "./MissionEditor/modules/me_news.lua"]:126: in function 'show' [string "./MissionEditor/modules/MainMenu.lua"]:392: in function 'show' [string "./MissionEditor/modules/MainMenu.lua"]:211: in function 'onCancel' [string "./MissionEditor/modules/me_options.lua"]:96: in function <[string "./MissionEditor/modules/me_options.lua"]:75> This has effected people in different ways. Can you please rename Saved Games\DCS\MissionEditor to MissionEditor.old and start up DCS again. There are a couple of other issues from your DCS log file: Please use the bin\DCS.exe instead of the bin-mt\DCS.exe. They are both identical, but bin-mt will be going away in the future. Disable Core Parking. You can do this using the ParkControl software.

This generally is caused by using Notepad (which is a terrible editor and can corrupt files so use Notepad++ instead). So either, use a different editor, or rename the file manually afterwards in Windows. This can cause the same problem for other files as well, e.g. people not understanding why a .lua file isn't taking effect, which they don't realise is actually being named .lua.txt EDIT: you should change your Windows settings to always display file extensions so these things don't get hidden in the future.

DCS launcher settings and in-game settings should be the same thing, the launcher just allows you to configure stuff before starting the game. This is especially helpful as some settings require a restart of DCS. Don't know Nvidia App settings you're referring to. Don't know what overlap there is with the ingame ones, you'd need to post a screenshot of Nvidia App settings you're referring to. You should always launch DCS using the DCS shortcut (and not the MT shortcut either).