Thanks, I’ll look into it.
Force of habit. I used CTRL+LMB to place the first point and when it asked for the second choice (rotation plane) for some reason I assumed it would be another point like the 1st and pressed the control button again. It’s a PEBCAK error, but given the workflow I wouldn’t be surprised if a lot of people trying out Roto Move make the same mistake.
I thought it might have been to fix some weird fix like that. I had to do a lot of those myself.
Wow, that’s far more complex than I realized. Hmm… Are you sure Blender (and/or one of the Python/numpy libraries) couldn’t most of that for you? That could massively simplify your rotation code. I know Blender has XYZ and “arbitrary axis” (spherical) rotations built into the “bpy.ops.transform.rotate” macro and also into the Vector, Matrix, and Quaternion classes. The somewhat tricky part with using the classes for rotations is you have to align your coordinates so they are being rotated around the “world center” (0,0,0), but I think there might be a way to do that on the fly.
I ended up dropping most-to-all of my add-on’s custom rotation code and switching to Blender API stuff. Thanks to that I was able trim off something like 50 or more lines of code and get a little performance boost in the process (the benefit of doing calculations with Blender’s compiled C instead of interpreted Python).
No problem It seemed to still work during the quick test run I did, but you may want to do further testing. I can upload my edited version of “get_eul_z_angle_difffff_in_rotated_system” if you want.
Hmm… If it helps, I was launching “NP 020 Point Scale” from the spacebar menu. I didn’t have this issue when launching Point Scale from the Tools Panel.
- Select mesh obect
- Launch “NP 020 Roto Move” from spacebar menu and rotate the object
- Undo the roto-move operation so the object is back to its original state
- Launch “NP 020 Point Scale” from spacebar menu with same object selected
I will go into more detail. With the current “NP 020 Point Distance” as soon as you select the second vertex, the add-on exits and the on-screen measurements disappear (changing Step from Simple to Continuous wouldn’t fix this). My request is to have the add-on stay running after the second vertex is selected (so on-screen measurements stay visible). Then you could do something like zoom in or out or rotate the 3D View to see the individual measurements from multiple viewpoints. That would be very useful for documenting dimensions.
Thanks for the reply. I’ll let you know if I run into any more bugs and I will keep an eye out for updates.