Skip to content

Conversation

@4ian
Copy link
Owner

@4ian 4ian commented Dec 8, 2025

  • When adding a new object type, the hot reload could break if a previous hot reload was done without the script files (typically, when adding an object from an already used type)
  • When adding a new object or anything needing a loading screen, the loading screen and the in-game editor were fighting for the rendering.

4ian added 2 commits December 8, 2025 19:17
* When adding a new object type, the hot reload could break if a previous hot reload was done without the script files (typically, when adding an object from an already used type)
* When adding a new object or anything needing a loading screen, the loading screen and the in-game editor were fighting for the rendering.
…the asset store)

This was because:
- The new object was the first of its type, and the second preview (related to the added object, after the first one related to the added resource) was wrongly not launched because of a stale state being read.
- On the web-app, the first hot reload was longer to launch than the second preview, and so the second hot reload was not launched. Now, it is queued properly.

- When an asset pack was installed, new object type was not recognized
@4ian 4ian force-pushed the fix/reload-crashs-and-flashes branch from 814bb40 to 59d4ecc Compare December 10, 2025 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants