SetAttr ($camShape + ".horizontalPan" ) 0 String $camShape = `listRelatives -c -s $camera` String $panel=`getPanel -wf` if ($panel = "StereoPanel") ĬatchQuiet(`setAttr ($camera + "." + $chan) 0`) ĬatchQuiet(`setAttr ($camera + "." + $chan) 1`) I put this on my hotbox so I can quickly access it: i added a small part to reset pan/zoom as well here is some mel code you can run in your scene to reset you camera. it looks like this issue is fixed in 2018.4īut until you get updated. Next in the view, go to view -> default Viewīut really, I'm more interested in how it happens, and how to fix it ! To fix this you want to do a couple things.įirst is to reset the TRS of the camera, so select it, and run Modify -> reset transforms. For some reason it will put NAN into all the translate channels of the camera, and also in the center of interest (which is the biggest issue), and using to try and go back to previous views. This new issue seems to be hard to track down, but easy to accidentally do, and that's when hit f to frame the camera on a selection.
but Maya, says, wait I don't know what NAN is and basically stops trying, and just errors out the rest of your scene. Fubar uvs are not my problem, and I can make new ones anyway. But it would mess up Maya read on open, and often would end up in an open file, with seemingly nothing in it but the transform nodes. especially with uvs coming from zBrush, as zBrush, like the honey badger, didn't care. The issue crops up when Maya has a division by zero issue, or something similar that results in an infinitesimally small or NAN number. I haven't seen this one in quite a while, but just got bit by it. All NaNs in IEEE 754-1985 have this format: An exceptional result is represented by a special code called a NaN, for "Not a Number". The act of reaching an invalid result is called a floating-point exception. Some operations of floating-point arithmetic are invalid, such as taking the square root of a negative number.
0 kommentar(er)
