Jump to content

line-weight

Member
  • Posts

    4,266
  • Joined

  • Last visited

Everything posted by line-weight

  1. Is that a report that has a ready-made template somewhere? Isn't "current revision" part of the "revision data" rather than "issue data"? It's only mentioned in the revision data bit of the dialogue. Yes, I think it would be good to make it clear when editing issue data that you are editing it document wide. But also, I think it could be made clearer what's happening when you delete an issue from a TBB, and you get this dialogue I find this wording confusing. To me it would make more sense to say something like: "Remove this TBB from the selected issue(s), or remove all TBBs from the selected issue?". or "Remove this TBB from the selected issue(s), or delete the the selected issue entirely?". I realise it might look different from a programming point of view, but from a user's point of view, a TBB is included in an Issue, rather than an Issue being included in a TBB.
  2. @Nikolay Zhelyazkov I think it is really critical that we are able to retrospectively edit "issue" information. I've just had an experience where for some reason, VW decided that a new drawing that I created within the last couple days had already been included in several drawing issues some weeks ago. My guess is that this might have happened because I created it by duplicating an existing drawing. I thought I might have to either reconstruct the entire issue sequence, or manually block out the cells in the worksheet where the wrong information was showing. In the end I managed to sort it by going to that specific TBB and editing its "issue data" - deleted the issues it shouldn't have been in and luckily got what I wanted in the drawing register ... but I didn't feel entirely in control of the process and this is definitely not what you want when you are under a bit of time pressure to issue a large set of drawings. One thing that is not clear to me is exactly how the "issue data" and "revision data" are connected to each other. For example, if I go into the issue data of an individual TBB and see this: I can see that I can delete some or all of those issues (for this TBB) but let's say that I want to change my drawing register so that it was revision B of this drawing that was included in issue no. 3, instead of revision C - can I do that? Highlighting one of the issues and pressing "edit" doesn't let me see or change that information. Also, presumably if I "edit" one of these issues, then I edit it for the whole file? Because it doesn't make any sense to edit, for example, the date of an issue, just relating to one TBB. Assuming that's the case it feels wrong that I am able to edit something that applies to multiple TBBs when I've got there from an interface that's about one specific TBB.
  3. In the ideal world, where infinite time was available, of course it would be best to update the whole set. But in the real world (especially when a project is in construction phase) you need to prioritise the information that goes out, so you may want to revise certain drawings, the ones that are important at that time to communicate something particular, and get them out as quickly as possible, rather than spending lots of time tidying up a large number of drawings that aren't actually that critical to what you are dealing with at that point in time. Generally those other drawings "catch up" in a later revision. It's never the case that a change in the model just automatically makes everything else update perfectly - the reality of modelling in VW is messier than that. For example, there is usually a load of stuff in annotations space that needs to be adjusted manually.
  4. When I drew in 2d, each drawing sheet was largely independent of the others in a drawing set. That is (with some exceptions) it was mostly the case that if I changed a drawing on one sheet it wouldn't change things on other sheets. So if I have drawings 001 through 010, and I've made revisions to drawings 002 and 006, I have two choices: a) issue just the revised drawings, 002-B and 006-B b) re-issue the full set, 001-A, 002-B, 003-A and so on. Option (b) is often useful, especially that drawings now tend to exist in PDF form rather than on paper, because it reduces the risk of anyone looking at out-of date drawings. They can always just look at the latest issue, and this will contain all drawings in their most recent revision state. However - this all becomes more complicated if the majority of your drawings are generated from a 3d model, because as soon a you change anything in the model, it's likely to cause a change in multiple drawing sheets. So, how to deal with this if I want to re-issue the full set, but keep many of the drawings in an unrevised state? a) Simply not update any viewport that I don't want anything to change in. But this feels very precarious and prone to error. b) Export only the altered drawings, then manually substitute them (as PDF pages) into the previously issued PDF set. But this is rather tedious. c) Change the revision number on every drawing each time I issue the set, whether or not anything's actually changed. But, this can cause confusion and a lack of clarity about which drawings have changed, and also means going through and checking every sheet to make sure unexpected things haven't happened in any viewports. Anyone have a better system? It would be very useful if there were something built into the VW "Publish" function that solved this issue.
  5. It seems that currently it's not possible to upload JPGs to include in posts. See screenshot below (which I had to convert from JPG to PNG to be able to upload it).
  6. Have a look at the thread @Tom W already linked to further up: https://forum.vectorworks.net/index.php?/topic/106776-catalog-objects-very-confusing/ The way it works is confusing (I'd have to reread that thread myself to remember exactly what the issues are). But in any case these catalogues aren't up to much in the end, because the limitations of the window tool mean that it's not possible to properly model any real world windows in any detail.
  7. I guess it is useful if you don't have any hand-drawing skills. And maybe those skills will become ever rarer as AI becomes more widespread? I like to imagine that somehow, having these skills ("talent", even) might keep just a little bit of an edge over what AI can do but that might be fantasy. The same applies to the design skills themselves (rather than drawing/presentation skills). AI will start making inroads at the lower end of the market first, design-wise - those who churn out variations of semi-standardised designs will probably be the first victims.
  8. Thanks, I'll have a look at what's going on with memory next time it happens (the M1 has a kind of shared RAM/VRAM arrangement). By sampling quality do you mean in the rendering settings? Would a too-low setting here cause inconsistent results though (ie. sometimes it works fine and sometimes it doesn't)?
  9. Well, yes, but that seems to defeat the purpose of having a dedicated brick shader!
  10. I think you are right. I don't feel the Help really explains properly. The bit in green implies that I should use the image of a brick face but doesn't warn me that it's going to tile it. It also doesn't tell me that it's going to stretch it vertically - as far as I can see it takes my brick-shaped image and distorts it into a square. What I actually need is a fully tileable square image, it seems.
  11. I thought briefly that setting an "alt brick" fixes it, but no, it's still a mess:
  12. Am I doing something wrong here? This is my brick image (I have put the red and green lines there to help work out what VW is doing with it) And here are the settings I'm using (I'm using blue for the mortar or "gaps" again to help make clear what's happening) And this is the result The mortar lines are drawn correctly, but what's going on with the brick image? It isn't placing one brick image per brick. It seems to be sort of stretching it into a square shape and tiling that but also doing something odd between bricks. Is it that it doesn't work, or is it me doing something wrong?
  13. I'm afraid I don't use referencing much, so am not really sure how to make this work. I think that you can reference the design layer (containing the DL viewport) into another file, and if you then want to look at the section straight-on, you can choose the appropriate view (front/side etc?) and then use this to create a sheet layer viewport in the file. So you then have a sheet layer viewport looking at a design layer viewport. I'm not sure if this would be helpful for you anyway though. Whenever I try and use design layer viewports, I tend to find various difficulties arise so try and avoid having to do it. Someone else may have better advice here.
  14. I wish we could just define a plane and use that to make a section cut. It sometimes requires some gymnastics to get what you want, in complex situations where the relevant elements aren't visible in a standard view.
  15. This kind of stuff (just for example - randomly found on google). https://haldaneuk.com/projects/timber-handrail-helical-staircase/
  16. A smooth, relatively large radius transition top & bottom. Ideally we would be dealing with a circular or oval -section handrail (it may also be a more complex, extruded shape).
  17. So, the sweep + fillet method works rather well. It actually lets me extract edges from the resulting object, which I can compose into a single NURBS And then use as a path object for whatever profile I want: All of this preserves the curve on plan very well. It doesn't quite give me the holy grail for handrails, which is a path that doesn't have any twist along its length. This is always a problem if you want a non-circular handrail. The path always has some kind of twist in it which produces results like this (I know I can tick the "fix profile" box in the EAP dialogue that partly resolves this, but it doesn't keep the profile section "normal" to the path which causes issues on steeply rising handrails)
  18. Thanks! Sweep - another tool I don't make much use of. Will have a look at it.
  19. Ok - attached is another file; this shows something more like what I was actually trying to model (but simplified). The green nurbs curves are where I want a continuous handrail to run. But I want a smooth transition from the handrail that follows the rise of the stairs, the the horizontal handrails that follow the edges of the landings top & bottom. And ideally I want some control over that transition - so that I can adjust the radius of the transition curve in the same way I might adjust the radius of a regular fillet between coplanar lines. handrail_arc.vwx
  20. It seems to me that unfortunately NURBS curves just can't really be used for many things that need to be precise. It may sound fussy but it causes problems when trying to model something like a stair handrail, because any small imperfections in the NURBS curve can be magnified if you use it as a path for an extrude. (These things are often also very hard to build in real life, of course)
  21. I just tried this a bit. It's not that clear exactly what is happening with each of the options. One of them keeps the resultant curve quite close to the circle line in plan. However, there's no control over things like how sharp or gentle the transition curve is, so it doesn't really help with drawing anything very precise.
  22. Are you drawing a section-elevation line on top of teh viewport, and then trying to use the "create section viewport" button in its OIP? If so, the section-elevation line needs to be drawn in the annotation space of the viewport, for this to work. This needs to be made clearer to the user, I think. Because if you just attempt the operation with the section-elevation line drawn on top of the viewport in the sheet layer, you get this error: And this is unhelpful because what it tells you to do ("select an .... viewport") is not what you need to do. What you need to do is go into the annotation space of the viewport and draw the line there. However @Amarin you don't actually need to go through this process using the section-elevation line tool. You can just select the viewport, then go to the "view" menu, choose "create section viewport" and then you can simply draw a line over the viewport.
  23. Do design layer viewports not work for this? https://app-help.vectorworks.net/2024/eng/VW2024_Guide/Viewports1/Creating_design_layer_viewports.htm
  24. Thanks - yes, now I see what you mean. This gives me a locus point at a certain point on the curve, and I can then move one of the interpolated vertices to sit on that locus, but I still have the problem that if I then change that vertex's z value, the line of the NURBS curve strays off the circular path in plan.
×
×
  • Create New...