Different setups for PC and Quest

When to use this

You upload a PC version and a Quest version of one avatar, and some pieces or effects should exist on only one of them. Do not delete the toggles from one copy. VRChat syncs parameters by their place in the list, not by their name, so both versions must have the same list. If they do not, players on the other platform see the wrong toggles.

Set the platform of an entry instead. On the other platform, the entry builds no menu control and no layers, but its parameter keeps its place. Parameters, sync and memory explains why the order matters.

This needs Advanced mode, the default.

Steps

For the whole component

1. In the Hierarchy, select the object that holds your AvatarDoc component.

2. In the inspector's header, open Component settings.

3. In Platform, choose Both, PC only or Quest only.

   Under it, a note says which platform the editor builds for right now, such as Building for PC.

For one entry

1. In the tree, select the entry.

2. In its panel, open the Advanced fold.

3. In Platform, choose PC only or Quest only.

   In the picture, 1 is the chip the row gets, 2 the Advanced fold, and 3 Platform.

   On a wide inspector, you should now see a PC only or Quest only chip on the entry's row. The tree shows these chips only while it is at least 360 pixels wide, except on an entry that is left out on the platform you build for: that one shows its chip at every width.

Inherit, the start of every entry, takes the choice of the submenu the entry sits in, or the component's. A submenu's choice counts for everything inside it, until an entry inside picks its own. With Inherit, triggers and overrides take the component's choice. Merged animators, menu assets and the AvatarDoc Shapes component each have their own Platform too.

What decides the platform

AvatarDoc reads Unity's active build target. Android and iOS count as Quest, everything else as PC. Switching the platform in Unity, or in the VRChat SDK's control panel, switches which entries build.

An entry left out on the platform you build for keeps its parameter, with the same name, type and place, and the same synced bits. It loses its menu control, its FX layers and its default in the scene. A trigger also loses its contact receiver, or the parameter it gives a PhysBone. A left out entry takes no place in the menu.

In the tree, an entry left out on the platform you build for is dimmed, and its chip shows in the warning colour. Its Builds line says it builds nothing there, such as Builds nothing: not built for Quest. On a wide inspector, an entry limited to the platform you build for shows a plain chip, so you can see what would go when you switch.

Check it worked

• Look at the tree. Entries left out on the current platform are dimmed, with their chip.
• Keep the PC and Quest copies of the avatar open in your scenes. When their parameter lists differ, the header shows a warning. No warning means the lists match.
• Press Summary in the header. The summary marks every entry that is limited to one platform.

If it does not work

• A warning says this avatar and another one share a blueprint, but their parameters differ at a position: build both from the same menu, in the same order. See the message.
• An entry still builds on Quest: its Platform is Inherit, and its submenu or the component says Both. Or the editor builds for PC: check the note under the component's Platform.
• The other copy shows no warning even though it differs: AvatarDoc compares only avatars that are open in a scene right now, and only copies with the same blueprint ID.

Related

• The inspector at a glance describes Component settings.
• Fit in VRChat's parameter memory explains what each parameter costs.
• A toggle works on PC, but is missing or wrong on Quest in Troubleshooting.