Saving, files and accounts
A project is one portable .sim file. The studio checks for save conflicts, keeps an automatic draft in the browser, and stores it in your private encrypted space.
On an empty canvas, Load demo opens scenario-test.sim with 3 AGVs, 7 stations, 2 traffic zones and Plant logic already configured, inside a building dressed with the 3D library. The demo project is the same in both languages and keeps its original names. You can edit it and save a copy in your own space; if your current draft has changes, confirm before replacing it.
The .sim project file
A .sim file contains everything you edit:
- the layout: paths, stations, links, traffic zones and annotations;
- the scenario: fleets, stations reserved to fleets, speeds, orders, dispatch rules, battery and the Plant logic diagram;
- the prepared CAD background, so the original DWG or DXF is not needed to reopen it.
It does not contain simulation results, the run comparison, the simulated clock or your browser preferences (language, theme, open panels). Results are kept separately in the Run archive.
The file is versioned and compressed, so it does not show readable JSON in a text editor. Compression is not encryption: anyone who knows the format can decode it. It is portable between installations of the studio.
Saving
- Save (top right, or Ctrl+S) writes all changes to the open
.simfile. A new or imported project asks for a file name ending in.simthe first time. - Duplicate project in the project menu creates a new file and never overwrites an existing one.
- Saving an existing
.simdoes not create an automatic backup. You can delete backups created by earlier versions from Project → Manage storage. - Save is disabled while a field holds an invalid value: correct it or press Esc in the field.
The save state next to the button shows Saved, Unsaved, Saving…, Not saved (a project never saved) or Fix the fields.
Conflicts
If the file changed on the server since you opened it, for example saved from another tab, Save refuses to overwrite it. Your draft stays intact: use Duplicate project to keep your version under another name, or reopen the file to continue from the newer version. Changes are never silently overwritten.
Opening, importing and exporting
| Command | What happens |
|---|---|
| Open project | Lists every project saved in your private space, ten per page, with its format (SIM or legacy JSON), last change and file size; the most recently changed come first. Click a column heading to sort by it and click it again to reverse the order. Click a row to open that project; the one already open is marked Open. Esc closes the window. |
| Import project | Reads a .sim file or a legacy JSON layout from your computer. The first save creates a new file in your private space; the original file on your computer is never written. |
| Download .sim copy | Downloads a copy of the current project as .sim, including unsaved changes. |
| New project | Starts an empty project. |
Whenever an action would replace unsaved changes, the studio asks for confirmation first.
Automatic draft and recovery
The studio keeps an automatic draft of the open project in the browser (IndexedDB), including valid unsaved changes and CAD backgrounds. After a refresh or a crash, the last project comes back with a notice such as Draft recovered. Press Save to update the project.
- The draft lives in the same browser and at the same address only. Do not switch browser or clear site data if you need it.
- It is not a saved file: press Save or Download .sim copy to keep your work.
- The simulation clock and results are not restored.
- Hover the save state to see whether the draft is protected. If the browser refuses storage, an error asks you to save before closing.
Legacy JSON layouts
AGV layouts in the older JSON format can be opened or imported. On the first save, the studio creates a new .sim file and leaves the source JSON untouched. Field names and casing (Settings, Segments, StartVector, MapResolution…), unrelated fields and operational settings are preserved. Operational fields such as actions and FTP settings are kept in the file but are never executed or sent to vehicles.
Undo and redo
Undo (Ctrl+Z) and redo (Ctrl+Y or Ctrl+Shift+Z) cover the whole project: layout, scenario, Plant logic and background. Each completed gesture is one step. View changes, language and theme are not recorded. In text fields, undo keeps its usual text behaviour.
Requesting a demo
The studio opens only after you sign in. To see it first, request a demo with the form at the bottom of the home page, or write to info@agvsimulationstudio.com: the sales team replies by email. The former address agvsimulationstudio.com/demo now leads to that form.
Accounts
At this stage, AGV Simulation Studio is available by invitation only. To find out more, contact our sales team at info@agvsimulationstudio.com. If you received an invitation, choose Create your account on the sign-in screen, or open the link in the email.
Administrators have Project → Manage users in the project menu. The table shows accounts and access status: press Approve to admit a user or Block to suspend access. Blocking applies on the next server request. The Storage used column shows MB used and the percentage of the 200 MB quota, including projects, backups and archived runs on the server. Use Sort by to choose registration order or storage from low to high or high to low; storage sorting includes every account, even beyond the first page. Unavailable indicates a failed reading and stays last in both storage sort orders. Use Refresh user list to reload registrations and usage, and the page buttons to browse beyond 50 accounts. Administrators cannot be blocked from this panel. These actions do not change the project or reset the simulation.
A new account can be created only with the email address of a valid invitation. Registration asks for the email address the invitation was sent to, then the six-digit code, then a username, a password and its repeat; email and code are checked together, without revealing first whether an address was invited. The password needs at least 10 characters with a lowercase and an uppercase letter, a number and a symbol: the requirements stay beside the field and a bar shows its strength from Weak to Strong. An account created this way is already confirmed and approved, and you go straight in. With Google or Microsoft, use the invited address and enter the code after signing in. When approval is enabled, new accounts accept the invitation or wait for the administrator before using the studio. Accounts created before the activation date keep access. After email confirmation, the waiting screen lets you Check access, enter a code under Have an invitation code? when the service is configured, or sign out. Once approved, finish choosing your username; until then use your email to sign in with a password. With email configured, the administrator receives a notification for each registration and the user receives an approval confirmation. To close an account that is still awaiting approval, contact the administrator through the privacy notice.
In Manage users → Invitations, press New invitation, enter the recipient's email, choose the language and press Send invitation. The recipient opens Create your account in the email, which takes email and code straight to the username and password step, or enters them from the sign-in screen. Someone who already has an account types the code on the waiting screen after signing in. The code is typed into the six boxes or pasted whole into any box (Ctrl+V). Typing advances automatically; Backspace and arrow keys let them correct digits. New codes have six digits (including any leading zeros), are single-use and expire after seven days. Existing long codes remain valid until expiry. After five incorrect codes for the same email, wait 15 minutes before trying again; blocked accounts must be restored by the administrator. The link is kept in the same tab across OAuth; if you change tabs, reopen the email or copy the code.
Awaiting acceptance shows one invitation per recipient: the latest, if pending or expired. Accepted lists those redeemed; History keeps all invitations, including revoked and previous versions, with no actions on historical rows. Search email searches the entire list, including beyond the first page; view counts follow the search. New invitation opens the form and preserves its draft when closed. The Email status column shows the sending state: Send accepted means accepted by the email service, not confirmed inbox delivery. The list refreshes every 30 seconds while the panel and page are visible, without interrupting a confirmation. Resend asks for confirmation and lets you choose the language; the new code invalidates the previous one. Revoke invitation prevents the code from being used. To suspend access already granted, use Users → Block. At most 100 invitations per day and one per minute per address are allowed.
Each user has an account and a private project space.
Open the online studio at agvsimulationstudio.com/app. Visits to the previous Render address are redirected to this domain.
- Sign in with email and password, or with Google or Microsoft when enabled. New passwords need at least 10 characters with a lowercase and an uppercase letter, a number and a symbol. Forgot password? takes your email or username and sends a link to choose a new one, entered twice; the answer is the same whether or not the account exists.
- Username: chosen during registration, or after the first sign-in with Google or Microsoft (3–32 characters, starting with a letter; letters, numbers, period, underscore or hyphen). You can then sign in with username and password too.
- Storage and deletion: Manage storage shows the 200 MB cloud quota per account, shared by projects, any older backups and archived runs. You can delete an existing backup or a project with all its backups. If you delete the open project, the draft remains in the browser: export it or save it with a new name. To close your account, enter your username and confirm: server files and the Supabase user are permanently deleted; the draft and pending runs are removed from the current browser.
- Signing out: the project menu footer shows who is signed in and a Sign out button. Save the changes you want to keep first.
- Privacy: projects, any older backups and the username index are encrypted on the server (AES-256-GCM) and traffic uses HTTPS. The browser draft is kept per account but is not encrypted by the app, and exported
.simfiles are not encrypted. This is not end-to-end encryption. - Limits: each uploaded file and each save request is limited to 100 MB, so very large CAD backgrounds may need to be reduced. Sharing projects between users and simultaneous editing are not available.