Jump to content

line-weight

Member
  • Posts

    2,788
  • Joined

  • Last visited

Everything posted by line-weight

  1. Here are the notes I wrote to myself when I was last trying to puzzle out how the grid tool works..... Put grid line objects on dedicated “grid” layer Put them in class “none” (to make sure they’ll appear in all viewport annotations) Grid line objects can be styled. Grid line style has design layer grid line instances called “grid line definitions” (drawn on “grid” layer). Each design layer grid line definition has its own letter/number (label) Each definition has a real-world start and end point. Then each of those has multiple instances in viewport annotation spaces Changing “show bubble at” in a definition doesn’t change already-drawn VP instances Changing “shoulder length” in a definition does change already-drawn VP instances Changing start & end points in a definition does change already-drawn VP instances Changing “bubble scale factor” in a definition does change already-drawn VP instances To avoid confusion, when drawing grid line definitions in the grid layer, leave shoulder length and bubble scale as per style. Changing attributes in VP instances only applies to that VP instance. [for now] attributes of grid line “lines” and “shoulders” set within style and not by class, and take on class of object (none) A kind of default “Shoulder length at” and “show bubble at” can be set within grid line style, and will apply to any newly drawn definition, but can be overridden in any definition and in any VP instance (in the OIP) Grid lines should appear in any viewport: – where GRID layer and none class are visible - where they are perpendicular to the VP view direction - where they are within (or intersect with) the VP’s crop - where, in the grid line definition’s OIP, under “grid line instances”, the relevant viewport has a tick against it. NB therefore grid line visibility in viewports is controlled by the definition’s OIP, not within the viewports’ OIP. A GL instance’s start & end in a VP are determined by the crop box (unless real world start/ends as drawn on Grid layer are inside the crop box. But can then be overridden manually. Manual adjustment will be remembered if crop box subsequently changed.
  2. I never use hidden line in design layers so am unfamiliar with how it works.... it seems the teapot is there for a while, then disappears, but it's not actually finished rendering yet, and there is then a green "Stopping Render" message in the bottom bar...and then at some point that eventually disappears and it's finished.
  3. Hrm... I posted the screenshot above, went away and had my dinner and stuff, then came back to the computer to find it looking like this... so it had maybe not entirely finished doing its render.
  4. Here's what I get on my mac mini
  5. This has just reminded me I was going to give this app a try as recommended by @E|FA
  6. I'm too lazy to use the space bar - I'd have to move my left hand several centimeters. Moving my right thumb a few millimeters is just about an acceptable amount of effort. Also - space bar is so commonly used for panning, in all sorts of applications, I'd be worried I'd confuse my brain/muscle memory if I started using it for something else in VW.
  7. I mean this thing, (smart options display?) It works for me because I just press one button and all the options are there visually for me with icons my brain has already learnt to recognise.
  8. I just use one of these https://www.logitech.com/en-gb/products/mice/m705-wireless-mouse.910-001949.html I like the weighted scroll wheel, the scrolling is smooth and you can scroll rapidly by sending it spinning. Only thing I don't like so much is the two buttons in the thumb position, they are a bit awkward because where my thumb naturally sits, it presses both of them at the same time. But I have the VW "quick actions" menu mapped to come up when I press those. I find there are only so many macros and mapped buttons that I can keep in my head at once so a mouse with a zillion buttons isn't that attractive to me.
  9. If anyone is willing to indulge me....
  10. Curious to see how the different the picture is when dealing with non-renderworks viewports. Open the attached file (sorry, it's quite large); it should already be looking at the sheet layer as per screenshot below; select all three viewports and press the "update" button to update them all. On my M1 Mac Mini 16GB it took 2 mins 48 seconds. 1049605006_vportrendertime.vwx
  11. here I have made the "value rating" (renders per day) / (price) x 100 Higher "value rating" means better value
  12. because it looks like it's fixed by "repairs" to the VW application itself, I'd assumed that sending a file is not necessarily going to produce something replicable, because it somehow depends on the state of the application as well as the state of the file itself.
  13. Just happened again - when I tried to resize a window opening. Resize the window opening (either using the handles on the object, or by typing a new value in the OIP) and the holes fill in, throughout the model. Undo reverses it, trying the same again, the problem is replicated. It seems to happen if I resize either of the openings on that particular wall - but not if I try resizing openings in other walls in the model. Fairly sure I've re-sized those openings a few times since I previously did the "repair" on VW, without issue.
  14. Above^^^ in bold is what doesn't make sense. Those two conflicting observations. If numerator = speed and denominator = price, then a high "value rating" number = better. If a high number = better, then the M2 Max MBP should be getting a higher value rating than the i9 iMac. But it doesn't in the table. I think a calculation is going wrong somewhere.
  15. I get the basic idea of value - just meant that the numbers in the table don't seem to make sense.
  16. I don't understand the "value" figure. For example M2 Max macbook pro gets 0.0016 and i9 iMac gets 0.0028. They both cost about the same but M2 Max is loads faster. This suggests lower number = better. But ... M1 Macbook Pro (0.0051) and M1 Mac Mini (0.0110) take roughly the same time for the render, with M1 Mac Mini being half the price. This suggests higher number = better.
  17. Glad to see 16GB M1 Mini winning on value 👍
  18. Yes - although I lost all of my door and window openings in that model, when the problem suddenly happened. Not just in that wall. The only unusual thing I did to that wall, that I can think of, was to use the "resize" handles to change the shape and size of the window openings, something I'd not tried before because it wasn't possible in earlier versions of VW.
  19. Even if you don't click away, it still gives wrong results (often shorter than the reality). Plus, I find it takes a while to start counting after I press the "update" button.
  20. I don't know! Same result here (but this is after doing a "repair" on my VW2023 install). Also, moving it by 0,0 will solve it yes, it does somehow come from a messy wall connection. It is inherited from a "as existing" model which has been changed to the "as proposed" but I have not got around to cleaning up that old connection. Below is what it looks like in the "as existing" model, both in "problem" and "healed" states. As above, no it's not needed in the "as proposed" version. The door opening is enlarged compared to the original.
  21. Are you all reporting the time Vectorworks gives you at the bottom of the screen when it finishes the render? Reason I ask is that I realised the other day that this number usually does not correspond with reality - if I measure with a stopwatch I get a different time from the one VW claims.
  22. Sample file attached. This wall has one door and two window openings in it. None of the fixes mentioned earlier in the thread worked for me - except for running the "repairer". Said it fixed 100 files. When I reopened VW, and the file, and then did a 0,0 move to the wall, the holes re-appeared. wallholes.vwx
  23. You can make a title block style which is set to "auto generate page number". I'm never 100% confident I know what's going on with that, but if you make a first instance of the title block and duplicate it, you get a second instance which gets numbered two. I just tried doing a duplicate array of such titleblocks and managed to create 300 of them numbered sequentially from 1 to 300. So if you got the dims right you could overlay these onto your page grid as well as the GL cells. All starting to deviate a bit from what all these things were really designed for though! As for producing individual PDFs ... there must be some kind of PDF editing app that can split a multi-page PDF into individual pages. But of course maybe you would not end up with sensible file names.
  24. This has just happened to me in 2023 SP3 too. Door in wall, all fine. Changed the door size and suddenly it's not cutting a hole through the wall. It looks OK in top/plan view but not when I look at it in 3d. Moving it in and out of the wall doesn't solve it. VW thinks it's inserted because it shows as "door in wall" in the OIP. Starting to regret moving to 2023 now... Screen Recording 2023-01-30 at 19.39.49.mov
×
×
  • Create New...