Is there an RPManager Submission script for 6.0 yet? Pretty high priority for us.
Not yet. Bobo may be looking at refactoring SMTD for 6 so that it works better with RPManager. We really don’t like how we have to hack together SMTD to produce RPM-specific scripts, especially because they don’t “update” automatically when the repository is updated. Ideally, the RPM script should just be a proxy that calls the repository SMTD script. Hopefully we can get this to work.
Cheers,
- Ryan
It should be pretty much just one script that is modified for RPM integration (or used to be for 5, I haven’t dug into 6 yet but will soon), Bobo’s been in touch and I don’t doubt it can be simplified down to something much cleaner.
cheers,
grant
Thanks Grant/Bobo.
We can’t really move ahead with deployment until RPManager and Power management is all straightened out for testing.
Also Ryan, will auto-update be enabled in the next build of 6?
Auto-updating should work from beta 3 -> beta 4 (and future releases) for Windows and Linux.
We’re working hard to get the OSX version ready for beta 4, but we won’t get a chance to really test the auto-update feature on OSX until after beta 4 is released, so we can’t guarantee it’s stability.
Couple months later. We could realllllllly use some RPManager support right about now. 
I tried and failed to make it work with one set of files, so we will have to take the current SMTD for 6 and produce a set of RPM-compatible files. Will try to do this ASAP.
Sorry about that. 
Hi,
I would like to test deadline 6 with RPM too. Please keep us informed of any development. Thanks for your work!
Any progress? We would like to switch to deadline6 but our pipeline depends totally on the RPmanager.
Please let us know if there is any progress.
Thanks
Richard
PROGRESS! 
I managed to get a version of SMTD 6.0 to load in RPM and submit passes.
I also got a version for SMTD 5.2SP1 that fits the UI much better, but discovered that the newest feature I added upon request by Snowball Studios (submitting jobs dependent on previously submitted jobs) is not working. It is probably caused by RPM reinitializing the SMTD structures after submission…
I sent an email to Grant to take a look.
In addition, some features that worked in 5.2 are currently broken in 6.0 due to the switch to Database, and I am still working on that. Specifically, the submission of external files (bitmaps etc.) to the Repository used to modify the .JOB file in the Repository job folder, but in 6 there is no such file, so that code needs reworking.
I am attaching the current 6.0 version here, keep in mind the above notes and keep your eyes open for further broken features. Please report anything you find in this thread!
RPM_Deadline6_20130129.zip (236 KB)
Hi Bobo,
We tried to set the Custom Submit of this script within the RPManager Preferences.
However it always comes up with an error that says
FileIn of custom submission rollout failed.
I think this is a known issue with RPM and not directly related to SMTD.
Have you ever managed to run an older version of SMTD (5.x) with this install of RPM?
I was getting the same error until I changed the access rights of the 3ds Max folder - UAC is sometimes preventing RPM from setting up the custom scripts.
If enabling write access to the 3ds Max folders does not fix the issue, please let me (and Grant) know.
Previously we have been successful in using the RPM Script since Deadline 4 and 5 without having to change the access rights of the 3ds Max folder.
We also tried:
- running it as admin and disabling the UAC.
- enabling write access to the 3ds Max folders.
Thanks for trying that!
My question was - if you still have Deadline 5.x around (next to Deadline 6), are you able to load the SMTD 5 RPM files on the same machine you are trying to load the SMTD 6 RPM files? I want to make sure RPM loads correctly the 5.x files and fails with the 6.
Since the error is caught by RPM, I have no way of knowing what exactly went wrong. And it works for me, so I am not sure how to reproduce your problem. Have you emailed Grant about it, or should I contact him?
That being said, I am still working on the SMTD for 6 code (looks like I will be able to have one set of files for pure SMTD and RPM after all), so I will upload a new build when I have it…
Yup I can confirm that SMTD 5 RPM files loaded correctly.
I’m not sure who Grant is actually, so I have not contacted him yet. I presume that he’s the developer of RPManager? If you could email him or pm me his email that would be good. (I’m actually a maya TD helping out the 3Ds Max dept.)
Yep, Grant Adam develops and sells RPM.
If your SMTD 5 loads correctly, then it must be a problem with the files I posted for 6.
I would love to hear from other users whether they have the same problem - the build I posted was an initial attempt to port SMTD 6 to work with RPM, and it is not supposed to be used in production yet. A few things have to be fixed before it is compatible with the new database storage. But it was at least supposed to load and perform basic pass submission…
I will try to post a new build as soon as I have it before we involve the RPM side.
Hi Bobo,
we also got the same error message while trying to load the custom rollout.
but i can still load the latest deadline 5.2 custom rollout.
Hi Omer,
When I was talking to Grant Adam, he mentioned that some people were having a problem loading the shipping 5.2 files and he was about to take a look at that. Strangely enough, both the modified 5.2 and 6.0 files load on my machine, and I have no access to what is going on inside of RPM to know what exactly is happening. I will tweak the files today and try to get you both 5.2 and 6.0 files in the next days just to confirm whether they are loading or not. If they fail to load, I will send them to Grant to try them out.
This is separate from the other issues you are waiting to be solved though - I implemented parallel submission from multiple copies of Max (that works) and chain-dependencies, but then it turned out that the latter does not fit in the RPM scheme of things because RPM captures all SMTD data per pass and the dependency information is being destroyed in the process. So right now I am trying to make the dependency storage independent from the SMTD data structures…
It is the most painful development process I have ever experienced - making SMTD work as sub-set of another system I only see as a black box (no insight into its code or logic) is just quite tricky…
Thank you very much for your patience!
Thank you very much Bobo.
about the chain-dependencies, if you will take a look at the Backburner submission rollout within RPM you will see that the dependencies there are not per pass but global. the same goes for the submission settings like timeouts and server limit. maybe this could help in some way.
Sorry to hear it is so painful!
I downloaded the RPM_Deadline6_20130129.zip package and it doesn’t load for me either - it’s missing a closing parenthesis at the end of the ‘initialiseDeadlineScripts.ms’ file - ie simply adding a ‘)’ at the end has it working for me.
I tracked down the problem with RPM printing messages such as
“Deadline6 data failed to restore:-- Syntax error: at ), expected “(” or “[”
– In line: #(#(#MachineLimit, 20), #(#OnComplete, “Nothing”), #(#SingleTileJobTop, “”), #(#TilesPadding, 0), #(#CustomTiles, #()), #(#Alter”
each time you change pass the other day to an order of initialisation issue. I have fix for this which I emailed through to you a couple of weeks back (I’m not sure we’re getting each others emails 
I’m currently setting up for production with deadline 6 so one way or another this will all be sorted out.
cheers,
grant