Early Access 0.1.0 · free on Meta Quest · last checked 18 Nov 2026
GILLA VR Guide

Known issues

Quick answer

Most reports in the first week are one of three things: the game says you are offline, nobody can hear you, or a room will not load. Restart the game first, then the headset, then check the Meta mic permission before anything else.

Checked 18 November 2026 against the Meta Quest store reviews, the game's privacy policy and gillavr.com.

Three problems account for most of the complaints in GILLA's first week, and only one of them is a bug you cannot do anything about. This page is the ordered list: cheapest fix first, reinstall last.

The issue table

SymptomLikely causeTry this first
"It says I'm offline" and joining failsSession or account stateFull restart of the game, then the headset
You hear nobody in a busy roomMicrophone permission or audio routingPlatform mic permission, then output device
Nobody hears youSame, from the other sideCheck your own mic before blaming the room
A private room will not loadCode or room stateTry a public room to isolate it
Dropped mid-roundSession validationRejoin; if it repeats, restart
Stuck on the loading sequenceUpdate check at launchClose the game and relaunch
Game will not updateLaunch-time version checkCheck the store for a pending update

1. The offline state

This is the most-reported problem in the first week and the most disruptive, because it does not look like a bug from inside the headset. The game tells you that you are offline and refuses to join.

The order that resolves it for most players:

  1. Back out to the lobby and try a public room. If a public room works, the problem was the private room.
  2. Close GILLA from the system menu. Not the back button: close it.
  3. Restart the headset. This is the step reviewers credit with fixing it.
  4. Relaunch and join a public room first. Then try private.

One reviewer reports it clearing "the next day", which suggests a server-side or account-side timeout rather than anything you did. If all four steps fail, stop reinstalling and come back later.

2. Silent voice chat

A room where nobody can be heard is usually three separate problems wearing one costume.

  • Permission. The headset grants microphone access per app. If GILLA is not allowed, nothing in the game will tell you.
  • Routing. If you are casting to a phone or TV, audio may follow the cast rather than staying in the headset.
  • Position. Voice is positional and comes out of your ape's mouth. Two rooms apart is genuinely quiet.

Work through when nobody can hear you before you change anything in the game.

3. Rooms that will not load, and drops mid-round

GILLA's sessions run on Photon servers in the western United States, and the developer's privacy policy describes an anti-cheat validation called ShiftAuth that runs roughly every thirty seconds while you play. A drop mid-round fits that shape: the session was fine, then the check failed, then you were out.

What you can control:

  1. Your connection. Wired or close to the router is not optional in a game where a dropped frame moves your body.
  2. Your region. If you are far from the US west coast, expect more validation hiccups than a player in California.
  3. Your patience with the retry. Rejoining immediately after a validation drop is sometimes the thing that keeps you out.

4. The launch-time update check

The developer's privacy policy says the game fetches a version file when it starts, to decide whether it needs updating. That is why a stale build can sit on "checking the game files" and why the fix for a stuck launch is to close and relaunch rather than wait.

If the store shows a newer version than the one you are running, update through the store. If the store and the game disagree, the store is right.

What not to do

  • Do not reinstall first. At about 1 GB it is not expensive, but it fixes less than a restart does and it costs you ten minutes.
  • Do not factory reset the headset for a join error. Nothing in the reports suggests a device-level cause.
  • Do not blame the room host for a microphone permission problem. That is the most common misdiagnosis in the reviews.

When it is worth reporting

If you hit the offline state twice in a week, report it: the developer's support address is on the game's own site, and the store review section is where the team appears to be reading. A report with your region, your headset model and the exact message is more useful than a one-star review that says "broken".

The broader state of the build, including what the version does and does not include, is in what 0.1.0 actually has.