denisT: but we want to participate too and be welcome in this party. At the moment both of you leave some kind of party-crasher-twins impressio…
the sourcecode is in the samples ( bonesdef or similar ) actually it’s a one liner to fix, simply an incoming parameter FPValue index is 0 instead of…
This bug was there in Max 2015 until (including) SP1 Was fixed in SP2 and SP3
Try in chrome , that worked for me for the bigger file ( the 2GB part ) The second part i had to download using firefox though … totally borked …
denisT: . just try to proof it’s not a myth but a gift dropped from heaven. I don’t understand your attitude at all. There are many shades betwee…
check the resulting filesize If you create an uncompressed AVI, it quickly can go above 2GB and thats the limit the AVI writer in 3ds Max stops creat…
I briefly looked in my maxscript code archive but did’nt find it As far i remember it involved DenisT’s method to expose Win32’s user32.dll’s “SetPar…
You can grab the viewports window handle via script, create a custom form via dotnet and rehook the viewport window as a new child of that form. After…
try2script: Of course, code protection I know everybody already knows about it , but it still would help NOT spreading this and other links, p…
Looks like you indeed use GUID’s for the function and variables names, with your prefix added and you put functions in a oneliner… so essentially it l…
Denis, that looks indeed very very unreadable ! Worse than i ever would believe that it would still run … @Martin: what i meant is simply replacing f…
I think you would have to write your own tools for MXS obfuscation I brievly thought about that topic half a year ago, and the only things i came up w…
Not o my workstation currently, but i think you can put an instanced “renderab!e spline” modifier onto the stack and adjust the spline thickness ther…
Are you sure it’s not your core for loop in “makeAVIpreview()” leaking ? I see you do dib = viewport.getViewportDib() which allocates a bitmap each …
Looks like maxscript still “hangs” somehow in the first, faulty struct definition ( the one with the wrong “=” ) You can check that as you will get a …