Only a small thing, but the selection of the 3DsMax version is no longer ‘sticky’ when submitting a vray spawner job from the launcher 
Good catch! Easy one to fix and will make sure this gets included in the next release. Just open up this python file:
“[your_repo_path]/scripts/Submission/VraySpawnerSubmission.py”
and edit the order of the following line from:
[code] settings = (“DepartmentBox”,“CategoryBox”,“PoolBox”,“SecondaryPoolBox”,“GroupBox”,“PriorityBox”,“MachineLimitBox”,“IsBlacklistBox”,“MachineListBox”,“LimitGroupBox”,“MaximumServersBox”,“ApplicationBox”,“VersionBox”,“PortNumberBox”,“IsInterruptible”)
scriptDialog.LoadSettings( GetSettingsFilename(), settings )
PopulateDropDowns(None)[/code]
and just move the “PopulateDropDowns(None)” line to be above the “settings = …” line as follows:
[code] PopulateDropDowns(None)
settings = ("DepartmentBox","CategoryBox","PoolBox","SecondaryPoolBox","GroupBox","PriorityBox","MachineLimitBox","IsBlacklistBox","MachineListBox","LimitGroupBox","MaximumServersBox","ApplicationBox","VersionBox","PortNumberBox","IsInterruptible")
scriptDialog.LoadSettings( GetSettingsFilename(), settings )[/code]thanks, fixed!
Somehow my DL launcher doesn’t start automatically after updating to 6.2
I re-enabled it in the settings (untick-tick) but didn’t help.
Shall I task-schedule it manually or is it better to reinstall?
Great.
I’m not too sure what you mean by “I re-enabled it in the settings (untick-tick) but didn’t help.”
The Deadline Launcher icon won’t be present if you are running it as a service/daemon or if you started the launcher via this command:
deadlinelauncher -nogui
However, I assume none of this is the case for you? So, sounds like a bad install and maybe re-install will clear this up.
(Make sure you re-install as a user with admin rights)
If this is still an issue after re-install, then BEFORE you reboot the machine after re-install, please provide the installer log, which will be in:
“C:\Users%username%\AppData\Local\Temp”
yeah… i was a bit confused… there’s an option to enable “launch slave at startup” mistakenly remembered it as “launch launcher at startup” 
Should have checked… I indeed don’t have it running as service.
Will re-install it in a bit and let you know if there’s trouble.