or was it never a bug in the first place. We’ve stuck with version “i” because of this reason, but now Max 6 is due to be arriving we will need to upgrade to “m” for compatability, so i’m just checking first.
Thanks
Rob
or was it never a bug in the first place. We’ve stuck with version “i” because of this reason, but now Max 6 is due to be arriving we will need to upgrade to “m” for compatability, so i’m just checking first.
Thanks
Rob
I could never really reproduce that, so I haven’t fixed anything. Is the “i” version more predictable in render times on the same file?
Best regards,
Vlado
We even went back to the g version, i find it renders way faster than the latest versions.
But that’s just me, i also can’t find a way to reproduce this.
Erik
am i correct in assuming M is the only max 6 compatible build?
we can’t also reproduce that strange behave… the only thing i can say is, that this happens only when memory consumtion was very high.
i still like to know what could happend..
Yes, I believe that “m” is the only build avalible for max6. Its the only one offered in the DL section anyway ![]()
-dave