Other Color for Bucket Color Possible?

[Uhlhorn]

Hi there,

is it possible to change the color for the bucket frames? Mostly they are hard to see, because I am rendering product shots all the time and they have white backgrounds.

[vladimir.nedev]

Not possible at the moment, the white bucket color is hard-coded.
Currently you can change the VFB background color by right-clicking outside the rendered image.
We could add options for the bucket color there as well.

Greetings,
Vladimir Nedev

[Uhlhorn]

I like the colors in Modo. But better as the colors in Modo would be variating colors for each render node.

I have to test V-Rays network rendering too. But actually I am testing V-Ray in general. (And I do not know how to setup network rendering. I have to lern it.)

[vladimir.nedev]

Not sure if we have it in the docs, but setting up distributed rendering is pretty simple (once you know what to do).

1. Install V-Ray for MODO on the render slave/server

2. Start the server
a. Under Windows, the Start Menu entry for V-Ray for MODO, has a Launch V-Ray render slave command, which will start the slave/server
b. Under Mac OS X, open a terminal, cd to /Applications/ChaosGroup/V-Ray/MODO_x64/vraysl (or wherever you installed) and execute ./vray.bin -server

3. On the client machine, open the Preferences in V-Ray for MODO (the P button in the V-Ray Toolbar) and enter the IP or network name of the slave machines.
You can separately enable DR for production and for RT CPU/GPU.

Enabling DR will (by default) add a separate render element where buckets are colored based on the server/slave that rendered them.
Also in DR mode, the server/slave name is printed in the top-left corner of each bucket.



Greetings,
Vladimir Nedev

[Uhlhorn]

This is not working. V-Ray is not using my server.
And the setup is not easy. It would be better if V-Ray would use a zero config network setting like bonjour. (This is a feature request.)

Network rendering in Modo is easy to use: Select „Use Network Render Nodes“ in the preferences and start the remote Modo in render slave mode. Thats all to do. It works like a charm.

[vladimir.nedev]

This is not working. V-Ray is not using my server.
And the setup is not easy. It would be better if V-Ray would use a zero config network setting like bonjour. (This is a feature request.)

Network rendering in Modo is easy to use: Select „Use Network Render Nodes“ in the preferences and start the remote Modo in render slave mode. Thats all to do. It works like a charm.

Yep, it would be nice if you didn't have to manually input the IP address of the network nodes.

You can check the Event Log in MODO to see what the issue might be.
Also the terminal on the render server might have information (like license not available or something).

Greetings,
Vladimir Nedev

[Uhlhorn]

This is the terminal output. It seems to be a license problem.

[2016/Jan/12|20:48:56] Starting DR session from 10.0.1.127
[2016/Jan/12|20:48:56] Receiving DR scene from 10.0.1.127
[2016/Jan/12|20:48:56] Reading scene file "/var/folders/8h/2_4rvnkd3hsfnwtmtrtfgv44000103/T/vrscene_diZl5y.txt"
[2016/Jan/12|20:48:56] Scene file parsed successfully in 0.0 s.
[2016/Jan/12|20:48:56] Scene created successfully.
[2016/Jan/12|20:48:56] Objects in scene: 0
[2016/Jan/12|20:48:56] Starting render sequence.
[2016/Jan/12|20:48:56] Preparing renderer...
[2016/Jan/12|20:53:00] error: Could not obtain a license (-65533).
[2016/Jan/12|20:53:00] Closing DR session from 10.0.1.127
[2016/Jan/12|20:55:50] 
[2016/Jan/12|20:55:50] Starting DR session from 10.0.1.127
[2016/Jan/12|20:55:50] Receiving DR scene from 10.0.1.127
[2016/Jan/12|20:55:50] Reading scene file "/var/folders/8h/2_4rvnkd3hsfnwtmtrtfgv44000103/T/vrscene_S8Yqhz.txt"
[2016/Jan/12|20:55:50] Scene file parsed successfully in 0.0 s.
[2016/Jan/12|20:55:50] Scene created successfully.
[2016/Jan/12|20:55:50] Objects in scene: 0
[2016/Jan/12|20:55:50] Starting render sequence.
[2016/Jan/12|20:55:50] Preparing renderer...
[2016/Jan/12|20:57:30] error: Could not obtain a license (0).
[2016/Jan/12|20:57:30] Closing DR session from 10.0.1.127 

[vladimir.nedev]

You have to setup licensing for the render server/slave just like for the client machine. I know, it gets more and more complicated.

You can point the render server/slave to the client machine (where the license server should already be running).
Easiest way to do this would be to do it during installation. Just select Customize during install, choose "Remote V-Ray license server on the network" and enter the IP of your client/main machine.

Or you could install the license server on the servers/slaves as well.

You need a separate V-Ray Render Node 3.0 Beta license for each machine.
support will add as many as you want to your account ( up to some quite big limit ), but normally these licenses come at an additional cost.
They are universal across V-Ray 3.0 integrations (Max, Maya, MODO, etc...).

Greetings,
Vladimir Nedev

[Uhlhorn]

You can point the render server/slave to the client machine (where the license server should already be running).
Easiest way to do this would be to do it during installation. Just select Customize during install, choose "Remote V-Ray license server on the network" and enter the IP of your client/main machine.

This is what I made. But I will not run.

You need a separate V-Ray Render Node 3.0 Beta license for each machine.
support will add as many as you want to your account ( up to some quite big limit ), but normally these licenses come at an additional cost.

Oh, I wanted to test it only, because I want to find bugs. I have to test it intensive, because I am looking for an replacement for Modo’s render.

Background:
The rendering of Modo ist really buggy, and it is quite slow. Luxology/The Foundry is not fixing known bugs. They prefer to write new buggy and therefore unusable features instead of fixing the known bugs (902). So I’m looking for an alternative for Modos rendering. V-Ray’s beta is actual more reliable than Modo’s render ever was.

An alternative to V-Ray is perhaps Octane and Maxwell. I will test them too. But V-Ray is well integrated in Modo, and I like this integration very much (I think that’s Your work? It’s well done!).

After receiving my eGPU I will give a short test to the GPU render Octane, because the GPU support of Octane. But ultimately I think I will buy V-Ray. The results are convincing, the integration is well done.

[vladimir.nedev]

This is what I made. But I will not run.

Maybe you have only 1 render license on your account. I am not sure how many they give you by default, I think the registration form has you enter an amount, might be wrong.

Check the license server status page : http://localhost:30304/#/online
It will tell you how many licenses you have.

It might be a firewall issue as well if you use one.

Greetings,
Vladimir Nedev

[Uhlhorn]

[vladimir.nedev]

Yep, only 1 render license. You need to send an e-mail to support asking them to give you more V-Ray Render Node 3.0 Beta licenses for DR testing V-Ray for MODO.
You need to include your chaosgroup.com (not the forum one) user name in the e-mail.

Greetings,
Vladimir Nedev

[BVA]

This is not working. V-Ray is not using my server.
And the setup is not easy. It would be better if V-Ray would use a zero config network setting like bonjour. (This is a feature request.)

Network rendering in Modo is easy to use: Select „Use Network Render Nodes“ in the preferences and start the remote Modo in render slave mode. Thats all to do. It works like a charm.

PLEASE don't change the way vray net render work! It is actually really easy to setup once you know how. The big advantage is it is SUPER STABLE.... Modo's netrender is easier but not that stable. Mostly the only difficulty for me is adding an exception to my firewall, once that's done it always work and reliable too.

[Uhlhorn]

deleted (double post)

[vladimir.nedev]

What's that ? The licenses didn't get updated ?
You will have to ask support what's going on, I don't work on the development of the online license server and have no idea what issues might arise there, or how to fix them.

Greetings,
Vladimir Nedev