Nealius Posted December 12, 2017 Share Posted December 12, 2017 After saving some missions, I attempt to exit the ME. Nothing happens. I attempt to exit again, and a popup claiming changes have not saved appears. It doesn't matter if I click Yes, No, or Cancel, the ME is still unresponsive. If I click on the icons on the left panel, the icons will higlight blue and remain highlighted, but none of the windows will appear at all. The only way for me to exit is to kill DCS.exe through Task Manager. I have already repaired the 1.5.8OB TWICE. This happens without mods. This does not happen on the 1.5.7 Release. Image for reference. You can see all of the icons on the left panel highlighted. Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted December 12, 2017 ED Team Share Posted December 12, 2017 can you reproduce and then attach your dcs.log straight after. it should show us some clues, possibly a GUI error Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
Nealius Posted December 12, 2017 Author Share Posted December 12, 2017 Log attached. After my two repairs I reinstalled a texture mod and environment sound mod, but this problem appeared even on the clean install prior to installing mods, so the mods should not be affecting it. Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted December 12, 2017 ED Team Share Posted December 12, 2017 00112.056 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_aircraft.lua"]:2077: attempt to index field 'group' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/me_aircraft.lua"]:2077: in function 'onSpinUnitOf' [string "./MissionEditor/modules/me_aircraft.lua"]:1720: in function 'verifySingleInFlight' [string "./MissionEditor/modules/me_aircraft.lua"]:742: in function 'changeType' [string "./MissionEditor/modules/me_aircraft.lua"]:1193: in function 'setType' [string "./MissionEditor/modules/me_aircraft.lua"]:1088: in function 'changeCountry' [string "./MissionEditor/modules/me_aircraft.lua"]:1572: in function 'fillCountries' [string "./MissionEditor/modules/me_aircraft.lua"]:1526: in function 'updateCountries' [string "./MissionEditor/modules/me_mission.lua"]:2425: in function 'create_new_mission' [string "./MissionEditor/modules/me_menubar.lua"]:377: in function 'Exit' [string "./MissionEditor/modules/me_menubar.lua"]:357: in function 'onExit' [string "./MissionEditor/modules/me_toolbar.lua"]:593: in function 'onChange' [string "./dxgui/bind/Button.lua"]:22: in function 'callback' [string "./dxgui/bind/Widget.lua"]:330: in function <[string "./dxgui/bind/Widget.lua"]:325> 00117.148 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_bullseye.lua"]:89: attempt to index field 'bullseye' (a nil value) GUI debug.traceback: stack traceback: My guess is a unofficial modification was left in during the update, have you tried a cleanup? and then a repair guide in my signature for the cleanup Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
Nealius Posted December 12, 2017 Author Share Posted December 12, 2017 (edited) Looks like the cleanup found some leftovers. And it looks like I'll lose all my liveries :( Edited December 12, 2017 by Nealius Link to comment Share on other sites More sharing options...
Nealius Posted December 24, 2017 Author Share Posted December 24, 2017 Cleanup didn't work. It seems like this issue only happens when I create/edit a KC130 in the ME. I wonder if there's some issue with the KC130? Link to comment Share on other sites More sharing options...
Dragonares76 Posted January 10, 2018 Share Posted January 10, 2018 Hi ! I have the same problem but on the release 1.5.8 ... But I identified what caused this unresponsive state of the ME (at least for me): When I try to place a M2000-C The bad thing is that I don't know how to resolve this problem, even when identified. I tested quite all the other planes playable in the game and they do not induce this unresponse of the ME ... "Clear to startup ... Contact ..." Geoffrey Wellum - First Light [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Dragonares76 Posted January 10, 2018 Share Posted January 10, 2018 here is my log file if needed ...Logs.zip "Clear to startup ... Contact ..." Geoffrey Wellum - First Light [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Flagrum Posted January 10, 2018 Share Posted January 10, 2018 Seems to be a problem with a livery. Do you have any non-standard M2KC liveries installed? Try it without them, if that is the case. Otherwise, try a DCS Repair. Link to comment Share on other sites More sharing options...
Dragonares76 Posted January 10, 2018 Share Posted January 10, 2018 I made a cleanup then repair I'll test, I'll keep you in touch asap ;) "Clear to startup ... Contact ..." Geoffrey Wellum - First Light [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Dragonares76 Posted January 10, 2018 Share Posted January 10, 2018 OK It works after Clean and Repair One guy of my team asked me if i deleted the .zip of our liveries, and it may be the source of the problem ... Check it if you have such issue ;) "Clear to startup ... Contact ..." Geoffrey Wellum - First Light [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Nealius Posted February 2, 2018 Author Share Posted February 2, 2018 (edited) This is still happening to me in 2.5. No mods. Cleanup and repair did not fix. Interestingly I never had this problem in 2.2. Edited February 2, 2018 by Nealius Link to comment Share on other sites More sharing options...
Recommended Posts