Stop, restart and update

Stop the app

1. Click Menu in the top bar and choose Quit app.
2. If the scene has parts in it, the app asks whether to save first. Choose to save, to quit without saving, or to cancel.
3. The page says that MeshOptimiser is closed and the server has stopped. On Windows the launcher window closes by itself.
4. Close the app window if it is still open.

Closing the app window stops the server too: about ten seconds after the last window has closed, the server stops by itself and the launcher window closes with it (a server started with the option --keep-running is the exception). You can also stop it from the launcher window: click it and press CtrlC, or close that window.

Start it again

Double-click start.bat or start.command again. The launcher finds the .venv folder from the first run and reuses it, so the app is ready in a second or two.

With the start screen’s resume option on, the file you had open last is offered at the top of the start screen. See Settings.

Update to a new version

From version 0.22.0 the app can update itself, and only itself: a few megabytes of the app’s own files, not the Python environment.

1. Open Settings and choose Updates. The app also checks by itself when it opens, if enough time has passed since the last check (you choose how often), and a small card in the corner says when a newer version is out.
2. Read what is new, then press Update now. Press Later or Skip this version on the card if you would rather not.
3. The app downloads the new files, checks them against a fingerprint, replaces only the files that changed and restarts. Save your scene first: the restart closes the window.

Your scenes, your settings, the inbox and exports folders and the Python environment are never touched. One earlier version is kept, so Earlier version in the same section puts it back with one press. If the new version never gets a working window up in three starts, the app puts the old one back by itself.

A check downloads one small file from the website, xpayn3.github.io, that lists the newest version. Nothing about you, your computer or your models is sent. The update itself comes from the releases on GitHub. In Settings, Updates you can switch the automatic check off, choose Stable or Beta, and turn off the notice in the corner. If a release changes the launcher files (start.bat, start.command), the app cannot replace them while they run, and it tells you to download the full zip instead. v0.31.0 is such a release: it moved the program into the folder app, so an installed copy older than that is offered the full download once, and the installer moves your inbox and exports into the new place.

Updating a version before 0.22.0

Those versions have no updater, so the first move is by hand. A new version is a new zip. This is a suggested way to move over, based on how the app stores things:

1. Quit the app.
2. Download the new zip and unpack it into a new folder, next to the old one.
3. If you want to keep converted files, copy them out of the old folder’s inbox folder (inside app from v0.31.0 on).
4. Start the new version with its launcher. The first start sets up its Python environment again and takes about three minutes.
5. When you are happy with the new version, delete the old folder.