Loftia won't launch or sign in: what to try first

What should you try first when Loftia will not start?

Restart Steam, update the Steam client, then verify the game files. That three-step sequence comes from the support reply on a launch failure (support reply), and it applies to a login that never completes as well as to a game that never opens. On a thread where the game did not reach the title screen, the reply asks for the log file and an email to support first, then lists a Steam update, a file verification and a DNS change as extra ideas (title screen thread).

1. Close Steam completely, or restart the computer.
2. Click the Steam menu and check for a client update.
3. Right-click Loftia in your library, open Properties, then Installed Files, then Verify integrity of game files.
4. Launch again and note whether the failure happens before the logo, at the avatar screen or at login.

If all four steps fail, email [email protected] with your in-game name and what you saw.

Why does “No licenses” appear?

That message came from launching the October Demo build after the Demo period ended. The Demo is no longer playable, so install and start the full game instead — app 2320980, the same listing the buying guide covers. If the full game shows the same error on an account that owns it, treat it as a licensing problem rather than a patch problem.

The game closes at the avatar screen

Try the DirectX 11 option at launch, which Qloud recommends for lower-performance machines, then report the crash with the Loftia.log attached. The bug report form has a “How to find your Loftia.log” section that lists the file path for Windows and Mac.

A crash that repeats at the same character or the same outfit is worth reporting with a screenshot of the avatar screen; the log shows which asset failed.

What if only the login step fails?

Check whether the servers are up before you change anything on your PC. A login error on a working client is more often an outage or an account-link problem than a broken install, and multiplayer and servers explains what the game expects from your connection.

If the error survives a restart and a file check, send support the exact wording on screen, your platform and the time. An account error that outlives a Steam restart, a client update and a file verification is already past the point where local fixes help.

How do you send a report that gets answered?

Use one of the three official routes, and include the log file:

• The bug report form on the website, which accepts the log and explains where to find it.
• The in-game feedback button: press Esc to open the menu hub, then use the button shaped like a person with headphones in the bottom-right corner.
• Email [email protected] with your in-game name, platform and the steps that led to the failure.

The October Demo fix notes are still useful for recognising an old symptom, but they describe a build that no longer runs.

Why does a controller not connect?

Use Steam Input rather than the in-game controller option when a pad is not recognised. A PS5 controller that did nothing with the in-game setting worked once Steam Input was enabled instead. Layouts and Deck notes are in the controller guide.

When is reinstalling a waste of time?

When the game never reaches the world and the log points at your account or a server, a fresh download changes nothing. Reinstalling also costs the full download for a problem that verification already covers. Check the official announcements first, then verify, then send the log — and only reinstall if support asks for it.

If the game runs but stutters or overheats rather than refusing to start, read low FPS and high CPU instead; a blocked objective after a successful login is in stuck quests.