AWS Thinkbox Discussion Forums

SMTD errors in v6.1

  1. Upon opening SMTD the first time only, I get this error (the priority slider is not happy and invisible once the GUI appears):
    (This only happens the first time and I can’t repeat this issue…)

– Error occurred in updateControls(); filename: C:\Users\owenm\AppData\Local\Autodesk\3dsMax\2014 - 64bit\ENU\scripts\SubmitMaxToDeadline.ms; position: 58406; line: 1430
– Frame:
– theIndex: undefined
– called in SMTD_MainRollout.open(); filename: C:\Users\owenm\AppData\Local\Autodesk\3dsMax\2014 - 64bit\ENU\scripts\SubmitMaxToDeadline.ms; position: 63129; line: 1563
– Frame:
– SMTD_LastSubRollout: 1
– RMpasses: undefined
– RPMDataNet: undefined
– allTodaysFiles: #()
– lastFileNumber: 0
– rpmdata: undefined

MAXScript Rollout Handler Exception:
– No “”/"" function for undefined <<
Total SMTD Launcher Time: 2288ms
– Error occurred in sld_priority.clicked(); filename: C:\Users\owenm\AppData\Local\Autodesk\3dsMax\2014 - 64bit\ENU\scripts\SubmitMaxToDeadline.ms; position: 52584; line: 1259
– Frame:
– value: 90

MAXScript Rollout Handler Exception:
– Incompatible types: 90, and undefined <<

  1. new “Multi Region Render” feature - I get this error every time I click “Add new region” and then with manipulators enabled in viewport, I simply click to select and try to move the region:
    (line 193 of RegionManipulator.ms is the area of interest…)

– Error occurred in mouseMove(); filename: C:\3dsMax2014x64\scripts\startup\RegionManipulator.ms; position: 6647; line: 193
– Frame:
– theSnapY: #(0.0, 1.0)
– which: 4
– theSnapThreshold: undefined
– width: undefined
– SMTDSettings: undefined
– y: undefined
– notBlowup: true
– x: undefined
– ySize: 332
– xSize: 444.0
– m: [326,169]
– vpAspect: 1.95495
– theSnapX: undefined
– rAspect: 1.33333
– height: undefined
– yDiff: 0
– xDiff: 103.5

MAXScript Scripted Plugin Handler Exception:
– Unknown property: “MultiRegionData” in undefined <<

  1. This is not my code, but it looks like it is possible that the attempt to read the maximum priority from the Repository returns #success, but the value read back from the result is undefined. We should add a check for that in the GetMaximumPriority() function.

  2. This is very interesting, I guess it has something to do with the order of loading of files. I haven’t seen it happening here, so it is possible that it is different on different machines (it worked on my home workstation, on my laptop and on the Siggraph demo machine, so it is new to me). Can you try opening the “RegionManipulator.ms” file in the Repository and adding the line

global SMTDSettings

as the first line in the script?
Then try restarting SMTD and see if anything changes. Since the RegionManipulator is loaded first by the launcher, it might be missing the global scope SMTDSettings struct and creating a local variable instead. Then again, I would have expected it to work the second time around if you restarted SMTD, but from your post it does not sound like that was the case?

Thanks for the feedback!

  1. Yeah, it’s definitely the new “Max Priority” setting that is causing this issue.

  2. Added this 1 line and now it’s fixed! I never tried re-opening SMTD in the same session (tired last night, giving it a once over). However, on a new session of 3dsMax, it would still go wrong. Anyway, it’s fixed now with the addition of this one line.

I’ll give it a proper test shortly…

Thanks,
Mike

I’ve committed the fixes for both of these issues, so they’ll be included in the next 6.1 beta.

Thanks!

  • Ryan
Privacy | Site terms | Cookie preferences