BETLOG
commented
2 years ago Instead of launching steam and then selecting the game I just tried launching the game via: setsid steam steam://rungameid/427520 & After waiting a short while i went into library and clicked the factorio 'icon' (not the actual start button inside that menu) .... as i did so the game started. Maybe the timing is unrelated, but it felt like it was a result of my entering the menu to view its stop/play button's status. It's all very random.
Confirmed: thats exactly whats happening. Apparently while waiting to fail to cloud-update (despite that being globally disabled), simply by entering the library and then the Factorio entry it immediately starts the game.
3 test cases - the last one succeeds:
KDE application menu > games > steam Factorio > PLAY "Preparing to launch Factorio" ...indefinitely steam > exit "Finishing steam cloud sync" ...indefinitely "EXIT NOW" steam exits
steam & Factorio > PLAY "Preparing to launch Factorio" ...indefinitely "CANCEL" steam > exit "Finishing steam cloud sync" ...indefinitely "EXIT NOW" steam exits
steam steam://rungameid/427520 & "Preparing to launch Factorio" ...indefinitely KDE system tray > steam icon > Library > Factorio (no, i do not even press PLAY/STOP - i simply enter the Factorio panel...) game immediately starts https://gist.github.com/BETLOG/e374b32291819f7fd44024808537d1ee https://gist.github.com/BETLOG/00eba8f8f1287e7953ea94dbe37a3bcb
brvcancr
Your system information
Please describe your issue in as much detail as possible:
expected Factorio complete or timeout on cloud sync, or obey settings>cloud>disabled setting, and start the game. did happen Factorio displays 'Preparing to launch Factorio' indefinitely (45 minutes at last attempt). In one case it did start after 5 minutes. Otherwise it has been impossible to start the game at all. Disabling or enabling cloud in steam settings or game settings, in any combination, does not help.
My entire .factorio directory is 115Mb, so its not a case of user-impatience', it's simply not doing it at all, nor obeying the 'no cloud' setting.
Steps for reproducing this issue:
There seems to be a bunch of other similar older issues, but I'm not sure this is the same as them. Seems someone resurrected an old bug in a slightly different form.