VRay build on swarm

[jskt]

Since the commercial release, every VRfR package uploaded to Swarm appears to display the same build information with the wrong hash and timestamp. This makes checking that all nodes have the correct version difficult. Can we get this fixed in future releases?

[Ana Lyubenova]

Can you please indicate the hash and timestamp you considered as wrong?

[jskt]

As visible in the above screenshot, when uploading the newest hotfix's package to Swarm, it still presents as 4.20.01 from last October 1st at 14:12:51; hash ending in c9. Are you saying that the latest hotfix doesn't require an update of the build on Swarm?

It would also be very helpful if instead of [aec], the builds were tagged with the actual application they support (ie [rhino], [revit], etc.)

[Ana Lyubenova]

The V-Ray Core version is shared across the AEC host apps. It basically has nothing in common with the V-Ray version within the app. For example, in the past we had V-Ray 3.60.04 for Revit using the V-Ray 3.6 Core. Then we did some enhancements to the V-Ray integration within Revit, so we had V-Ray 3.70.01 for Revit that was still using the V-Ray 3.6 Core.

Tags per app are simply not applicable because Swarm runs no matter the host app. For example: you can run it out from SketchUp on 2 nodes having V-Ray for Revit and V-Ray for Rhino installed. It will check the V-Ray Standalone versions on each node. If they differ, it will install the one that is used in the host app you run the rendering from (in that particular example, it's SketchUp), and will render. That's it.

Back to the UI screenshots -> the version depicted in the Swarm UI is the V-Ray Standalone version. And it corresponds to the V-Ray Core version depicted in the V-Ray for Revit about window.
V-Ray for Revit itself has a separate version which is not necessary to coincide with the Core version, and it also can't have the same hash.

Now, regarding the other thread you posted in, I guess there is something in your setup that is causing the automatic upload to fail. Are you able to drop a line at support@chaosgroup.com, so that we can schedule you for a remote session?

Best,
Ana