4. FAQ

Common Mistakes

Q: The project fails to open because it's missing prefabs. What do I do?

A: Getting Started

Q: I just created a new stage and it crashes when I try to load it. The crash report says something like Variable <variable> not set before reading it

A: In most cases, this means the instances in the room were placed in the wrong order. Make sure they are created in this exact order:

• obj_game
• your stage controller object, for example obj_rm_stage_test
• player objects
• everything else

Check the instance creation order in the room and fix it if needed

Performance Issues

Q: My framerate drops a lot or becomes very unstable

A: Make sure you apply culling to the objects you create. By default, some triggers do not use culling so they stay loaded, which already gives you around 60 loaded objects on average. If the number of loaded objects goes above 120, something is probably wrong

Also, line scrolling (the one set up with bg_convert_scaled()) does not use a shader. It is drawn in a brute-force way, which is expensive by nature. Try to keep the number of lines drawn by this effect as low as possible

Collision Problems

Q: I created a new collision tileset, and now the game crashes when I load a stage that uses it. The crash report says ds_map_find_value argument 1 is incorrect type (undefined) expecting a ds_map

A: The framework relies on precomputed collision data to significantly reduce collision calculation overhead. Before using a new collision tileset, you must register it in the Collision section of the scr_game_setup() script

Q: The player sometimes loses all momentum when landing after a long fall

A: This is expected, since wall collision always happens first. It is recommended to mark all shallow surfaces with the jump-through marker, so the player does not try to collide with those tiles horizontally