Bug: VRayScene nodes — referenced assets inside .vrscene files are not detected or uploaded

[oehmends]

Describe the bug

When submitting a Maya scene that uses VRayScene nodes (which reference external .vrscene files), the submitter detects and uploads the .vrscene file itself, but does not parse its contents to discover the textures, geometry proxies, IES lights, and other assets referenced inside it. Additionally, on the Linux worker, the paths inside the .vrscene file are not remapped from Windows paths to the session's asset root paths, causing V-Ray to fail loading all textures.

This affects any V-Ray for Maya workflow that uses VRayScene nodes to reference pre-exported vrscene files containing materials and textures.

Expected Behaviour

1. Submitter: The asset introspector should parse .vrscene files referenced by VRayScene nodes and include all discovered assets (textures, proxies, IES files, etc.) in the job's input file list for upload.
2. Adaptor: On the worker, the paths inside .vrscene files should be remapped using the Deadline path mapping rules before V-Ray reads them, so that textures resolve correctly on Linux.

Current Behaviour

1. Submitter: Only the .vrscene file itself is uploaded. Textures, proxies, and other assets referenced inside it are not detected.
2. Adaptor: V-Ray reads the .vrscene file with the original Windows paths (e.g. Z:/bib/cgi/.../texture.png or //server/share/.../texture.png), which don't exist on the Linux worker. All textures fail to load and the render output is grey.

Key issues encountered during implementation:

• The vrscene format can be compact (all params on one line) or multi-line — the parser must handle both
• UNC paths (//server/share/...) must not be stripped by comment removal (// is also the comment prefix)
• Maya's dirmap does not remap paths inside vrscene file contents — only the node's FilePath attribute
• dirmap(getAllMappings=True) returns corrupted mappings on Linux — raw rules must be stored separately
• Path prefix replacement must be case-insensitive (Windows/UNC paths are case-insensitive, V-Ray may change casing)
• Trailing separator normalization is required to avoid missing / in replaced paths

Reproduction Steps

1. Create a Maya scene with a VRayScene node referencing a .vrscene file that contains texture references (e.g. BitmapBuffer with file="Z:/path/to/texture.png")
2. Submit the job via Deadline Cloud submitter
3. Observe that textures referenced inside the .vrscene are not in the uploaded asset list
4. On the worker, V-Ray logs warnings like: Bitmap file "Z:/..." failed to load: error reading file:2: file does not exist
5. The rendered output is grey (no textures)

Environment

1. Windows 10/11 (submitter), Amazon Linux 2023 (worker)
2. Maya 2025
3. V-Ray 7.10.00 for Maya
4. deadline-cloud-for-maya (current mainline)

[loachri]

Thank you for opening this issue! My understanding is that you have a fix on the way for this bug, and that it is currently not blocking anything. If not, please correct me. Otherwise, looking forward to reviewing your contributions!