topic Re: Snap problem 3ds max 2017 in 3ds Max Forum

Snap problem 3ds max 2017

Anonymous — Fri, 22 Apr 2016 19:54:04 GMT

I tried to snap a pivot to vertex and it's just not happend. It doesn't work if you in edit poly or editable poly. Snap works only when you create a box or a sphere etc. After a convertation to editable poly it doesn't recognize vertices. I attached a video. https://youtu.be/B_gq6moLY-Y

Re: Snap problem 3ds max 2017

spacefrog_ — Sat, 23 Apr 2016 04:56:20 GMT

Yes please report this. A colleague Just found that too recently and i could repro

Here's the defect form

http://download.autodesk.com/us/support/report_a_bug.html?SelProduct=3dsMax

Re: Snap problem 3ds max 2017

Anonymous — Sat, 23 Apr 2016 06:10:08 GMT

Thanks. I sent it.

Re: Snap problem 3ds max 2017

Anonymous — Tue, 26 Apr 2016 11:41:58 GMT

Same here

But aligning the working pivot works fine.

Re: Snap problem 3ds max 2017

Anonymous — Wed, 27 Apr 2016 13:01:56 GMT

I too, am having this problem. I've had to jump back to 2016 to use the vertex snap since 2017 is really borked atm.

Re: Snap problem 3ds max 2017

Anonymous — Thu, 28 Apr 2016 23:12:25 GMT

In 2016 snap/cut are also broken. After some time working with modeling they just stops working.

Re: Snap problem 3ds max 2017

Kilowog01 — Tue, 03 May 2016 13:28:02 GMT

My problem is different. Here when I mark the Snap box in Vertex 3ds max crashes.

Re: Snap problem 3ds max 2017

danrod3d — Thu, 12 May 2016 06:05:42 GMT

Same for me as well. 😕 I submitted a bug too.

A sort of fast way to work around this is to do the following:

-Isolate your selection,

-duplicate your object and reselect the one you want to edit the pivot of.

-adjust the pivot of what you have selected, using the duplicate object as a point of reference to snap to.

-delete the extra object

Pivots work fine on other objects and editable polys, just not with itself

Re: Snap problem 3ds max 2017

I_Megaman_i — Fri, 13 May 2016 20:14:36 GMT

click on affect pivot then just ctrl+v, adjust your pivot on a new copy, then simply delete the original model, easy) though would be better if it wasn broken in the first place, its an essential feature...****

Re: Snap problem 3ds max 2017

Anonymous — Mon, 06 Jun 2016 17:41:42 GMT

Hey guys, I got the same issue here. But I solved it increasing the value of Snap radius and Snap preview radius, the default value is 20. Maybe it works for you.

Re: Snap problem 3ds max 2017

waqasziachaudhry — Tue, 29 Nov 2016 12:42:08 GMT

Make sure to unhide all your vertices before attempting to vertex snap. Even if you did not hide them they might still have ended up being hidden thru another sub object hide operation within Edit poly.

Re: Snap problem 3ds max 2017

manoffoot — Thu, 01 Dec 2016 12:56:38 GMT

I'm having similar issues. If the model is an editable poly (nothing in the modifier stack) when I try to effect pivot (snap to vertex) it doesn't work but it does as an editable mesh no problem. I've made sure it's not backfaced culled and all vertices are visible. My tool will even pick up the vertex in question as a possible start point for snapping but won't find any vertices once I've clicked on the gizmo handles. This is regardless of axis constraints.

Re: Snap problem 3ds max 2017

waqasziachaudhry — Thu, 01 Dec 2016 13:42:16 GMT

I have recently had the same annoying problem. It can sometimes help to zoom a bit out or orbit around the vertex in question. Wish I had a better answer for you. Also try going from persepctive to ortograhpic view, as that might help in tracing to the right vertex.

Re: Snap problem 3ds max 2017

Alfred.DeFlaminis — Sat, 03 Dec 2016 01:06:58 GMT

Hello @manoffoot and @waqasziachaudhry,

Can you please verify you have the latest update? I am unable to reproduce this but I did try. Maybe I'm doing the wrong method, can you please correct me? I've got a sphere, converted to poly. Then, I turn on 'affect pivot' and 'snaps toggle' for vertices. I am able to snap the pivot. I'm likely doing something differently here, so thanks for any clarification. I tried on the same object and other objects.

Best Regards,

Re: Snap problem 3ds max 2017

kgokhangurbuz — Sat, 03 Dec 2016 08:59:39 GMT

Hi;

I see that you have Axis Constraints Enabled under snap options, which allows you to move your snap axis only by 2. Also, you have grid snaps on.

Can you please turn Enable Axis Constraints option OFF and un-check Grid snap options and re-try?

-Go to Snap icons > Right click > Options tab

-Uncheck Enable Axis Constraints

-Under Snaps Tab, disable grid, make sure only Vertex is active.

Axis constraints for snaps has two shortcut combinations which is most probably to accidentally applied - ALT + D and ALT + F3

This might cause the problem.

Can you please update me with the suggestions above applied?

Regards;

Re: Snap problem 3ds max 2017

manoffoot — Mon, 05 Dec 2016 11:47:46 GMT

I will try to recreate the error again myself but I'm thinking it may be model/scene specific otherwise it would have been easily picked up. Unfortunately I can't at the moment as I have a deadline.

Re: Snap problem 3ds max 2017

alexnode — Mon, 05 Dec 2016 21:00:04 GMT

If autodesk is going to fix this issue could you have a look at fixing snapping a slice plane on the same object's vertices too. I always have to create a separate dummy object snap the vertices to my original object and then go to my original object to snap the slice plane on the dummy object.

Re: Snap problem 3ds max 2017

Alfred.DeFlaminis — Mon, 05 Dec 2016 23:29:31 GMT

Hello @alexnode,

There does seem to be some weirdness there, I'll log this. Thank you for reporting it.

EDIT: Some strange issues with the tool.

Best Regards,

Re: Snap problem 3ds max 2017

Anonymous — Tue, 06 Dec 2016 14:02:38 GMT

Same here, when working with dwgs from archicad I have a lot of crash. Max 2017 seems not to deal with 3d snaps when too many vertices.

Re: Snap problem 3ds max 2017

Alfred.DeFlaminis — Tue, 06 Dec 2016 22:30:41 GMT

Hello @Anonymous,

I'd like to get my hands on any files that cause crashes so I can attach them to currently existing reports or investigate them to find out why this is happening. If I created a private folder, would it be possible to share an offending file with me?

Best Regards,