Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by line-weight

  1. That's great to hear that these issues are being looked at. I hope some progress will be made. But they aren't new. This is no criticism of you: but how has this mess been allowed to exist for so long? Here's a thread from 2007 with someone confused by pretty much the same thing. That's 13 years ago. 13 years! Will we be coming back to this in 2033?
  2. Yes I agree. To add to the confusion, I think the shortcuts will rotate planar objects in 3d views, but it rotates them relative to the screen plane or something, so you don't get the result you want. Therefore I just don't touch them unless I'm in top-plan.
  3. The excellent analysis by @Andy Broomell of the multiple ways in which these particular elements are confusing is illustrative of a common theme across the whole of VW. There are so many tools that have similar problems. Many instances of two tools that do nearly the same thing, inconsistent naming of functions, and much of it not properly documented, so that the only way you can figure out how things actually work is to spend a large chunk of your own time untangling it. I wonder if the notes I've written for myself on how VW functions work may soon be more extensive than VW's own help pages. Occasionally I do what @Andy Broomell has done above - write out a detailed explanation of why something's ultra-confusing. And then several releases later - nothing has changed. I feel sorry for anyone trying to learn VW from scratch.
  4. Do you mean rotate left/right by 90 degrees via the menu command or shortcuts? While these don't work, you can still use the rotate tool in 3d views.
  5. Are they actual mesh objects (rather than groups of 3d polygons)? Also, have you tried fiddling with the OpenGL options (crease angle can be adjusted here as well as in document preferences)?
  6. @rseybert my recent experience trying to use NURBS curves has led to me the conclusion that VW simply isn't much good at them, if you want accuracy. You might find some of this thread (perhaps more towards the end) of interest.
  7. It seems to defeat the purpose of offering the 'user origin', if stuff like this starts happening though. It seems like a bug to me - unless there is some good reason for it to work this way.
  8. Hm - it seems that the internal origin and user origin are not aligned, and it looks like this is the cause (judging by the offset). I had not changed the user origin myself - but something must have happened when I imported a DWG file. Thinking about it - in another file where I've been having similar problems, I had set the user origin myself (I think). Is this therefore a bug?
  9. Ok... thanks for the reply. For me it's been happening in 3d space. Might see if I can post the relevant file here if I get time.
  10. I'm aware there are various issues with symbols (and other containers) and internal origins and so on. But I'd like to know if the following is something that's not working properly, or the error is mine. I thought that if I (a) create a symbol (b) leave the original instance in place (b) specify the insertion point of that symbol as the drawing origin 0,0,0 Then (a) that instance of the symbol should have its internal origin in the same location as the drawing origin. (b) therefore copying something from outside of the symbol container, then doing a paste-in-place within the symbol, should result in that object staying in the same location Is all of that correct? Because sometimes the paste-in-place ends up with the object somewhere else, and I can't work out why.
  11. Do I need to update the title of the thread linked below to read 'VW2021' instead of 'VW2020'? (I've not used 2020 yet myself)
  12. I fear you may be in for a long and tedious process... but just in case it helps at all, see the second post here - something I hadn't realised was possible
  13. I've had some success using the 'spoil pile' site modifier to create kerb lines - you can draw as polygon in plan, and it'll offset the surface of the DTM by whatever height you specify. I've done it using it to offset pavement (ie sidewalk if you're in the US) areas upwards but you could potentially use it to offset roadway areas downwards instead. I've experienced some bugs using it in VW2018 but it's just about usable.
  14. I just tried making this NURBS curve into a 3d extrude Then 'extract edge' to get the highlighted edge. It looks ok zoomed out but when you look closely it looks like this Two faceted curves that don't quite match each other.
  15. Going on a bit of a tangent here... but I've realised there's something that's very tricky to get right even if you aren't worrying about the faceting. The attached image is in wireframe view so there is no faceting going on. It's a top, orthogonal view. Say I have drawn the blue curve first - and it then becomes part of the geometry of an object, the edge of a table, let's say. Now I want to draw the orange curve - I want it to follow that blue edge exactly. As you can see, it's easy enough to get it nearly right ... but if you want to get it exactly right, then the only option is to take the original blue curve, and cut it back somehow. Is that correct? Which is something you can only do if you've kept that original curve somewhere. If the object is something that has gone through a process of some subtractions, extrusions and so on, the original curve might not be easily accessible. So if you are doing this stuff properly then presumably you have to be always thinking about keeping track of the original geometry somewhere. I imagine these issues would come up modelling something like that boat. Or is it somehow easier in Rhino?
  16. Yes, that all makes sense to me. I'd sort of assumed that in principle, that's how it would work anyway (ie pre 2020) but sounds like it's not necessarily. So in pre 2020 versions, VW is calculating a load of facets even if a thousand of them are within a single pixel on screen?
  17. Hi @sbarrett and thanks for your reply. Following your instructions I've managed to remove a menu command, and also re-name it by re-saving it as a new menu command with the name I want. I note that it seems to be necessary to quit & reopen VW for these changes to take effect. Regarding using a network without making it a menu command... whether it's in the form of a symbol or not, the idea is that you place it into the drawing space of whatever you're wanting to use it to work on, and then delete it from there once it's no longer needed? Once it's in the drawing space, what does and doesn't it act on - does it act on anything in that file, or just on that design layer?
  18. yes, as noted further up the thread, increasing the number of control points on the curve has no effect. Regarding NURBS curves and 'degree' settings - this is a separate issue to what is being discussed in this thread, but contrary to what that PDF document implies, it is not at all clear what 'degree' means in VW and how it is controlled. I explain this in another thread:
  19. Thanks for taking the time to look at it and it would be good to hear if and when there is any progress. It strikes me that the faceting can be controlled by the various render settings which range from 'low' to 'very high', it's just that 'very high' is not high enough. Therefore is it possible to add an extra tier that *is* high enough? I assume that there are then potentially problems with the rendering becoming unmanageable but other elements are rendered in way too much detail.
  20. Looks like it also has some issues with sectioning elements that should be solid but turn out hollow - for example the roof, and roof beams here That's perhaps dependent on the geometry that it's given, so not Twinmotion's fault... but maybe means it can't solve this hollowness problem which is often encountered in VW?
  21. What's the Muntin tool? (By the way it would be nice if region-specific versions of VW could use the correct terminology for building elements. In the UK we don't call these muntins; they are glazing bars. It adds an extra level of confusion to the options in tools if you also have to go and find out what unfamiliar terms mean. Not only are we disallowed the superior window/door tools that users in other regions have access to but we have to decode north american terminology used in the permitted, substandard ones.)


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...