You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Importing some .yyzs made with 2024.1300 Betas can cause 2024.11 to lock up - you will get the dialog that the project needs to be downgraded, but the IDE instantly goes into a hang and so you cannot click on anything except the close button.
No errors are logged in the ui.log - it simply stops like this:
[15:39:21:628(6e64)] Importing project 'D:\Downloads\DestroyParticleTest.yyz'
[15:39:21:646(6e64)] Importing 'D:\Downloads\DestroyParticleTest.yyz'
[15:39:21:784(6e64)] Setting ProjectFullFilePathMacro to 'C:\Users\danie\GameMakerProjects\DestroyParticleTest\DestroyParticleTest.yyp'
[15:39:21:784(6e64)] Setting ProjectDirMacro to 'C:\Users\danie\GameMakerProjects\DestroyParticleTest'
[15:39:21:785(6e64)] Setting ProjectNameMacro to 'DestroyParticleTest'
Expected Change
The IDE should not lock up, I should have been able to downgrade and import the project
The issue is now fixed in 24.13+
We can't fix it in 23.11, as it was bad logic in the IDE, rather than anything to do with the project or ProjectTool itself, sadly.
Description
Importing some .yyzs made with 2024.1300 Betas can cause 2024.11 to lock up - you will get the dialog that the project needs to be downgraded, but the IDE instantly goes into a hang and so you cannot click on anything except the close button.
No errors are logged in the ui.log - it simply stops like this:
Expected Change
The IDE should not lock up, I should have been able to downgrade and import the project
Steps To Reproduce
How reliably can you recreate this issue using your steps above?
Always
Which version of GameMaker are you reporting this issue for?
2024.11.0 (Monthly)
Which operating system(s) are you seeing the problem on?
Windows 10
Are you running GameMaker from inside your Steam library?
No
Sample Package Attached?
Sample Project Added?
The text was updated successfully, but these errors were encountered: