IrLED Posted December 9, 2015 Share Posted December 9, 2015 Today 09DEC2015 DCS_Updater was updated to 2.6.9.43 (digisign from 8 dec 2015 21:30:41) and it looks like functionality to switch between release/openbeta is broken (http://forums.eagle.ru/showthread.php?t=114030) Command like DCS_Updater.exe update release:1.2.16 gives [Wrong update command syntax] dialog Using recommended syntax gives error in log (eg. "DCS_Updater.exe update 1.5" -> ERROR: Version 1.5 is not available.) Link to comment Share on other sites More sharing options...
Grimes Posted December 9, 2015 Share Posted December 9, 2015 The syntax has changed. I'm not sure if I can reveal what has changed so its best to wait to see if C0ff makes a comment. The right man in the wrong place makes all the difference in the world. Current Projects: Grayflag Server, Scripting Wiki Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread) SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum Link to comment Share on other sites More sharing options...
ED Team c0ff Posted December 9, 2015 ED Team Share Posted December 9, 2015 Hi new syntax is not a secret, but I preferred to not show the new syntax in full in the help dialog. The reason I changed it is that too many users did thing like "DCS_updater update ka50" thus breaking their installs. Hmm, I've just realized that they probably edited their autoupdate.cfg files and the new syntax won't help. The updater does check if the branch name is a valid one. Anyway, the new syntax is [version][@branch], like DCS_updater.exe update @release DCS_updater.exe update @openbeta DCS_updater.exe update @openalpha or DCS_updater.exe update 1.5.1@openbeta Dmitry S. Baikov @ Eagle Dynamics LockOn FC2 Soundtrack Remastered out NOW everywhere - https://band.link/LockOnFC2. Link to comment Share on other sites More sharing options...
Recommended Posts