It does not accept keyboard or joystick inputs.

[yakiniku]

After the update, I cannot use any keyboard or joystick inputs at all.
I noticed this on the controls settings screen.
Also, when pressing several keys on the controls settings screen, the display turns completely black and becomes unreadable.
In addition, when I press the OK button to return to the main screen, the display also turns completely black.
 

ログ.zip

Edited 16 hours ago by yakiniku

[silverdevil]

1 hour ago, yakiniku said:

After the update, I cannot use any keyboard or joystick inputs at all.
I noticed this on the controls settings screen.
Also, when pressing several keys on the controls settings screen, the display turns completely black and becomes unreadable.
In addition, when I press the OK button to return to the main screen, the display also turns completely black.

i see in your log

2025-09-19 13:39:39.417 INFO    INPUT (Main): created [Keyboard]
2025-09-19 13:39:39.424 INFO    INPUT (Main): created [WINWING Orion Throttle Base II + F15EX HANDLE L + F15EX HANDLE R] with full id [WINWING Orion Throttle Base II + F15EX HANDLE L + F15EX HANDLE R {F7B1ED60-DDCA-11ef-8001-444553540000}], ForceFeedBack: no
2025-09-19 13:39:39.425 INFO    INPUT (Main): created [T-Rudder] with full id [T-Rudder {AC1AA1A0-1F3C-11ef-8001-444553540000}], ForceFeedBack: no
2025-09-19 13:39:39.435 INFO    INPUT (Main): created [WINWING Orion Joystick Base 2 + JGRIP-F16] with full id [WINWING Orion Joystick Base 2 + JGRIP-F16 {1D001920-DDCB-11ef-8002-444553540000}], ForceFeedBack: no
2025-09-19 13:39:39.459 INFO    INPUT (Main): created [TrackIR]

is it possible your bindings got deleted or corrupted?

[yakiniku]

The control settings have not been deleted.
On this screen, it does not even respond to key inputs.
Naturally, both the keyboard and joystick work fine outside of DCS.
 

[yakiniku]

After reverting DCS to version 2.9.19.13478, both keyboard and joystick inputs returned to normal.

And after updating to the new version again, it stopped accepting inputs.

It seems there is indeed some kind of bug in the new version.

Edited 4 hours ago by yakiniku

[sleighzy]

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.

Edited 2 hours ago by sleighzy

[yakiniku]

Deleting the MissionEditor folder solved the issue. Thank you.