05-14-2021, 11:26 AM
And another bug in the tyPreview. Not sure if it needs a different post.
I'm replacing default max grabber with tyPreview and there is a for loop in my script where I run preview with different settings.
I noticed that some previews have strange pixels offset. After some research I've found that tyPreview creates good preview only in first iteration in a loop, but then it creates those previews with offset. Presumably because for loop doesn't wait for some tyPreview ending procedure and next tyPreview grab starting in some wrong state.
I've found a dirty fix on maxscript side:
These two strings together are fixing the issue:
colorman.repaintUI #repaintAll
windows.processpostedmessages()
3ds Max 2020.3
To reproduce this bug you can comment those 2 lines and grab some camera animation around a Teapot.
____
Of course I've already fixed it for myself, but tyPreview would be even better without this bug
I'm replacing default max grabber with tyPreview and there is a for loop in my script where I run preview with different settings.
I noticed that some previews have strange pixels offset. After some research I've found that tyPreview creates good preview only in first iteration in a loop, but then it creates those previews with offset. Presumably because for loop doesn't wait for some tyPreview ending procedure and next tyPreview grab starting in some wrong state.
I've found a dirty fix on maxscript side:
Code:
(
clearlistener()
fn Grab i =
(
f = @"D:\Downloads\tygrab\" + i as string
tyPreview output_filename:f appearance_safeFrames:off
colorman.repaintUI #repaintAll
windows.processpostedmessages()
)
for i=1 to 2 do
(
Grab i
)
)
colorman.repaintUI #repaintAll
windows.processpostedmessages()
3ds Max 2020.3
To reproduce this bug you can comment those 2 lines and grab some camera animation around a Teapot.
____
Of course I've already fixed it for myself, but tyPreview would be even better without this bug
