Dangerzone Posted December 25, 2022 Posted December 25, 2022 Hi, With my version of DCS - I only get prompted to update when a new stable release is out (which is what I want). However on another computer we're having problems where it keeps prompting us to update to the latest Open Beta release, but we wish to stay on stable. I've tried the command line "dcs_updater update @Release", which it comes back with "Latest version installed", but every subsequent start of the application we get prompted to update to 2.8 again. Can someone please tell me where the configuration is and how to change it so that we won't get prompted for Open Beta updates, but only stable on this other PC? Cheers DZ
Flappie Posted December 25, 2022 Posted December 25, 2022 Hi. The updater configuration is contained in .".DCS World\autoupdate.cfg". The file itself recommends that you don't mess with it. But if you break it by editing it, you can delete it and ask for a repair anyway. Open the file and ensure you see this: { "WARNING": "DO NOT EDIT this file. You may break your install!", "branch": "release", I use the "dcs_updater update @release" / "dcs_updater update @openbeta" commands several times a month and I never had your issue. Try without the capital "R", maybe? 1 ---
Dangerzone Posted December 25, 2022 Author Posted December 25, 2022 (edited) 19 minutes ago, Flappie said: Hi. The updater configuration is contained in .".DCS World\autoupdate.cfg". The file itself recommends that you don't mess with it. But if you break it by editing it, you can delete it and ask for a repair anyway. Open the file and ensure you see this: { "WARNING": "DO NOT EDIT this file. You may break your install!", "branch": "release", I use the "dcs_updater update @release" / "dcs_updater update @openbeta" commands several times a month and I never had your issue. Try without the capital "R", maybe? Thanks flappy. I've just checked the autoupdate.cfg on that system - and it indeed already says "release" in the branch section of that config file (all lowercase too... so I didn't need to make any changes), yet it continues to persist to update me to 2.18. Very strange. As you mention - I've used the command line numerous times myself without issue too - so I have no idea what's going on with that system - but it definitely seems to want to switch from release to open beta each time I update. Edited December 25, 2022 by Dangerzone
Flappie Posted December 25, 2022 Posted December 25, 2022 Please attach your "autoupdate_log.txt" log. ---
Dangerzone Posted December 25, 2022 Author Posted December 25, 2022 14 minutes ago, Flappie said: Please attach your "autoupdate_log.txt" log. Thanks for taking the time to look at this for me Flappie - it's got me confused. Please find attached both the log file, as well as the config file. autoupdate.cfg autoupdate_log.txt
Dangerzone Posted December 25, 2022 Author Posted December 25, 2022 I'm going to try allowing it to 'have it's own way' and update to Open Beta, and then force an update back to Stable and see if that resolves the issue...
Solution Flappie Posted December 26, 2022 Solution Posted December 26, 2022 It looks like your release version is not up-to-date. Your should do this update indeed. { "WARNING": "DO NOT EDIT this file. You may break your install!", "branch": "release", "version": "2.7.17.29493", 1 ---
Dangerzone Posted December 26, 2022 Author Posted December 26, 2022 That's it. That's solved the issue. Thanks Flappie for your help!
Recommended Posts