-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reset #8636
Comments
I am guessing this is a report that your computer or GameMaker reset/crashed while trying to build your project inside GameMaker? There is no information here on what you are actually reporting, but I can see from your logs that your GameMaker ui.log and compiler logs both seem to stop mid-way through a build:
(Although, I am not entirely sure how we still have a partial compiler log if it is that your machine reset, so this doesn't entirely sound right either.) |
Project contains 1 Sprite which appears to be an animated player character, but this contains 207 frames at 1920x1080 size. The Sprite is then added into the room on an Asset layer and is manually-scaled down to a very small value (relatively-speaking). |
Okay, so I am guessing now that by "reset" you mean that you manually cancelled your project from building, thinking it was stuck, as this project does take about 5 minutes to run - however, it does succeed: I get the same logging, so there is no bug here:
Then there is a long delay before anything else appears, and then there is one more GC line, followed by all the rest of the build logging:
|
Closing as Not A Bug. You simply need to review the size and also the number of sprites you're using - your player character does not need 207 frames at 1080p (and it probably should be on a transparent background anyway) - and then your build times will hopefully improve accordingly. |
Description
reset
Which version of GameMaker are you reporting this issue for?
IDE v2024.8.1.171 Runtime v2024.8.1.218
Which operating system(s) are you seeing the problem on?
Windows 10.0.19045.0
dc0aa10f-f372-495a-8dbe-f388917d65bd
The text was updated successfully, but these errors were encountered: