---
title: "Proxy Scene"
canonical: "https://documentation.chaos.com/space/VRHINO/116129837/Proxy%20Scene"
format: markdown
---
This page provides information on the V-Ray Proxy Scene Geometry object.
## **Overview**
---
## **UI Paths**
---
## **Importing a V-Ray Scene**
---
## **Exporting a V-Ray Scene**
---
You can export either the whole scene or a selection of objects as a .vrscene file.
> ℹ️ Exporting multiple objects as a .vrscene proxy is possible only when they are grouped together or included into a single component.
> ℹ️ Exporting multiple objects as a .vrscene proxy is possible only when they are grouped together or included into a single component.
### **Exporting Through the Asset Editor**
---
### **Exporting Through the Toolbar Button**
---
## **VRayScene Parameters**
---
## **Animation**
---
## **Notes**
---
- Any external assets associated with the imported *.vrscene* file need to be accessible (have valid paths) for proper render results. Such assets may include image, .*ies or *.*vrmesh *files. Alternatively, the assets need to reside in the same folder as the .*vrscene *file.
- Certain effects, such as displacement, are not supported for VRScene files exported using V-Ray 3.6 or earlier.
- Proxy Scene files exported from V-Ray 3.6 for Grasshopper cannot be rendered with the Next version (v4.0 or later) of V-Ray Standalone, V-Ray for Rhino or V-Ray for Grasshopper. There are two workarounds available:
- Open the .gh scheme(s) and re-export the .*vrscene* files using V-Ray Next;
- Manually edit each affected .*vrscene* file.
- V-Ray Proxy Scene can be instanced by using the *_Array* command or Alt+drag in the Rhino viewport.
- Memory usage can be viewed from the [Stats section](https://docs-chaos.atlassian.net/wiki/spaces/VRHINO/pages/116129852/V-Ray+Frame+Buffer#Stats) of the new V-Ray Frame Buffer.