Hi @Zalek4, Looks like line 20 looks like your culprit, an invalid transform on the persp camera. setAttr ".t" -type "double3" -nan(ind) -nan(ind) -nan(ind) ; changing this to regular float in np++ values seemed to load ok for me. I found this by checking the script editor/log, one of the first errors looked like the…
@Zalek4 -nan(ind) is shorthand codespeak for -NotANumber(Indeterminate) What that means is that when maya wrote out the .ma file, it couldn't figure out what those numbers should be, so it sh$t the bed and fail-safe to codespeak. This is often times due to very large or small numbers that confuse maya. One remedy is to…
OMG. I saw a bunch of posts about the QNAN and NAN, but my file still wasn't working after changing those. I legit signed up for this forum just to thank you for pointing out how to look for IND and how to fix it. That just saved my artist's ass who would have otherwise lost a full day of work.
Oh I totally forgot to address that. I'm 81% sure that you need to use float values instead of integers on that setAttr, 0.0 instead of straight 0. It is annoying that the whole rest of the file fails because of that. One would think that since they decided to write nan(ind) that they'd have the courtesy to at least…
Hi @throttlekitty ! Thanks a TON for helping me out! Just to clarify, what should the syntax look like when I change it? Am I replacing "double3" with "regularfloat", or am I replacing "-nan(ind)" ? Or none of the above? I'm not familiar with the code for .ma files :) Again, thanks a lot! Edit: I figured it out and it…