Glad to see these timeline fixes slowly come in. I experienced crashes and corruptions so many times I could not spend the time to even report them. Still enjoyed using timelines/custom eases.
Wow, all my respects to you good sir. Software is a nightmare, and you are a valiant knight.
If anyone wants to work consistently and freely using Github, currently the PWA is not the way to go. Shortcutting an editor version works exactly as it was before you enforced updates, and has never given me any issues since. I just click c3 on my taskbar, and the correct version is displayed for everyone.
If anyone wants extra steps and the risk of losing progress, that's cool. Tried reasoning on the forums a long time ago, to everyone's frustration on the dev's responses. I still respect his stance, and his work is absolutely incredible (has been my main professional engine for too long to remember).
For anyone reading this reply, my workaround fixes the known "Stuck in old version" bug which annoys a lot of people around the discord at the very least (PWA c3 gets stuck to the version you install it as, and inconsistently prompts you with an update on launch which leads to members sometimes doing commits in an older version) and also lets you actually stick to a version in case some custom functionality breaks without your consent.
Additionally those using custom engine launchers or edits were in a disadvantage as it was impossible to choose when to upgrade your team to a new version. I still lost time because of the devs not implementing a basic software QOL option before finding this workaround. The original post has everything noted.
Your work is awesome, Ashley, but you are ignoring a lot of paying customers by not even adding an advanced option like a Chrome parameter for disabling the enforced updates which have consistently broken workflows.
Scirra has since enforced updates upon any user.
This breaks version control more often than not, and leads to losing time and resources.
I tried reasoning with them on a thread to no use, even though any other user agreed a toggle in options or at the very least an advanced Chrome parameter was necessary.
There is a workaround I discovered recently:
1. Go to the editor version url (editor.construct.com/rXXX)
2. Three dots Chrome menu -> More tools -> Create Shortcut (open as new window)
3. Pin this window to your taskbar.
This way, you can actually control when you want your team to upgrade.
In case anyone at Scirra cares, the same issues I talked about in the thread you dismissed are still ongoing and affect Github workflows.
Not working!
After adding the object, the game launches in a black screen without even having added events. This is solved by undoing adding the object, or deleting it right off the bat.
r218, nw 0.47 & greenworks 0.47
Member since 11 Jun, 2020