[RESOLVED]Black screen when adjusting controls after update April 22

[Tornado]

When I want to adjust the controls of the M-2000C and press on ok the screen turns black. Music is still playing but I have the to kill DCS with the taskmanager. Start DCS again. I tried to adjust the controls for the mirage 3 times now, but every time same story. Black screen and now way to get back in the menu. It happens indeed after the update 1.5.3. But then I was able to do something in push the OK button after every change I did. But when I edited more controlls in one run the screen starts to turn black.

 

After todays update in 1.5.3 (April 22) I tried to adjust only one button for my Warthog and pressed on ok and the black screen turns in.

Edited April 23, 2016 by BIGNEWY
TITLE

[BIGNEWY]

Strange, does DCS have administration rights?

 

do you have an xbox one controller by any chance?

 

attach your logs folder after reproducing the problem, we may find some clues

[Tornado]

Additional information. Also black screens on the last update of the NTTR map DCS 2.0.2. But only when want to adjust the controls for the Mirage. Other aircraft are doing fine the controls menu sofar. But I get crashes when adjusting the controls of the Mirage. However in the last update of OpenBeta 1.5.3 (today April 22) I don't have that problem. Only the updated release version DCS 1.5.3 and the DCS 2.0.2.

 

Also:

It only happens in the DCS options Controls menu. When adjusting the Warthog buttons in flight or ramp start up I can adjust the buttons without problems.

 

For me sofar the Mirage is afffected with that problem

[Tornado]

Strange, does DCS have administration rights?

 

do you have an xbox one controller by any chance?

 

attach your logs folder after reproducing the problem, we may find some clues

 

 

I don't have an Xbox controller. What I have is the Warthog Trustmaster, VKB rudder MKIII and a TrackIR4 Natural Point

Yes strange indeed. Only the Mirage sofar. Here are my logs from the OpenAlpha 2.0.2. (update yesterday) and the release version of DCS 1.5.3. (update today). I hope you can find out what the problem is. There is another simmer who reported that on the 21st of March

 

 

http://forums.eagle.ru/showthread.php?t=162989&highlight=controls

 

I responded first on that thread. But made a new thread on this issue

dcs 1.5.3 release version.rar

dcs 2.0.2 OpenAlpha.rar

[BIGNEWY]

Seeing some unusual things in the 2.0 log

 

00129.261 ALERT LUACOMMON: Error: GUI Error: [string "./Scripts/Input\Data.lua"]:1591: attempt to index local 'defaultCommand' (a nil value)

GUI debug.traceback: stack traceback:

[C]: ?

[string "./Scripts/Input\Data.lua"]:1591: in function 'getCommandAddedCombos_'

[string "./Scripts/Input\Data.lua"]:1647: in function 'getKeyCommandDiff_'

[string "./Scripts/Input\Data.lua"]:1666: in function 'getKeyDiffs_'

[string "./Scripts/Input\Data.lua"]:1729: in function 'saveDeviceProfile'

[string "./Scripts/Input\Data.lua"]:1851: in function 'saveChanges'

[string "./MissionEditor/modules/Options\TabViewControls.lua"]:78: in function 'save'

[string "./MissionEditor/modules/Options\TabsView.lua"]:141: in function 'onOptionsSaved'

[string "./MissionEditor/modules/Options\Controller.lua"]:58: in function 'optionsSaved'

[string "./MissionEditor/modules/Options\Data.lua"]:142: in function 'saveChanges'

[string "./MissionEditor/modules/me_options.lua"]:91: in function 'onChange'

[string "./dxgui/bind/Button.lua"]:22: in function 'callback'

[string "./dxgui/bind/Widget.lua"]:310: in function <[string "./dxgui/bind/Widget.lua"]:305>

 

 

 

 

try a fresh saved games dcs folder, rename the ones you have to keep them as backups, restart dcs and allow them to create new ones, redo your settings and try the controls again.

 

C:\Users\yourname\Saved Games\DCS

C:\Users\yourname\Saved Games\DCS.openalpha

 

 

Also do a repair, if you are using any unofficial mods remove them first and then do a repair.

 

Let us know how you get on

Edited April 22, 2016 by BIGNEWY

[Tornado]

try a fresh saved games dcs folder, rename the ones you have to keep them as backups, restart dcs and allow them to create new ones, redo your settings and try the controls again.

 

C:\Users\yourname\Saved Games\DCS

C:\Users\yourname\Saved Games\DCS.openalpha

 

 

Also do a repair, if you are using any unofficial mods remove them first and then do a repair.

 

Let us know how you get on

 

I will be back tomorrow and try out your suggestions. It is getting very late (after midnight) but thanks for your help sofar. I will be back as soon.

Tornado

[Rangi]

@OP have you tried setting control in a single player session? Someone else said they were getting crashes in options control setup but not in-game, worth a try to get you going for now.

[mvsgas]

http://forums.eagle.ru/showthread.php?t=165090

[Tornado]

Seeing some unusual things in the 2.0 log

 

 

 

 

 

 

try a fresh saved games dcs folder, rename the ones you have to keep them as backups, restart dcs and allow them to create new ones, redo your settings and try the controls again.

 

C:\Users\yourname\Saved Games\DCS

C:\Users\yourname\Saved Games\DCS.openalpha

 

 

Also do a repair, if you are using any unofficial mods remove them first and then do a repair.

 

Let us know how you get on

 

As stated yesterday I did some tests on this issue today I can report the following:

 

I took the actions as suggested. I made backups from the saved games folders and let DCS 2.0.2. and 1.5.3 (release) made fresh folders. I was able to adjust the buttons for the Warthog as I was used to. So indeed the problem was somewhere in the saved games folders of both versions.

 

I did some further research as I wanted to know which folder caused the problem. I repaced my DCS saved games folder backup back and tested each separate folder (renamed the folder so there was a new one created). Well the problem was in the following folder: MissionEditor. After renaming it and let DCS make a new MissionEditor folder the problem was gone. In which specific lua file the problem was, I coundn't find out. I guess it is one of the lua files in the MissionEditor head folder. I put some backup lua files back in the new created MissionsEditor folders. Because there was a new log file you loose all your data in your logbook. That kind of lua files I pushed back.

 

Maybe you have an idea which lua file was affected. Well it is good to know for all of us.

 

Thanks for all help and suggestions.

 

Tornado

[BIGNEWY]

Great to see you are back up and running. Enjoy!

 

and thanks for feeding back, I will enquire about the log book, I do not know much about it to be honest. Can you not just move the old one back?

 

C:\Users\yourname\Saved Games\DCS\MissionEditor\logbook.lua

[Tornado]

Great to see you are back up and running. Enjoy!

 

and thanks for feeding back, I will enquire about the log book, I do not know much about it to be honest. Can you not just move the old one back?

 

C:\Users\yourname\Saved Games\DCS\MissionEditor\logbook.lua

 

Yes all is working again. Perhaps I expressed (did not write it correct) it wrong about the logbook. I used backup logbook.lua in the new made C:\Users\yourname\Saved Games\DCS\MissionEditor.

I renamed C:\Users\yourname\Saved Games\DCS\MissionEditor.org. So my old logbook.lua was saved. After DCS made a new MissionEditor folder I took my old logbook.lua file.

Just as you wrote I moved to old one back.

Sorry for the miscommunication.:)

[BIGNEWY]

No problem all is good :)

 

enjoy

[mvsgas]

The problem is still there for me. Renaming the mission editor file, did work initially, but after flying online and going to the option page, changing controls and pressing ok will cause a black screen. So far changing the SU-25T or the Mirage. This does not happen if I change controls in single player, while in the cockpit.

[jcbak]

The problem is still there for me. Renaming the mission editor file, did work initially, but after flying online and going to the option page, changing controls and pressing ok will cause a black screen. So far changing the SU-25T or the Mirage. This does not happen if I change controls in single player, while in the cockpit.

Same here....

[BIGNEWY]

Open new threads so I can help you individually and attach your logs and autoupdate_log.txt