Jump to content

line-weight

Member
  • Posts

    3,715
  • Joined

  • Last visited

Posts posted by line-weight

  1. 7 hours ago, Senthil Prabu said:

     

    Generally, it is identifying those self-intersection cases (see below image), but this case it is missed, it is a bug.  We will look into that, if possible, please create a bug. 

     

    image.png

     

     

    Thanks for your reply. If it's a bug, then I think you should find someone within VW to register it.

  2. Agreed.

     

    In particular it would be good to have a way of texturing materials with some kind of directional grain in an intelligent "3D" way.

     

    Like you I'd be interested to know how other softwares deal with this.

    • Like 3
  3. @Senthil Prabu these "self-intersections" in source polygons quite often cause things to fail in VW. It's quite easy to introduce them without realising, and it can be quite hard to find them.

     

    It would be good if - when this causes a failure - we could get an error message that tells us that this is the problem. Because in many cases, the operation just fails, or we get some kind of generic message, and this does not help troubleshooting.

  4. Ok, the main thing to understand is that when you change a design layer "scale" in vectorworks you aren't really changing the scale of anything, it's just changing how it is presented to you - how it is "previewed" if you like. This is confusing and I've long argued that the terminology should be changed, to stop confusing people.

     

    When you change the "scale" of a layer in VW nothing at all happens to the geometry itself. If you've decided that 1 drawing unit = 1mm then that doesn't change.

     

    If you import something externally you just need to make sure that the drawing units match. So, if in your file 1 drawing unit = 1mm then you make sure that you import geometry such that in the imported geometry, 1mm = 1 vectorworks drawing unit. Depending on where it's coming from you might need to rescale it during the import process to achieve this, but once it's in VW you don't need to change it again.

     

    You can set different "scales" for different design layers in VW. So if you have a 10mm x 10mm rectangle on one layer, with layer scale = 1:1 and you have a 10mm x 10mm rectangle on another layer with layer scale = 1:10, and you have both layers visible at the same time, one rectangle will appear 10x larger than the other. But it's not. Change both layers to the same scale and the two rectangles will be the same size.

     

     

     

  5. On 1/5/2024 at 5:48 PM, shorter said:

    Would anyone find it useful to have a button to lock the position of section viewports when placed on a design layer?

     

    Why don't section viewports have the same X, Y and Z values that normal viewports have on design layers?

     

    It is impossible to know if one has moved, which is critical if you want to ensure your details are coordinated with the model.

     

    What do you use section viewports for, on design layers? What are they placed relative to, and why?

  6. I agree with everything that benson shaw says.

     

    I think that trying to measure on the drawing to predict where the ends of the bent sheet material will end up, when attached, is destined for failure. If I wanted joints to be in specific locations, I would choose those positions such that the predicted edges of a bent sheet oversail them a bit, and work on the assumption that the sheets will be trimmed back on site.

     

    The issues you touch upon, of faceted curves and accuracy of snapping to them, these are a bit of a problem in vectorworks in certain situations. What is and isn't a problem is a bit complicated. But I'd say that in general terms, as soon as you start doing complex curves especially things like NURBs curves in Vectorworks, then in practical terms expect to lose a bit of precision. If you are preparing drawings for some kind of high precision manufacture then VW may not really be the right tool. However... the reality of building construction is that nothing is actually that precise, and you can get away with "near enough". But it does need some careful thought in how you prepare the drawings, and some sensible allowance for tolerances.

  7. These yuk responses, which of course must be disheartening for the VW employees who put so much hard work into developing these complex tools, could be avoided if the company were to take user testing and interface design seriously, but it's very clear that the people at the top don't. The proof of the pudding is in the eating.

     

     

    • Like 1
  8. I think you'll find that you come up against various things that aren't possible with this tool. It'll let you customise up to a point and not further. And there are some things that you could do with the old version, that you now can't. For example L-shaped corner cabinet with unequal leg lengths.

    • Like 1
  9. 2 hours ago, Pat Stanford said:

    I dont' use Stories or Levels. Can those of you who do please comment on if there is any benefit to using them if you are not using Walls and PIOs that can automatically associate with the levels?

     

    If I am only using modeled solids that won't automatically adjust when I change levels is there any benefit for me?

     

    As l said above, the ability to use elevation benchmarks is benefit enough for me. Even if no objects are actually associated with them.

     

    I no longer need to have the bit of paper stuck next to the screen with a project's significant levels written on it.

     

    Part of the attraction for me is that I don't really like giving layers elevations, because I like to be able to paste-in-place between different building storeys. Having a single storey with a number of important/useful "levels" proves to be a good way of keeping Z values organised and recorded. For me and the kind of projects I do.

     

    I find it quite satisfying/reassuring when I can make, say, a steelwork setting-out drawing and with a couple of clicks have things like finished floor levels, or top-of-steel levels, or whatever appear in the right locations in viewports.

    • Like 4
  10. I think it's because you've got "display 2D components" turned on. So it is drawing the 2d component of the symbol rather than rendering directly from its 3d geometry.

     

    To make it coloured you either need to turn off "display 2D components, or edit the symbol's 2d component so that it has the colours you want.

  11. 5 hours ago, E|FA said:

    If you're doing that why use Stories at all?  Take a look at the original post in this thread to see the No Story workflow.

     

    Like Zoomer says, it's mainly about accessing Levels.

     

    The parametric possibilities are one reason, but also the ability to have reference levels that I can use to create elevation benchmarks on elevations/section viewports. Even if I never really change the levels, I find them very useful for making sure everything is in the right place. It's a visual check that things are at the correct height relative to things like finished floor levels, and is also useful when I have "existing" vs "proposed" and need to match a height somewhere. I like that the elevation benchmarks will always be correct automatically. Similar to grid lines in plan views.

    • Like 4
  12. Do you have "use original" selected here?

     

    Screenshot2024-01-03at12_18_41.jpg.8bbd48483e18788780cc51f19f8befa2.jpg

     

    That controls what any objects seen in elevation will look like.

     

    If you also want the objects to retain their colours where they are sectioned, you'll need to select this too:

     

    Screenshot2024-01-03at12_20_33.jpg.e14e1a8ed50d0d6327ddfce6459ba81f.jpg

  13. Is it a building with multiple levels, and are those multiple levels repetitive?

     

    If not, just put everything in one storey. Then you don't need to worry about storey elevations. Just have a zero datum for the whole thing & relate all your levels to that.

    • Like 1
  14. There's something wrong with the way this works. It often seems impossible to find the legend that's supposedly been created (even using the custom search).

     

    I have to resort to copy-pasting one in from another file, and then all new ones in that file are made by duplicating the first one.

×
×
  • Create New...