Thanks, tried all three versions (2014-2016). They all have the same issue, which makes me think it's something I'm doing. The weird part is, it works perfectly well in the legacy viewport in all 3 versions. And I'm computing the boundingbox the same way for both the legacy and vp2 locators.
On Friday, January 29, 2016 at 6:26:10 AM UTC-8, Dilen Shah wrote: > > Hey, what version of maya are you using? because there is some > supportability issues of viewport 2.0 in maya 2014 and 15. > > I wouldn't want to use vp 2.0 with draw functions for now until it gets > patched but i guess that won't happen. > > But 2016 Maya has some improvements may be you can try on it. > > Goodluck! > > D. > > On Friday, January 29, 2016 at 1:49:43 AM UTC+1, Daniel Lindsey wrote: >> >> Has anyone else had this issue? I have a custom locator, that has >> attributes on it to define scale, orientation, and translation offsets. >> It draws properly in vp 2.0, and even reports back the proper boundingbox >> size from the boundingbox method. >> However, the locator is only selectable in the region of -1,1 in the >> scene. Once selected like that, then the boundingBox seems to be updated >> properly, >> and you can select the locator from the correct bounding space. >> >> Has anyone had this issue? Has anyone found a workaround for this if >> they have had this issue? >> >> Thanks, >> -D >> > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/01690964-31cf-4727-82bc-ffe703be15e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
