Handling failed to apply virtual background

Windows

triangle-exclamation

You may encounter this error when attempting to apply a virtual background in PRISM Lens. This occurs when the program fails to properly recognize the core model files required for background detection.

Error Screen


Cause

This issue is typically caused by the following factors:

  • Missing or Corrupted Files: Essential model files were not installed correctly or became corrupted due to disk errors.

  • Installation Path Issues: The installation path contains special characters or is too long, preventing the app from accessing the files.

  • Insufficient Disk Space: Lack of storage on the installation drive prevented the package from decompressing properly.

Solution

1

Reinstall PRISM Lens

  1. Uninstall the current PRISM Lens from your Control Panel.

  2. Download the latest version of PRISM Lens from the official website.

  3. Complete the installation and check if the virtual background feature works correctly.

2

Check the Installation Environment

If the issue persists after reinstallation, please verify your system environment:

  • Verify Installation Path: Ensure the path does not contain special characters and try to use the default installation directory.

  • Clear Disk Space: Ensure there is sufficient free space on your installation drive.

3

Manually Verify the Model File

If the steps above do not work, please follow these steps to manually verify if the required model file exists in the installation path.

  1. Right-click the PRISM Lens shortcut icon on your desktop.

  2. Click [Open file location] from the menu to go to the PRISMLens installation folder.

  3. Within that folder, navigate through the following subfolders in order:

    resources > app.asar.unpacked > node_modules > core-node > data > models

  4. In the final models folder, check if the file named algo_ggl8pgg5cal0pcvpka.model is present.

    1. If the file is missing: It indicates the installation package did not unpack correctly. Please attempt to reinstall the app once more.

Reference

Last updated

Was this helpful?