Skip to main content

Upgrade Guide

VirgoMotion is distributed as an experimental version (-exp), and an upgrade can change the format of saved data, so some of your previous settings or live scenes may not carry over. This page summarizes, for each version with a breaking change, what's lost and what to redo after upgrading.

tip

If you're upgrading across multiple versions, check every version newer than your current one.

Before You Upgrade​

  • Back up your live project folder. Files used for streaming — live scenes, avatars, sets, props, etc. — are all kept in this folder (see Live Project).
  • For settings that won't carry over (see "What's Lost" for each version below), it helps to take a screenshot or note them down before upgrading, so you can redo them easily.

Changes and Steps by Version​

0.26.0 ← 0.25.3​

What's Lost

  • The shadow and parent (follow target) settings for lights saved in existing live scenes. The shadow setting changed from on/off to a choice of shadow type.
  • Fusion settings (webcam enable, height, blink calibration, receive channel). This is because where these settings are saved moved to the folder of the live project you have open.
  • Prop presets (*.preset.json). These can no longer be loaded.
  • Props contained in live scenes saved before 0.23.5.

What Changed

  • The screen's background type/color, and VirgoMotion reception's UDP port, playback delay, camera height, and camera distance are now saved to the project settings (per-PC settings) instead of the live scene. They no longer change when you switch live scenes.
  • Props are now scene objects placed from the "+" in a live scene. The Props page is now a list of prop files, and adding/removing and configuring props happens in the live scene. Live scenes saved from 0.23.5 onward carry over their avatar, stage, and props as-is.
  • Save as Preset in the Remote App was removed; avatar settings are now saved automatically. Previously saved avatar presets can still be loaded.

What to Do

  1. Re-set the shadow type and parent (follow target) for lights, then save the live scene again.
  2. On the Remote App's Capture / Fusion page, re-set webcam enable, height, blink calibration, and receive channel.
  3. If you had changed the background or receive port, re-set them in the project settings.
  4. If you were using prop presets, re-place the props from the "+" in the live scene and save the live scene.

0.25.3 ← 0.24.3​

What's Lost

  • The attachment point (socket) for props or cameras attached to an avatar may come loose. This is because socket names have changed (e.g. Head → S_Head).

What Changed

  • The Fusion app now runs in a windowed app.

What to Do

  1. Re-select the attachment/follow target for props and cameras, then save the live scene again.

0.24.0 ← 0.23.6​

What's Lost

  • Expression key assignments set on the Expressions page. This is because of a move to a new operation system.
  • Props exported (.prop.lsb) with an older version will no longer work correctly.

What to Do

  1. Recreate expression key assignments on the Operations page (see Operations).
  2. Use props that have been re-exported with the latest SDK. For distributed props, get a newer version from the distributor.

0.23.6 ← 0.23.5​

What's Lost

  • The warp-to-mark setting specified in a Placement object (Avatar Placement). This is because the mechanism changed to a per-set warp.

What to Do

  1. On the Stage page, re-specify the warp destination mark from the set's details, then save the live scene again (see Stage).

0.23.2 ← 0.22.1​

What's Lost

  • The background (world) setting for live scenes saved in the old structure (world / scene bundle). This is not migrated automatically.

What Changed

  • The "World" page became the "Stage" page, and the background scene (world) is now called a Set. The previous .scene.lsb can still be loaded.

What to Do

  1. Reload the set on the Stage page, then save the live scene again.

0.21.3 ← 0.21.1​

What's Lost

  • Avatars exported for the older URP build may fail to load. This is because the Studio app is now a Built-in RP build.

What to Do

  1. Re-export the avatar with the latest VRChat Avatar Transfer.

0.20.1 ← 0.19.0​

What's Lost

  • Some data from scenes saved with an older version. This is because the scene structure changed.

What to Do

  1. Open the scene, check its contents, redo any missing settings, and save it again.

0.19.0 ← 0.18.2​

What's Lost

  • All data saved with an older version. The scene format is not compatible.

What Changed

  • The Avatar, Screen, and Background pages were removed and merged into the Scene page.

What to Do

  1. Recreate your settings on the Scene page and save.

0.12.0 ← 0.11.0​

What's Lost

  • Edited expression data.
  • The license you had entered.

What to Do

  1. Set up expressions again.
  2. Enter your reissued license (see Configure License).