Bruce Kieffer Posted December 1, 2011 Share Posted December 1, 2011 I have one file that's giving me grief. Snap to objects is not working. It works fine in other files. Is there a way to fix this? I assume something's corrupt. How would I find the corrupt object or objects? Quote Link to comment
Pat Stanford Posted December 1, 2011 Share Posted December 1, 2011 Any chance your Class Options got set to something other than Show/Snap/Modify? Quote Link to comment
monkey Posted December 1, 2011 Share Posted December 1, 2011 silly question, but have you tried all the usual things like projection, plane, scale etc etc 1 Quote Link to comment
Dieter @ DWorks Posted December 1, 2011 Share Posted December 1, 2011 Are you in a group? Sometimes being in a group results in only snapping to objects in the group, espacially when using symbols etc... Quote Link to comment
the frog Posted December 1, 2011 Share Posted December 1, 2011 When this happens to me, the first thing I do is to copy the plan (being sure to group each layer not to lose my classes) then I open a new document and paste. If something was wrong in the old file it is usually corrected in the new one. Hope it works! Quote Link to comment
Bruce Kieffer Posted December 1, 2011 Author Share Posted December 1, 2011 All good suggestions. The problem seems to be layer plane. When I switch to screen plane all snaps work fine. OK, so I guess this goes back to my hatred of the screen plane/layer plane mess. Why doesn't VW see my view as 2D when I'm looking straight on in front view? I thought this was fixed in 2012 with automatic working plane. So now switching views is not enough. I also have to switch planes. Not good. Is there some setting I have missed with automatic working plane? Quote Link to comment
Damon Design Posted December 1, 2011 Share Posted December 1, 2011 Isn't a front view by its definition a 3D view? Quote Link to comment
Kevin McAllister Posted December 1, 2011 Share Posted December 1, 2011 Bruce, This is exactly why I keep reverting back to working in Screen Plane only. I wish the \ toggle toggled Automatic / Layer / Screen instead of just turning Automatic on and off. It totally is a mess. The screen mode snaps are so much more useful than the 3D snaps which are really only half functional. And of course anyone who worked in 3D before the screen/layer plane addition is totally dependent on these snaps as part of a workflow... Kevin Quote Link to comment
Bruce Kieffer Posted December 1, 2011 Author Share Posted December 1, 2011 Isn't a front view by its definition a 3D view? It is in VW, but when the projection is orthogonal, to me that's a 2D view. Please tell me a situation that warrants front view orthogonal to be a 3D view? Quote Link to comment
bcd Posted December 2, 2011 Share Posted December 2, 2011 When a building facade isn't parallel to the x-axis Quote Link to comment
Bruce Kieffer Posted December 2, 2011 Author Share Posted December 2, 2011 (edited) When a building facade isn't parallel to the x-axis bcd, Please you be more specific. Can you post an image or movie that shows this? When I view orthogonal front view, I only see the x and y axis. Any objects I place in that view are always set in that orientation. There are no vanishing points, and everything I see is in one plane. Edited December 2, 2011 by Bruce Kieffer Quote Link to comment
AndiACD Posted December 5, 2011 Share Posted December 5, 2011 When a building facade isn't parallel to the x-axis Surely in these circumstances, one uses "Look at Working Plane" (which i still have trouble getting to work since the "Planes" Enigma arrived) and this can be reached from a normal 3D view anyway as this is why the various elevation views were realised in the first place, the fact that you can work3D objects in any view is just a bonus of a 3D App. Problem is, despite claims with the new planes iteration, the connections between the two are very limited. Objects and Views continue to change . . . . . . for me anyway. Quote Link to comment
Assembly Posted December 6, 2011 Share Posted December 6, 2011 Symbols now drive me nuts with the 2d/3d/symbol plane. It seems that by default the 2D info goes to 3D layer plane. urggg Quote Link to comment
Ozzie Posted December 6, 2011 Share Posted December 6, 2011 I have not used the Hardscape Tool for several VW versions now because I do not like it at all ? rather do it by hand So recently as it had been ?greatly improved in VW 2012 ? maybe 2011 ? supposedly? decided to give it a burl ? what a convoluted piece of c**p but as I say that - if you wish to use it for pretty things - fine but what about if you wanted to show different things within it turned on and off in different Viewports Today I tried to put a Hardscape inside a 2d Symbol for a Legend Item within a 2D Legend which itself was a symbol and when I exited the Symbol was told through a pop up ? something like ? you have turned something 2D into 3D so now you will not see me in a 2D view I reckon the surface of VW is sometimes made to be cool and honky dory ? BUT ? the depths of Vectorworks are un-plumbed and a deep dark science The lesson I learned today was never use the Hardscape Tool again Why sometimes as you delve deeper into Symbols, Groups and ?contained geometry? all of a sudden no longer can you see other things whilst in editing modes although you have it ticked in VW Preferences Sorry to ramble on but how come since I learned recently Screen Plane is a Legacy thingy that is left there because that is how it used to be - today I was drawing away and had not changed nuffin from Layer Plane to Screen Plane and as I tried to add two surfaces together was told both were on different planes ? what whoo back there boy ? I did not do that ? or maybe I did without knowing and that could be the point Quote Link to comment
Bruce Kieffer Posted December 6, 2011 Author Share Posted December 6, 2011 This will never be over until screen plane and layer plane go away. I still say all we need is everything is 3D until I tell an object to be 2D, and when I look at something in one plane (say front view orthogonal), that's a 2D view. Quote Link to comment
reGenerate Design Posted May 10, 2021 Share Posted May 10, 2021 for anyone else out there grappling with this issue - I just found out that I was drawing on a layer that was set to a different layer scale. Make sure your layers are all the same scale because if they aren't, snapping won't work, and of course, you'll get mismatched geometry. Quote Link to comment
MarcelP102 Posted February 23, 2022 Share Posted February 23, 2022 On 12/1/2011 at 1:48 PM, Dieter @ DWorks said: Are you in a group? Sometimes being in a group results in only snapping to objects in the group, espacially when using symbols etc... I have got the same issue. Objects within a group within a 3D symbol won't snap to objects outside the group. Everything like classes and layers are set to snap to others. What can this be? Anyone else have had this issue? What's the fix? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.