Frequently Asked Questions

Here are some frequently asked questions and their answers regarding VirtualLens2.

Introduction

First, please check for updates in the change log and the download page on Booth to see if there are any updates available. If you are experiencing issues with VirtualLens2 or if the symptoms are due to changes in VRChat client and/or SDK, these issues may have already been fixed by an update.

Setup-related Questions

My avatar’s expressions or gimmicks broke after installation.

In most cases, this is due to the “Write Defaults” settings. Adjust the “Enable Write Defaults” setting within VirtualLens Settings > Advanced Settings appropriately and reapply. You can find more information about “Write Defaults” in the VRChat official documentation.

VirtualLens2 tries to automatically adjust the settings based on the existing FX Layer’s Animator Controller during the setup. However, in cases like the following, it may fail to determine the settings, and manual adjustments are required:

You changed the settings after the setup. There was a mixture of “Write Defaults” settings during the setup.

Changing the Menu Item Installation Location

When using a non-destructive setup, adding the “MA Menu Installer” component to an object that has the VirtualLens Settings component allows menu items to be added according to its settings. By configuring the “Install To” parameter of the added component correctly, you can change the installation location of menu items.

Operation-related Questions

When I switch to Drone Mode, the camera flies off somewhere.

VirtualLens2’s drone function is controlled using the position of the hand without the camera. Therefore, if you move the controlling hand unintentionally, the drone might fly in unintended directions or at unintended speeds. When transitioning to Drone Mode, try operating the menu with both hands lightly extended forward.

Miscellaneous Questions

I want the camera to be visible to others when using the drone function.

Currently, due to constraints in VRChat, correctly synchronizing the camera’s position with others is challenging. Therefore, it is intentionally configured to not be visible to others.

I want to improve my performance rank.

The current method of calculating performance rank counts even objects that are only used locally, so complex local gimmicks like VirtualLens2 tend to have a worse ranking than the actual load when viewed by others. In most cases, when viewed by others, most objects are never activated, and they don’t significantly contribute to the performance. If VRChat’s specifications change in the future to allow correct handling of local objects, we will provide an update to address this.

Reference: [FEEDBACK] Mark local objects explicitly and exclude them from performance rank calculation

Certain worlds may be rendered incorrectly

Due to the effects of post-processing settings or shaders functioning as effects within the world, depth-of-field simulation of VirtualLens2 and/or other effects may not work correctly. While ongoing improvements aim to ensure proper functionality, certain technical constraints remain unresolved. As of now, the following combinations are known to cause rendering issues:

Features that may critically impact VirtualLens2 Usage

  • Post-Processing: Depth Of Field
    • The captured image may appear overly blurred.
  • Objects highly affected by weak directional lights
    • When VirtualLens2 is active, it enables a light source, which can significantly alter the appearance of such objects.
    • In some cases, users may bypass this issue by temporarily disabling depth texture generation.

Features that may render ineffectively with VirtualLens2

  • Post-Processing: Ambient Occlusion
  • Post-Processing: Motion Blur

When Things Go Wrong or You Don’t Understand

If you encounter issues or have questions, please contact via the messaging system on Booth or through Twitter DM. Since image sharing is often necessary, contacting via Twitter DM is recommended. In your message, please include the following information to help streamline the communication:

  • Whether there were any errors displayed in the console when you clicked the “Apply” button.
  • Screenshots of the VirtualLensSettings.
  • Screenshots of the VRC_AvatarDescriptor.
  • Screenshots of the AV3 Debug screen in VRChat (can be displayed by going to Puppet Menu > Options > Config > Debug).