Render Manager 2.1.5

Render Manager Release Logs
#1

Download the latest version from here: https://public.pulze.io/pulze-downloads/pulze_service/2.1.5/pulze_215_win.zip

  • Added new V-Ray Standalone job type
  • Added new Chaos Vantage job type
  • Added new Arnold Standalone job type
  • Added new Fusion job type
  • Added Fusion and V-Ray Swarm options to Spawner Mode
  • Support for 3ds Max 2023
  • Support for Corona 8
  • Support for V-Ray 6
  • Scene Manager 2.2 compatibility
  • Added Render target option to the Job Submitter when V-Ray or Arnold is used as the renderer
  • Added Fusion, Arnold Kick, V-Ray Standalone, Chaos Vantage and V-Ray Swarm to program search
  • Added experimental distributed rendering job type for Corona
  • New filter options to the Job and Node lists
  • Added benchmark indicators to the node row
  • 3ds Max plugins will be also searched at the new plugin addon environment variable (ADSK_3DSMAX_PLUGINS_ADDON_DIR)
  • Tiled image method, number of tiles and dependency type will be saved as default from now on
  • Added V-Ray Irradiance map status and progress
  • Fixed issue with 3ds Max quick submit buttons
  • Fixed issue when nodes are not starting single frame jobs after an error in the queue
  • Fixed issue with not closing 3ds Max when stopping corona spawner mode
  • Fixed an error that prevented the submission of scenes with tyflow
  • Fixed issue with Submit from 3ds Max buttons not triggering file save when required
  • Fixed issue with dependency type not being set correctly on job submission
  • Fixed issue with Scene Manager MaxScript commands in 3ds Max 2022 or higher
  • Fixed render issue when submitting multiple files from an opened 3ds Max
  • Fixed issue with packed task not saving output results
  • Fixed error with Edit Job when changing single frame to range
  • Fixed several job distribution errors
  • Minor UI fixes and improvements
1 Like
Vantage Chaos Workflow
#2

Hi Peter,

we have installed the New Version but V-Ray 6 is not beeing detected!
Nodes Now say there is no supported Version installed

Cheers

#3

Have you restarted Render Manager since you installed V-Ray?

#4

yes we did already couple of times :slight_smile:

#5

Could you please reach out to info@pulze.io with a collected log (Pulze FAQ | How do I collect my Render Manager logs and send them to Pulze support?) from the computer that produces this error and will look into it.

#6

After this update, there is a lot of issues. Camera rendering with target incorrect on all nodes. Now when starting, you need to confirm on each node anima people purchases, this did not happen before, and now because of this it is impossible to run the render remotely. I don’t think it’s necessary to launch a power shell. And there was also no option for the program to start minimized and not a full screen. (pulze 2.1.5 max 2021. corona 8.2. win 11) And because of this it is impossible to switch to max 2023. must use old version of render manager

image
image1920×1080 133 KB

#7

Yes there has been some issues unfortunetly which we managed to address. Please download and reinstall this again and it should be all good: https://public.pulze.io/pulze-downloads/pulze_service/2.1.5/pulze_215_win.zip

#8

Hi @peter.sarhidai,

For the future, can such fixes be released as a hotfix?
Or perhaps released as another version of Pulze Render Manager, i.e. 2.1.6 / 2.1.5 hotfix 1?

Alternatively, can users be informed via email that reinstallation is required.

If it wasn’t for us checking the forum, we would never know that the fixes have been made and that we need to update manually. Effectively, we would be stuck with non-functional/buggy version of RM 2.1.5. until the next release.
In fact, this has caused multiple jobs to render incorrectly over the weekend, which of course resulted in delays in project delivery. This could have been avoided if we knew the new fixed version of RM already exists.

The possibility to update RM on all machines all at once is great and very convenient, I don’t understand why the fixes to 2.1.5 could not be forced/suggested to users as it is done with every other bigger release.

Thanks

#9

Hi @inkvisual

First of all we are sorry for the inconvenience and for the trouble that the initial update might did. We are planning to have another release during August, but we have to wait a bit until these new issues are cleared and fixed.

Unfortunetly some of these are out of our hands and we had to remove a few fixes and new features in order to keep all the job types and render engines stable.

I agree that this could have been handled better, we definitelly learned from it and will try to avoid these problems in the future.

Once we have a new version we will reach out to every RM user via email and a notification should appear in the software as well.

#10

I had the same problem with anima. But you can define the purchased asset path on each rendernode, in the anima settings. Once you do that on each node, the message goes away.

#11