Search
-
mya 2015 (modeling toolkit manipulator issue)$100 reward
i have an issue i cant fix, if anyone can check out the video caps below. $100 reward for info leading to the fix. the modeling toolkit manipulator stops working, cant select handles and drag (only on some verts sometimes). it works fine with legacy manipulator, or when i switch to quad view ports. if i reset prefs it will… -
Re: mya 2015 (modeling toolkit manipulator issue)$100 reward
thanks Saf, in about an hour from this post im going to load the dirty prefs. if its busted on this ATI card ill try your suggestion first. maybe it will just work though (then im stuck with ATI..heh). ill post my results though, thanks again... ive been trying stuff like this with a bunch of the gpu variables.. { int… -
Re: mya 2015 (modeling toolkit manipulator issue)$100 reward
Maya 2015 SP5? try change clipping plane: setAttr "perspShape.nearClipPlane" 0.001; setAttr "perspShape.farClipPlane" 10000000; -
Re: mya 2015 (modeling toolkit manipulator issue)$100 reward
try selectPref: selectPref -manipClickBoxSize 4; selectPref -clickBoxSize 4; selectPref -xformNoSelect 0; -
Re: mya 2015 (modeling toolkit manipulator issue)$100 reward
thanks for the reply guys, much appreciated. SyncviewS, i have to run dx11 for our gametools/shaders. i switched my card out with an ATI and im in working order so im getting some work done. when the day ends ill force the problem prefs file and see if it still happens on the ATI. saf Maya 2015 sp6. extension 1, all… -
Re: mya 2015 (modeling toolkit manipulator issue)$100 reward
Hi meshiah, this is just a hunch, so don't hold your breath. I noticed you have your viewport rendering API set to DirectX11. Is there any specific reason for that? Maya defaults to OpenGL. If you haven't tried this already, set it to OpenGL. Go to the menu item Window > Settings/Preferences > Preferences. Choose Category:… -
Re: mya 2015 (modeling toolkit manipulator issue)$100 reward
ugh, so i loaded the dirty prefs on the ATI card and I get that error still. when i snap to legacy view port then back to 2.0, it fixes it self, but it will come back im sure... were diffing the 2 preferences right before and after i swap to legacy and back....and yea i did try all those Saf plus amny more....
7 results