View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0027052||2.x IDE Bugs||Compiling||Public||2017-07-11 16:15||2018-10-25 16:49|
|Priority||Medium||Severity||C - General||Reproducibility||100%|
|Platform||-||OS||Windows 10||OS Version||Pro x64|
|Target Version||2.2.1||Fixed in Version||2.2.1|
|Summary||0027052: Compiling: "Corrupt or damaged GameMaker build tools." status should properly abort builds and tell the user to fix|
|Description||Looking at a ticket about not begin able to run projects following an update to 2.0.7, we can see that GMS2 has logged out that their runtime files are corrupt, but the IDE doesn't actually tell the user this, so they had to contact us for us to investigate. They were also sat watching the build timer tick upwards with no info in their output window log, when the build should have been gracefully aborted.|
Expected: Any time we identify this state the build should be stopped and the user shown a message that their runtime is damaged and do they want to re-download it now, as without doing this they will be unable to build projects. Saying "Yes" should take them to the runtime manager dialogue and automatically start getting the runtime the IDE expects.
|Steps To Reproduce||1. Install GMS2, but then mess about with your runtime install.|
2. Try running a project for Windows.
3. See if the build gets "stuck" in the output window and the timer keeps going up.
Repro: Not reproduced internally yet, but the log makes it clear this happens.
|Tags||No tags attached.|
|2.x IDE Found In||184.108.40.206|
|2.x Runtime Found In||220.127.116.11|
|2.x IDE Verified In||18.104.22.1685|
|2.x Runtime Verified In||22.214.171.1248|