Alignment Rotation Increment Issue

Support Basics & Interface
1

Hi Everyone,

I do apologise if this has been answered before but I am struggling to find anything that can help me.

I start off with a circle (any number of verticies).

I then hit: Ctrl + Shift + Tab and select increment (snap element).

I try to see if I can rotate the circle to get another vertex at the top of the circle. But it never rotates properly.

Also trying to get an edge at the top or the bottom doesnt seem to align with the grid.

As you can see by the image the increment element isnt aligning very well. (Probably something i’m doing wrong!)

Issue 01.jpg1276×665 86.5 KB

I have tried all of the below settings. I cant think of trying anything else.


I also have an additional problem that I cant seem to resolve.

I have removed these two panels / menu’s and would like to recover them:

issue 02.jpg1892×969 246 KB

Any help would be great.

Regards,
Lee

2

increment snapping happens in 5° increments when the snapping is toggled on (shift+tab). 1° increments with shift, and can slow down the rotation with both. Snapping without toggling snapping on can be done by holding down ctrl. Aligning the sides on a mesh circle with 16 vertices means rotating 11.25° so increment snapping won’t help there

Write 360/16/2 in the rotation field for the object, or the same in edit mode by entering it on the operator panel after rotation, or with python input (numpad_*) during.

ctrl+o, uncheck load UI before opening the workfile, and stop cropping screenshots.

3

Hi JA12,

Ah OK, that makes sense with the increment snapping / rotation. I thought there was a bug but it was my poor maths skills. Looks like I need to brush up on that side of things! :slight_smile:

I loaded my model and unchecked ‘load UI’. Work great!

Thanks for replying so quickly and helping out a noob! + I won’t crop my screens in future. I thought it might help if I reduce the size of the image but I suppose a complete screen will show you exactly what I can see at the time of the problem etc…

Thanks again!

Kind Regards,
Lee

4

Yeees. The common trend is to only show one piece of information, often also what is already said in text form. You want people to answer with something that you don’t already know, but the source of that information is within the file when troubleshooting. The interface often has at least something relevant visible, if not the cause of the problem.

The trick is to use images so that you don’t have to write as much. People can see what you show without anyone saying anything. That includes the Blender version, the type/statistics/mode/view settings of the object/scene you’re showing and whatever else manages to be in the shot. If any of that is relevant to your question, it takes less time to not crop a screenshot than writing it down.

Images are great for explaining things but an example .blend is what you want to include for troubleshooting. What information people might need from you? That’s easy, everything you’re working with that relates to the problem. That’s why preparing a .blend is the most effective way to relay information. It works as an exchange file and as a source for visuals when people start replying back to you, and they’re more likely to reply with answers instead of questions and guesses.

Those should help with future questions that might also be more involved.

5

I didn’t think of uploading a .blend file. I will do that the next time I cant find a solution. + provide a full screen capture.

Thanks again for the help! Really appreciate it!

Lee