Jump to content

line-weight

Member
  • Posts

    3,715
  • Joined

  • Last visited

Everything posted by line-weight

  1. Thanks for your reply. Regarding the shifted sections - let me see if I can find the time to submit a bug. As an alternative could I just send the file to someone at VW directly, and they can then decide whether it should be submitted as a bug? Thanks for the explanation on the section-elevation line objects...I will have more of a play with this tomorrow. The line thicknesses - I think this is explained by the 'zoom line thickness' toggle not working. I couldn't switch it on, therefore I couldn't see any of the line thicknesses. As you suggested - I did have 'navigation graphics' set to something other than 'best performance'. In fact, I usually have it set to 'best performance' but had changed it to another setting earlier today whilst trying to solve some problems with jerky 3d navigation in OpenGL view (which seems to be worse in 2021 than 2018, at least on my current hardware). When I changed the setting to 'best performance' the line thicknesses appeared as they should - so thank you for that. I am glad the fix for this is not something more complicated. I have to say, having got the line thicknesses back, it's a little disappointing to see that zooming in and out is more erratic and less smooth in 2021 than in 2018. Again - on my current hardware at least.
  2. I have been thinking of a 256GB, partly because that's the only option of the 16GB RAM version that is available "in stock" in the UK just now... otherwise it's a 3-4 weeks wait. My applications at the moment only seem to add up to about 80GB so it seems like enough for apps. Maybe you have some especially large applications?
  3. So, I am preparing to drag myself and various drawings from VW2018 to 2021. Immediately on a test run I am seeing various problems with the way sections have imported. I'd be grateful if anyone can let me know how many of these are known problems/easy fixes: 1. Some of my sections seem to have shifted. There's nothing in the viewport, but if I crop out, I find that the section is there, outside the crop box, and rotated. Both of the sections I've found where this has happened are neither vertical nor horizontal (they are cut perpendicular to a slopnig roof pitch). 2. What were called "section-elevation markers" in VW2018 now seem to be called "section-elevation lines" and the text is displaced from the bubbles. Am I best just to redraw them? They are not linked to viewports, just ones I've drawn manually. 3. Why have all my section line thicknesses changed? I have my sections set up as "separate cross sections" and "use attributes of original objects". So, cut line thickness is determined by the class the object is in. Has something changed here? What were previously thick lines are now all thin lines. For example, I tend to use 0.35 as my "cut line" thickness but to get something looking like that it appears that I have to go and change all my class settings from 0.35 to 1.00. Why is this? 4. Does the "Zoom line thickness" toggle now work differently? If I turn it 'on' then it seems to work as predicted for things in annotations, but not for lines in the section viewport itself. For example, those lines where I've set the class attribute of the sectioned object to 1.0 ... the thickness of those lines does not zoom, whether I have "zoom line thickness" turned on or off. Is that a bug? It leaves me unable to judge what the drawing's going to look like when I convert it to PDF. 5. Anything else I should watch out for?
  4. Those of you already successfully running M1 mac minis - what size internal storage did you go for? I am considering going for just 256GB and spending the money saved on decent external drives. Does that make sense? I am assuming that read/write speeds are not absolutely critical for VW, and I would be fine having drawing files sitting on an external disk?
  5. This has been discussed previously and it's one of those things about VW that is more confusing than it needs to be. When you are asked what scale you'd like your layer to be at, it suggests that you're setting something intrinsic to the layer but you're not. You're just setting how you'd like to "view" that layer whilst working in it. It would be much more logical (and useful) to have this as something you choose on the fly, along with things like render mode and projection. I realise there might be legacy reasons to leave it where it is... but it could at least be renamed to something like "scaled viewing simulation" (OK, something better than that, but less confusing than how it's currently presented).
  6. I have a 3dconnexion spacemouse pro and having got used to it, couldn't now survive without it. Strongly recommend one of these if you do stuff in 3d. That's in my left hand and in my right is a fairly basic logitech mouse which does the job fine. It's got more buttons but I really only use left/right click and the scroll wheel.
  7. Yes, possibly I only need the old versions for a "transition period". Make sure everything transfers OK, then I can sell old licence. I am also hoping to switch to M1 macs quite soon - and then anything pre-VW2020 becomes redundant anyway.
  8. Well, I'm currently using 2018, and I can also use 2017 and 2016 - but I did 'buy' each of them at some point (via VSS upgrades). Since 2018 I stopped VSS and now I'm looking at my options for going straight to 2021. For example I can do an upgrade... Or possibly for similar price buy 2021 'new' and then sell my old licence. Also... If I decide to hold out until 2022 that might make a difference. It would be good to know that whatever way I end up with a 2021 or 2022 licence, I could still open drawings in older versions. Just in case of any unexpected problems migrating large and important drawings by 3 versions in one go.
  9. If I buy a license for a certain version, does that allow me to run all previous versions too - or just the one that I've bought? For example if I were to buy a new 2021 license would it allow me to run 2020 and 2019 too?
  10. That's true. Maybe I should say "the pane where your mouse is, or where you last did something, if it's not over a pane".
  11. For me that's a reason to keep it consistent: if you do a thing, it always happens in the pane where your mouse is, or where your mouse last was - and that's indicated with an unambiguous visual cue. I actually think the current blue outline and title might be a little too subtle for something that's quite important. I'd suggest that the orange 'selected object' box could be useful for this too - so that it has a stronger emphasis in the active pane than it does in others. I ought to be able to look at VW and immediately be 100% clear which pane is active but I feel that's not always the case at present.
  12. I get the basic logic of this. But although the Spacemouse is technically independent of the cursor, I think that in 90% of cases, a user would want to manipulate the view which they currently have the cursor over. I can't really think of a scenario where I would have the cursor over pane A, but have pane B selected/active and want to manipulate pane B with the spacemouse. Why would my cursor be over pane A? - If it was because I wanted to do something in pane A before using the spacemouse, then I would have done this and pane A would have become selected/active. So, I would need to move the cursor to pane B anyway, to make it active - thus my cursor would be over there anyway. - If my last action had been in pane B, making it selected/active, then for what reason would my cursor be over pane A, at the point where I then want to manipulate pane B? I would only have moved it to pane A if I wanted to do something to it, in which case pane A would become selected, and I would then have to move back to pane B anyway. Maybe a plausible scenario is that I have been working in pane B, I have gone to the toolbar or a pallette to activate some command, and then I happen to have absent-mindedly left the cursor somewhere over pane A even though I now want to use the spacemouse in pane B. But that would run contrary to what my intuition/muscle memory tells me: an action applies to the pane that my cursor is over (because that's what happens in all other cases, with the exception of when the cursor is over no pane at all). For me at least, the fact that VW trains me to move the cursor over the pane I want to do something to, is evidenced by the number of times that I move the cursor, do something with the spacemouse and then curse things for happening in another pane. In fact... now that I have focused on this, I realise that this uncertainty has generated in me the tendency to click on a pane before doing anything with the regular mouse, even though this is not in fact necessary.
  13. I've just been trying various things to try and understand the difference between "selected pane" and "active pane" but I don't think I get it. For example... I am working in pane A. Its title is highlighted in blue. Then I take my mouse cursor over to pane B. If I just hover over it nothing happens but if I use the mouse wheel for zoom then it takes effect in pane B and pane B is now highlighted in blue. If I take my mouse cursor elsewhere, pane B stays highlighted. I can't see a stage in the process where one pane is 'selected' and one is 'active' - can you explain further? Another thing: and I think this is part of what causes confusion for me - I use a 3dconnexion Space Mouse continually in VW. But this behaves differently from the mouse: if I have pane A selected and highlighted blue, then I move the cursor over pane B, and instigate a move using the Space Mouse, it does not take effect. Instead, something unpredictable happens to the pane A. Sometimes nothing happens, sometimes it spins off into space. To get the space mouse to act on pane B, I have to first make it 'selected' ie. highlighted in blue. Maybe you can see why this behaviour causes user confusion, because when I do things that seem similar in principle to me, different things happen. With the mouse wheel zoom, I simply go to the pane and use it. With the space mouse, I have to go to the pane, click on it, and then do a move. I'm still on VW2018; perhaps some of these things have been changed since.
  14. Yes, having done a bit of reading it seems it would be a bad idea to try and run 2018 or 19 on Big Sur.
  15. I think you need to design specifically for the use case where a pane is on a 2nd monitor. I can't be the only one who wants to do this. I wonder if it should be more of a "window" in that scenario.
  16. The other thing that has bugged me about multiple views since they arrived - and I think it was discussed at the time - is that it's too easy to do stuff and have it happen in the wrong view pane. For example, zooming in or out or changing visibilities. I think normally expected behaviour would be that if your cursor is over a view, then that's the view which is going to be affected if you do something. In VW, you often have to click on the pane to be quite sure that's the 'active' one. The title should turn blue as soon as the cursor is over the pane. This is particularly the case with floating panes on other monitors.
  17. @Josh Loy if you are the multiple view pane expert, can you offer anything on the question I asked here - https://forum.vectorworks.net/index.php?/topic/80100-macos-how-to-keep-vw-floating-pane-alive/ This aspect of the floating view pane's behaviour is quite frustrating.
  18. Has anyone tried running VW2018 or 2019 on it? (Or are they completely out?)
  19. This might be useful for anyone who, like me, is interested in the M1 mini but wants to run more than 2 displays. Here he has 2 extra running: And here with 6:
  20. I'm not sure if this is something that's under the control of Vectorworks, or macOS. I'm using Mojave, and VW2018 at the moment. I have three monitors and I often want to have things arranged like this: Monitor 1: Vectorworks main window Monitor 2: Vectorworks floating view pane Monitor 3: Other things (eg web browser, image viewer, etc) The problem is that I can get this set up, but when I then go to monitor 3 and start doing something in, say, Firefox, the VW floating view pane on monitor 2 disappears. To make it appear again, I have to go to Monitor 1 and make VW active, and then it re-appears. Is there any way of stopping this happening?
  21. My feeling is that while all these ideas for automatically framing around windows and that sort of thing would be really great if it could be made to work.... it's way down the line of things that need to be urgently fixed. Make the windows themselves work properly first, for example. Because if the windows are essentially unusable at a construction detail level, then there's not much point trying to make the walls able to frame around them. And while it would be great for VW to automatically create correct corner junction details in timber frame... can we first get it to work properly with basic monolithic materials like masonry, please. As pointed out above, timber frame corners are not usually mitred in real world construction.... but neither are brick wall corners, whatever VW thinks.
  22. Is the "structural member" tool now reliable and free of bugs? Last time I tried using it, it certainly wasn't. I currently draw all my structural members, and any wall studs, manually from scratch as extrudes.
  23. That's certainly interesting to hear ... it seems I could be confident that it would outperform my refurbed 5,1 classic Mac Pro, where I'm trying to decide if it's worth upgrading the GPU to make it last another year or so before becoming entirely obsolete. The price of a new M1 mini does not make the price of buying a new video card for the Mac Pro look like very good value.
×
×
  • Create New...