Render setup window very slow to open

[^Lele^]

Mmmmh, i have never used RPManager myself, so i can't really give you an opinion on it.
I was also being facetious with the feelings thing, ofc. ^^
There may be leaks (max 2017 sp2 is giving me all sorts of odd, small issues, for example) somewhere, but it's quite difficult to find out what is doing what in a specific circumstance and configuration.
It not being scene-dependent either makes reproduction all the more complex.

I'm not being a smarta** when i claim the times i do, it's really what i am getting.
Say it's a local dongle: maybe a slightly old or badly written USB driver, or a defective usb port which may require retransmission when the machine heats up because the SNR drops, all would potentially contribute to slowdowns when license checking.
Maybe testing with the demo version, which has no license check may help.
If the issues go away, then it's a problem with the license checking, not inherent with the V-Ray code.

Further, i'm noticing max doesn't REALLY like my 5k monitor, and it all becomes sluggish in the ui quite rapidly, the windows redraws slow as heck (that's likely due to my VP settings, and yet.), and dropdowns take half a day, perceptually, to display their lists.
Opening an overlay window on the redrawing VPs isn't making it happier, that's for sure, in my case. Any window, not the render dialog itself.

Keep the questions and issue reports coming, we'll figure this out.

[^Lele^]

I slightly modified the script to run ten times in a row, and at the end of each open/close pair, do a "heapCheck()" to verify the maxsctipt heap memory isn't corrupt.
If one sees anything but "true" then something's wrong.An example run of the script, on a max that's been open, and severely manhandled by maxscript (to render out a bunch of stuff which it created procedurally from text files on disk), for the best part of my day:

"run #1" --run number
"0.911" --open
"0.061" --close
true --is memory heap ok?
"run #2"
"0.9"
"0.062"
true
"run #3"
"0.913"
"0.063"
true
"run #4"
"0.904"
"0.064"
true
"run #5"
"0.896"
"0.069"
true
"run #6"
"1.125"
"0.069"
true
"run #7"
"0.984"
"0.072"
true
"run #8"
"0.951"
"0.071"
true
"run #9"
"0.97"
"0.082"
true
"run #10"
"0.95"
"0.075"
true

rendDiag_timer.zip

[Sprawl]

I have a dongle local license. I test with License Vray as service and .exe, but it's the same.
Here my results:

3ds max 2017 sp2 with no scene loaded, Vray 3.40.02:
"run #1"
"0.0"
"0.333"
true
"run #2"
"0.872"
"0.297"
true
"run #3"
"0.879"
"0.292"
true
"run #4"
"0.886"
"0.29"
true
"run #5"
"0.884"
"0.293"
true
"run #6"
"0.884"
"0.293"
true
"run #7"
"0.881"
"0.294"
true
"run #8"
"0.889"
"0.295"
true
"run #9"
"0.889"
"0.298"
true
"run #10"
"0.895"
"0.295"
true

3ds max 2017 sp2 with a architectural scene loaded with one RE, Vray 3.40.02:
"run #1"
"1.13"
"0.305"
true
"run #2"
"1.116"
"0.304"
true
"run #3"
"1.134"
"0.312"
true
"run #4"
"1.155"
"0.305"
true
"run #5"
"1.253"
"0.306"
true
"run #6"
"1.247"
"0.307"
true
"run #7"
"1.239"
"0.307"
true
"run #8"
"1.221"
"0.309"
true
"run #9"
"1.248"
"0.31"
true
"run #10"
"1.249"
"0.31"
true

[Vizioen]

3ds max 2016 (no scene) + Vray 3.40.02


"run #1"
"1.344"
"0.344"
true
"run #2"
"1.306"
"0.339"
true
"run #3"
"1.652"
"0.337"
true
"run #4"
"1.62"
"0.341"
true
"run #5"
"1.603"
"0.329"
true
"run #6"
"1.585"
"0.332"
true
"run #7"
"1.606"
"0.374"
true
"run #8"
"1.686"
"0.333"
true
"run #9"
"1.6"
"0.371"
true
"run #10"
"1.598"
"0.329"
true


3dsmax 2016 (simple studio scene loaded with 7 REs) + Vray 3.40.02

"run #1"
"1.657"
"0.359"
true
"run #2"
"1.776"
"0.378"
true
"run #3"
"1.99"
"0.517"
true
"run #4"
"1.791"
"0.347"
true
"run #5"
"1.703"
"0.348"
true
"run #6"
"1.731"
"0.419"
true
"run #7"
"1.914"
"0.383"
true
"run #8"
"1.838"
"0.444"
true
"run #9"
"2.289"
"0.439"
true
"run #10"
"1.652"
"0.345"
true

I have a sh*t ton of plugins and scripts loaded too, all in all I can't complain, everything 's stable

[dlparisi]

Local dongle, max 2016 and vray 3.40.02. So far the times feel normal, a light delay over scanline but nothing too strange. I'll try and retest once it gets all wonky. Oddly though, max appears to go unresponsive after 2 or 3 dialogs open and close but returns after 15 seconds as if everything is fine even though nothing was actually opening on the screen. It reports the times as if it was actually displaying them.

BTW, this is the oddest benchmark I've ever run...

"run #1"
"1.666"
"0.141"
"run #2"
"1.684"
"0.141"
"run #3"
"1.751"
"0.142"
"run #4"
"1.75"
"0.137"
"run #5"
"1.85"
"0.139"
"run #6"
"1.872"
"0.142"
"run #7"
"1.788"
"0.147"
"run #8"
"1.809"
"0.15"
"run #9"
"1.803"
"0.157"
"run #10"
"1.84"
"0.151"

[^Lele^]

yeah, that's viewports overlay and redraw being bad for Max.
I used to know what to do to get that stuff out of the way with the old D3D drivers.
Don't ask for nitrous, though...

BTW, this is the oddest benchmark I've ever run...

Ahahah, i have to completely agree to this! XD