[RESOLVED]Crashing with 1.5.3.53108@openbeta and DCS_updater error

[Gliptal]

I just now updated to 1.5.3.53108@openbeta using DCS_updater. The game autolaunched fine, but subsequent launches crash immediately. Logs\dcs.log is as follow:

=== Log opened UTC 2016-05-22 09:52:46
00000.000 INFO    VFS: Using 'Saved Games': "C:\Users\affa\Saved Games"
00000.002 INFO    DCS: DCS/1.5.3.53108 (x86_64; Windows/6.2.9200)
00000.002 INFO    DCS: CPU cores: 4, System RAM: 8191 MB
00000.011 INFO    EDCORE: (dDispatcher)enterToState_:0
00000.026 INFO    Dispatcher: 2016/5/22 11:52 V1508170900
00000.058 INFO    INPUT: Device created Keyboard
00000.060 INFO    INPUT: Device created Saitek X52 Flight Control System {3012D900-4049-11e5-8001-444553540000}
00000.061 INFO    INPUT: Joystick created[saitek X52 Flight Control System {3012D900-4049-11e5-8001-444553540000}], ForceFeedBack: no
00000.065 INFO    INPUT: Device created Logitech RumblePad 2 USB {440AE2E0-92DD-11e5-8001-444553540000}
00000.066 INFO    INPUT: Joystick created[Logitech RumblePad 2 USB {440AE2E0-92DD-11e5-8001-444553540000}], ForceFeedBack: no
00000.078 INFO    INPUT: Device created Joystick - HOTAS Warthog {B261BDA0-6C58-11e5-8001-444553540000}
00000.078 INFO    INPUT: Joystick created[Joystick - HOTAS Warthog {B261BDA0-6C58-11e5-8001-444553540000}], ForceFeedBack: no
00000.096 INFO    INPUT: Device created Throttle - HOTAS Warthog {B2640790-6C58-11e5-8002-444553540000}
00000.097 INFO    INPUT: Joystick created[Throttle - HOTAS Warthog {B2640790-6C58-11e5-8002-444553540000}], ForceFeedBack: no
00000.114 INFO    INPUT: Device created Controller (Xbox 360 Wireless Receiver for Windows) {0F3BEBC0-3A2E-11e5-8008-444553540000}
00000.114 INFO    INPUT: Joystick created[Controller (Xbox 360 Wireless Receiver for Windows) {0F3BEBC0-3A2E-11e5-8008-444553540000}], ForceFeedBack: no
00000.331 INFO    SOUND: loaded 1084 sdefs from "sounds\sdef"
00000.400 INFO    SOUND: Using driver: xaudio29
00000.436 INFO    SOUND: XAudio2: channel layout: Headphones/Stereo
00000.436 INFO    SOUND: Using SSE FTZ/DAZ mode.
00000.745 ALERT   DCS: Error running Scripts/Database/db_main.lua: [string "./Mods/aircraft/M-2000C/entry.lua"]:70: attempt to index global 'M2KFM' (a nil value)

 

I understand it's a M-2000C module problem, so tried to repair using DCS_updater. Whatever command I give though, the updater crashes with the following log:

--- Log file: C:\Program Files (x86)\Games\Other\DCS World\autoupdate_log.txt
=== Log opened UTC 2016-05-22 09:53:52
INFO : DCS_Updater/2.6.16.58 (Windows NT 6.2.9200; Win64; en-GB)
INFO : cmdline: "C:\Program Files (x86)\Games\Other\DCS World\bin\DCS_updater.exe" --apply repair
STATUS: Initializing...
INFO : basedir: C:\Program Files (x86)\Games\Other\DCS World\
ERROR: Can't parse config: JSON error: parse error: premature EOF
                                      
                    (right here) ------^
INFO : Config contents: --- BEGIN ---
INFO : Config contents: ---  END  ---
ERROR: JSON error: parse error: premature EOF
                                      
                    (right here) ------^
=== Log closed.

I already dowloaded a new copy of DCS_updater.exe from the official website. I'd rather not have to download all of DCS again.

Edited May 22, 2016 by BIGNEWY
TITLE

[LevelPulse]

Delete the M-2000K Module and install it again.

[Gliptal]

Can't. DCSW now starts, but it won't let me log in (I click on the arrow but nothing happens) and it hangs at 12% when loading the module manager.

 

DCS Updater is still broken.

[LevelPulse]

Can't. DCSW now starts, but it won't let me log in (I click on the arrow but nothing happens) and it hangs at 12% when loading the module manager.

 

DCS Updater is still broken.

 

Ah i see, i had a similar. I gave up in the end and reinstalled DCS.

[Gliptal]

I'd rather not. My connection is quite slow. Any official support available?

 

LevelPulse, any chance you could send me your autoupdate.cfg file? Mine seems to be corrupted, and it may be what is holding the updater back.

 

EDIT: I was right, the problem was a corrupted autoupdate.cfg file. I was sent one, modified a couple of the properties to match my installation, and ran a repair. I had to download a couple of DLCs, but it's still better than downloading the whole thing again.

Edited May 22, 2016 by Gliptal

[BIGNEWY]

for ref.

 

delete the autoupdate.cfg and repair it should fix the issue

 

you should not edit or modify the autoupdate.cfg

 

if your updater is corrupted you can get a new one here

 

http://updates.digitalcombatsimulator.com/

[Gliptal]

I tried, the updater wouldn't work.

[BIGNEWY]

but all is ok now, correct?

[Gliptal]

Yep, a new .cfg did the trick.

[BIGNEWY]

super :)