k4noe: That’s not the important one, this one is:
(
local obj = convertToPoly (Plane lengthSegs:1000 widthSegs:1000)
st = timestamp(); sh = heapfree
local selectedVerts = polyop.getVertSelection obj
for i = 1 to 100 do
for j in selectedVerts do ()
format "time:% ram:%
" (timestamp()-st) (sh-heapfree)
)
max 2016: time:661 ram:248L
max 2017.1: time:15673 ram:264L
max 2018: time:2656 ram:264L
Sorry bout that, it seem because I change my PC its got better, but its not…I cant seem to open my max 2014 after installing max 2017 or 2018 to testing it … I still don’t know why. I’ll try it at home .Thanks for pointing that out.
“… Only time will tell …”
Well, two years after and we can see that there was indeed something wrong in Max 2017 release.
Being it a bug, a poor design or a bad design implementation isn’t of much relevance at this time.
The fact is that something was changed and things got better in Max 2018 and Max 2019, at least for what is tested in this script.
We all make mistakes. Thank you for improving the speed issue![b]
3DS MAX 2014[/b]
time:785ms heap:3369576L RAM:1149.14MB
3DS MAX 2016
time:776ms heap:3500440L RAM:1148.87MB
3DS MAX 2017
time:2975ms heap:3477760L RAM:1151.37MB
3DS MAX 2018
time:968ms heap:3464852L RAM:1156.11MB
3DS MAX 2019
time:999ms heap:3680068L RAM:1146.99MB
As far as other scripts (for example this one from Swordslayer), things also got better in Max 2018 but still not as good as in the pre-2017 release.
max 2016: time:217 ram:248L
max 2017: time:7125 ram:268L
max 2018: time:979 ram:272L
max 2019: time:971 ram:196L
Definitely is way better than 2017! But sucks in that last example , it’s still quite a lot slower than 2016. Which is what I use at work and home yet.