The forum is active for archival purposes only.

Join our discord community for new topics.

Forum Navigation
Forum breadcrumbs - You are here:ForumPrism: GeneralVray standalone rendering
You need to log in to create posts and topics.

Vray standalone rendering

Page 1 of 2Next

Hi,

When rendering we like to submit vrscenes and render via vray standalone. This is a very clean way and makes sure we only need to install vray on the farm machines. However I can't seem to figure out how to do this in Prism. It seems to submit the .hip file to deadline.

Can anyone help me with this?

Thanks,
Boyo

Exporting and rendering the scenedescriptions is only supported for some renders currently. These include Mantra, Redshift, Arnold and 3Delight. Support for Vray might be added very soon as well.

ok, thanks! This would be really important for us to be able to use prism in production.

We added this feature now. In the next Prism update you'll be able to submit Vray standalone jobs from Houdini to Deadline. There will be 3 jobs, which are dependent on each other: the first one exports the .vrscene files from the .hip file (this job requires a Houdini license), the second job renders the .vrscene files with Vray standalone and the third one is a Python cleanup job, which deletes the .vrscene files.

Thanks!
We would need to do the the first step on the local machine though. Because the farm doesn't have Houdini installed.  Is this possible in this setup?
In our current pipeline, the user presses "render to disk" which writes the vrscenes and then a post-render script get called to send it to the farm.

Currently the export will be submitted as a job to the farm, but it should be easy to add an option for local export in any of the next updates.

ok, thanks! That would be amazing.

Hi,

I was wondering if the local export is coming in a next update? What we're doing now to get around it is this:
- We use prism state manager to set up the render. But we check on "Submit suspended". So it set's all the paths in the ROP, but the jobs don't actually get executed. We then delete this job in deadline. Only use it to set paths.
- Then we use the vrayDeadline node to actually submit the ROP to deadline. There we check on "Export Locally/Render job"

It works kind of, but is a bit of a hassle and prone to human errors. Would be great is prism could work just like the vrayDeadline node, where when you hit publish it would export vrscenes locally and then only send the vray render job to the farm.

Uploaded files:
  • You need to login to have access to uploads.

Yes in the next update there will be a new option in the State Manager to export the scene description locally before submitting the render job to Deadline.

That update should be released later this month.

awesome, thanks!

Page 1 of 2Next