VRScene Files (.vrscene)

VrScene Files created by Golaem Crowd (either from the Render Proxy or from the Simulation Exporter) defines how V-Ray should handle the exported Simulation Caches and render them as Crowd Characters. Here's how those information are stored in the .vrscene file for the following example:

And the corresponding .vrscene file:

// VRay node containing the association geometry <-> material
Node rendercrowdField1@node
    // Notice that this transform has no influence on the rendered characters (see below)
    transform=Transform(Matrix(Vector(1, 0, 0), Vector(0, 1, 0), Vector(0, 0, 1)), Vector(0, 0, 0));

// Golaem Crowd character rendering properties
GolaemCrowd rendercrowdField1@mesh1
    // Transform to apply on top of the Simulation Cache (below means neutral transform)
    glmTransform=Transform(Matrix(Vector(1, 0, 0), Vector(0, 1, 0), Vector(0, 0, 1)), Vector(0, 0, 0));
    // Frame offset to apply to the current frame
    // Simulation Cache attributes (CrowdField name, cache name, cache dir)
    // Characters Files used in the rendered Simulation Caches (separated with ;)
    // Motion Blur attributes
    // Subdivision Surface attributes
    // Render Stats attributes
    // Frustum Culling attributes
    // Misc Attributes
    // List of lights which will influence the crowds (if none, all scene lights are used)
    // Log level
    // Dcc Package in which the crowds will be rendered (0 for Maya, 1 for 3Ds Max)

When generating the .vrscene file with the VRay Render Proxy, all those attributes are filled automatically depending on the Proxy node attributes. When generating the .vrscene with the Simulation Exporter, only the attributes listed in the tab are filled. The other attributes are created with their default value.

Notice that the VRay Render Proxy and the Simulation Exporter both generates only one .vrscene per simulation (as it is not required to specify the current frame to render within the .vrscene)