Notifications
Clear all
[Closed] Anyone knows this MAXScript bug?
Page 3 / 3
Prev
May 20, 2012 9:39 pm
Hmmm, very interesting. The invalidation has nothing to do with it. Regardless of the end result, this:
addModifier obj (copy (Subdivide size:42))
is much faster than this:
addModifier obj (Subdivide size:42)
care to tell us why?
1 Reply
May 20, 2012 9:39 pm
I see.
Anyways, this one is faster than yours, but it is specific to the subdivide modifier
fn foo obj =
(
disableRefMsgs()
local s = subdivide manualUpdate:0
addModifier obj s
enableRefMsgs()
numPoints obj
s.size = 42
s.manualUpdate = 1
)
edit: actually my timing results are inconclusive.
May 20, 2012 9:39 pm
for me the speed is the same. which makes sense.
also i don’t see the big difference with and without the disabling of ref-messages.
1 Reply
something like:
delete objects
b = box .[i].. size[/i]... [i]segments[/i]...
bb = copy b.baseobject
[i]timestamp[/i]
[i]loop[/i] [i]of number iterations [/i]
(
b.baseobejct = bb
foo b
)
[i]timestamp[/i]
that gives me the constant result…
May 20, 2012 9:39 pm
same issue with max2011 32bit , i try subdivideSpacewarpModifier() and the result is different
Page 3 / 3
Prev