We have just switched from the Beta to the version pushed out to us via email and noticed a few things that worked in the beta but arent in the final version
1. the statistics have reverted to non-uniform units. they are back to being listed in bytes, megabytes and gigabytes. Clock time is back to days hours minutes seconds. This was fixed and reverted which broke all our statistics tracking.
1a. the export data function doesnt seem to be working. I cannot get any CSV files out of the farm statistic reports.
2. Some settings in the Max submit script that were not sticky now are, tiles are one area we have seen this issue.
Other feedback
Blow up mode doesnt work properly for region rendering in max. We cant get it to work no matter what we try
It would be great to get a check box in the Max V-Ray DR submission to give the user an option to release the DRs when the current job completes
It would be great to reset the DR enabled state to where it was previously when the user closes the DR dialogue. Here is what appears to be happening. The user uses the vray DR script to manage DR nodes. They then close the DR script window and just want to submit the job as a normal render job, however the DR option is now turned on and when they submit if another user has a DR job going the person who has the DR enabled box on unintentionally grabs some of the nodes that are running the Vray spawner for other users.
So in an effort to keep everyone happy, the default behavior for copy & paste is the same as it was in 6.1, but you can toggle that off to use the raw data.
We received requests to make these settings sticky. However, you can edit SMTD’s sticky settings file to make them not sticky again: thinkboxsoftware.com/deadlin … y_Defaults
Has blow up mode ever worked for you, or has this always been a problem? Can you provide examples of settings you’ve tried to make it work? We’ll log this as a bug and try to reproduce, but it might be helpful to know what you’ve already tried. Also, are you using the VRay frame buffer or the Max frame buffer? Maybe it simply doesn’t work with the VRay frame buffer…
We’ll add that to the wish list. Knowing maxscript, there is probably a callback we can hook into here.
Thanks for pointing this out. I am testing it now, however I still cant get it to save a CSV. It goes though all the motions, but when i hit save a file is not created.
this is great news!
Blow up mode has not worked for us, however i didnt use it at all with my last studio and we only just recently switched to deadline here so I cant really say if it ever worked.
Looks like we can reproduce this. Might just have to get a fixed version of the 6.2 public release asap, since there isn’t any workaround at the moment.
Just an FYI that there is an updated 6.2.0.32 installer available which fixes issue (1). Just use the link you got in the email from sales earlier and download again.