Troubleshooting Gessa: common problems and fixes
Use these checks when an editor or game will not load, a friend cannot open a published link, a shared rule behaves differently than expected, or an AI edit or generated asset needs adjustment. Compare the result after each change to find the next useful step.
The editor or a game will not load, or shows offline
Cause: the browser or device may not meet the graphics and network requirements, or a connection dropped. Gessa renders with WebGPU where it is supported and falls back to WebGL2, so an unsupported browser, disabled hardware acceleration or a blocked network can all show as a page that will not load.
Try: use a current, compatible browser with hardware acceleration on, reload the page, and check your connection. On a managed device such as a school Chromebook, confirm that graphics support and network access are not restricted by policy.
The game looks different for me than for a friend
Cause: browsers and devices differ, and the same scene can take the WebGPU path on one machine and the WebGL2 fallback on another. Lighting and performance can vary as a result.
Try: test on the browsers and devices your players actually use, and compare the same scene across them. Judge visual quality on target hardware rather than on one machine.
A friend cannot open my published game
Check: confirm that the link opens the published play page and that the version you intend to share has been published. The play page is separate from the editor.
Try: publish the game, then open its public play page yourself, outside the editor, and share that link. Confirm the game loads and the controls work before inviting more people.
The AI changed the wrong thing, or not what I asked
Check: compare what changed with the behavior you intended. Identify the specific object or rule and the smallest change that would produce the result you want.
Try: ask for one specific change at a time, and describe the difference between the intended result and what you observed. Inspect and test after each change, so you always know which edit did what.
Multiplayer feels laggy or players see different states
Check: use the same game version and reproduce the shared action with both players. Compare their connection quality and what each player sees. Gessa’s runtime is server-authoritative, so test the shared result rather than relying on one player’s view.
Try: keep shared state focused on what players truly need to agree on, test the specific shared rule with more than one player, and expect the server, not any one client, to be the source of truth. Describe the intended shared behavior when asking for a change.
A generated model looks wrong in the scene
Check: compare the model’s scale, orientation and materials with the player and surrounding scene. Identify the specific shape or appearance you want to adjust.
Try: refine the prompt for a clearer shape, adjust scale and materials in the editor, and open the model in browser Blender when it needs real shaping. Always judge it against the player and the rest of the scene.
Performance is poor or the frame rate drops
Check: compare the same scene on your target devices. Scene complexity, dynamic objects and effects can affect frame rate; test one change at a time to see which makes a difference.
Try: reduce scene complexity, reuse assets, and simplify expensive effects. Test the same gameplay sequence on your target devices after each change.
I cannot find a project or an asset
Cause: assets live in the workspace library rather than as loose files, and project state is versioned, so a change you expected to see may be in a different version or a different place in the library.
Try: search the workspace library for the asset by name, and check that you are in the right project and version. Generated assets land in the library, ready to place, rather than downloading to your computer.
Frequently asked questions
- Why does my game load on one computer but not another?
- Browsers and devices differ in graphics and network support. Gessa uses WebGPU where available and falls back to WebGL2, so an unsupported browser, disabled hardware acceleration or a restricted network can block loading. Test on a current, compatible browser with hardware acceleration on.
- Why can a friend not open my game?
- Check that you shared the published play page for the intended version. Open that link outside the editor and compare what you and your friend see before trying another change.
- Why does multiplayer look different for each player?
- Check the game version, connections and specific shared action with both players. Gessa’s server-authoritative runtime owns the shared simulation; comparing both views helps distinguish the intended rule from what actually happened.