Saving And Working Together

Visual Space manual, Live Apps, Saving And Working Together

This is the read-only HTML version. For the full Visual Space experience, open the app.

Visual Space manual, Live Apps, Saving And Working Together

Visual Space manual, Live Apps, Saving And Working Together

Poly saves completed edits so that you can return to a scene and work with other people. Save feedback tells you whether the latest work has finished, is still uploading, or needs attention.

Poly saves completed edits so that you can return to a scene and work with other people. Save feedback tells you whether the latest work has finished, is still uploading, or needs attention.

Know What Saved Means

Saved is the checkpoint for durable work. A visible change, a responsive viewport, or another person's pointer does not by itself confirm that your latest edit has been saved.

Geometry and textures can need more time than a simple transform. Painting also has two related results: the editable Canvas source and the texture used by Poly. If the source saves but its Poly attachment fails, the work remains pending.

The feedback distinguishes useful states:

•
Saving…, Saving changes, or Uploading means work is still in progress.
•
Changes pending means there is local work that has not finished saving.
•
Read only means you can inspect the scene but cannot author changes in that session.
•
Offline — retained locally means recoverable work is held on this device; it is not a completed remote save.
•
Review conflict, Save failed — retry, or Needs attention means the work needs recovery or review before normal editing can continue.

Wait for the result of a large import, geometry change, or painting session before closing the window. Use the current message to decide what to do next rather than repeatedly making more edits while saving is blocked.

Work in the Same Scene

People with the required access can open the same scene. Accepted changes reach other sessions, and shared awareness can show their pointer, selected object, tool, and view. A second window belonging to your own account is also a separate editing session.

Compatible edits can be combined without replacing untouched parts of someone else's work. This does not mean every simultaneous operation can be merged. Two edits to the same property, competing geometry changes, or changes to a modifier's inputs can conflict.

Coordinate edits to the same mesh. Let one person finish a topology, sculpt, rig, or complex modifier operation before another changes that same object. Simple division of work makes the scene easier to understand and reduces recovery interruptions.

Keep Undo Personal

History follows meaningful actions in your editing session: creating, transforming, grouping, changing surfaces, and other supported edits. Undo and Redo help you explore and correct your own work.

History is not a shared activity log or a browser of every saved scene version. Playback, navigation, hover, and ordinary selection do not create authored scene changes. Do not use Undo as a way to recover somebody else's earlier version.

When Work Needs Recovery

Poly retains eligible unfinished edits and binary work locally and can retry compatible work when a writable scene reopens. Retained recovery belongs to the account, document, and device where that work was made; it is not a substitute for reaching Saved.

Reconnect before trying to continue an offline session. Open the More menu and use Retry saving when recovery actions appear. For a pending painted texture, save again with Ctrl+S or Command+S and wait for the result. When the latest scene no longer matches the work being recovered, Poly keeps the conflict instead of silently replacing the newer content.

When more than one retained session is available, the More menu offers Resume retained changes entries. Choose the session containing the work you want to recover. Open another session starts separately while keeping retained work available; it does not mean that the unfinished edits have been saved or discarded. If a conflict remains after retrying, keep the original local data and report the visible message with the scene name.

Check the Document Details

Use More → Doc Details to inspect the scene title, location, dates, and storage usage. Document rename changes the file title; it is separate from renaming an object inside the scene.

The current scene's stored assets count toward the space allowance, including small public assets. Scene data and saved history do not themselves add to that asset allowance. Removing an asset from the saved document stops it counting there, even if physical cleanup happens later.

Common Questions

Can I edit freely while offline?

Authored editing pauses when the session is disconnected or blocked. Reconnect and resolve the pending state before resuming.

Does retained locally mean another device can open the latest version?

No. Another device can rely on accepted saved work. Local recovery remains tied to the original device and account.

Will refreshing always fix a conflict?

No. A conflict can remain because the scene or geometry changed underneath the unfinished edit. Reopening is not permission to overwrite that newer work.

Does creating the scene publish it?

No. A scene begins as a private document. Publishing an article or feed item is a separate action, and access still follows the scene's space and area rules.

Follow Save and Reopen Your Work for the practical checkpoint sequence.


Visual Space

4 Followers

Meet fellow creators and transform bright ideas into real projects ✦✦✦ or just geek out for the fun of it 😊

Visual Space is built for projects like this—where creators collaborate, organize goals, and grow communities around real work.