Feature request: Add support for Vray export workflow

[ZainAallii]

Describe the problem

3dsmax submitter does not support exporting the scene out as standalone renderer format. It is common workflow for 3dsmax to export and submit jobs as .vrscene file.

Proposed Solution

1. Add support for local export as a .vrscene file and submitting Vray standalone job to Deadline Cloud.

2. Also add support for submitting a 3dsmax export job and a dependent standalone render job on the farm.

Example Use Cases

#dsmax is only support on Windows instances which are significantly more expensive than Linux alternatives. V-Ray renderer supports both Windows and Linux , creating an opportunity for substantial cost
savings.

Recommended Workflow:

1. Job Export: Export V-Ray render jobs locally or through the render farm
2. Rendering Execution: Process the exported jobs on cost-effective Linux instances

Cost Benefits Based on Spot Pricing: Example
• Windows Spot: $3.86-$4.24/hr for 16xlarge instances
• Linux Spot: $0.92-$2.13/hr for 16xlarge instances
• Potential Savings: Up to 76% cost reduction by rendering on Linux vs Windows

This approach leverages V-Ray's cross-platform compatibility to minimize expensive Windows instance usage for compute-intensive rendering tasks, while maximizing utilization of lower-cost Linux spot instances.
The result is significant infrastructure cost savings without compromising render quality.

[leongdl]

I would like to move feature requests to discussions - #140 (comment)

This will hopefully give a higher view what features to prioritize.