Jump to content

Andy Broomell

Member
  • Posts

    2,050
  • Joined

  • Last visited

Everything posted by Andy Broomell

  1. I seem to encounter a number of sporadic bugs related to containers, but they're always hard to nail down or submit JIRA reports about. In 2021 specifically there seems to be an occasional issue with undoing inside containers involving certain object types, where undoing more than once causes geometry to become 'invisible' until you exit the container and re-enter. There's also currently an issue with Clip Cube not working properly inside containers. Other than that, there have always been various container-related issues such as randomly not being able to snap to things outside of the container even if they're visible, or 2D objects behaving like they're on the wrong plane, or view-centering within containers not working, etc.
  2. OpenGL can only show black pixel-based edges; it'll never show an object's pen or lineweight. But using OpenGL background render (no Color, no Edges, w/ AO) with Hidden Line foreground render usually looks fantastic. Hidden Line can of course be slow depending on the model, but it's worked well for me 95% of the time.
  3. Try downloading the worksheet from the third post in this thread, then put the worksheet into your TBB. (The built in Drawing List worksheet is useless)
  4. The fact that it behaves this way in the first place is such a PITA. One workaround I've found (at least if the extrude is still perpendicular to the ground plane), is to select the Extrude, Flip it Horizontal, then enter the extrude, select all shapes, then Flip Horizontal again.
  5. Try going to Tools > Custom Modification. Type is Dimension. Include Viewport Annotations. In the Properties pop up, change the Dim Std for all the Dimension objects (not sure why the pop-up gets weird at this point). Click OK and it should work.
  6. This is a great wishlist item. The "send to back" trick is useful only in limited situations. Currently, for example, there's no way to "highlight" areas on an elevation viewport that's OpenGL (white model shading) + Hidden Line foreground, because the entire elevation has a white/grey fill from the OpenGL render. Color overlays have to shapes on the top of stacking order; you can't send to back. And using opacity isn't ideal, because then it washes out black linework. Another case where this doesn't work is with dimensions (when the dim is centered on the line) because that requires the dimension to have a white fill to obscure the dimension line. There are numerous other situations where fills are necessary and where a "multiply" blend mode on 2D shapes might be useful. (I suppose the main challenge would be it implementing without it being overly complex or affecting exist workflows).
  7. I think you'd have to start by making the pink part "taller" and with equal radius fillets, then using the Z scaling factor that solids have in the OIP to squish it. It'd just take some calculations ahead of time to figure out the correct pre-squished dimensions. Another option would be to use an Extrude Along Path of the negative shape, then subtract that from a regular extrude.
  8. Agreed. And having the option to see the separations between different objects rather that merging sectioned areas. Essentially like a Section Viewport except interactive in the 3D model.
  9. @inikolova Does the 3D web view have Ambient Occlusion? (Haven't checked lately). If not, that should definitely be added to the list.
  10. If your plan and orthographic viewports are going to be 1:50, I highly recommend leaving your Design Layer scale at 1:50. Don't set it to 1:1, otherwise you're not utilizing the benefits such as seeing hatches, linetypes, text sizes, etc. at page scale. Think of Design Layer scale as a "preview" scale for what a viewport would look like at that scale. That being said, Design Layer scale is completely independent of sheet layer viewport scale and one doesn't affect the other. In fact, you can even change your Design Layer scale at any point, and existing viewports will still be at the scale you set them at; they won't be affected at all. Regarding the perspective viewport, if it's small on the sheet when you create it, just make the viewport larger. In the OIP change the ΔX field to something larger. You're literally just setting the width of the viewport in inches. (You could also use the viewport's Scale field, but perspective doesn't actually have scale so it's a bit misleading.) If this doesn't address the issue, you're welcome to include a screenshot to illustrate what you're seeing.
  11. @Daniel B. Chapman off topic, but what font is your “tag text”?
  12. This is great!! The new chaos levels make me laugh 😂 Do the "Create Classes" and "Create Default Symbol" checkboxes currently do anything?
  13. Before you try any solutions, make sure to deselect everything, then in the Attributes palette turn off both of the end marker buttons. Then regenerate the thumbnail by whatever means and hopefully that should work. It's possible that you've been regenerating the bug each time you try fixing it (And no, it shouldn't be happening in the first place).
  14. Not sure if it's possible to make Vectorworks not export PDF bookmarks, though that would be a great enhancement. I usually don't want them either. One solution is if you have Acrobat Reader, you can open the Bookmarks panel, and delete them from there.
  15. The former viewport is set to a Renderworks Style called "B&W Rendering" while the latter is presumably NOT set to this render style. If this doesn't solve it, the other thing to do is go to the Resource Manager, find that Renderworks Style, right click, Edit, go to Lighting tab, and make sure "Apply Lighting Options" is still checked. When this is checked, clicking the Lighting Options button in a viewport's OIP is actually taking you to the Edit Renderworks Style window (same as through the RM - meaning it apples to all viewports using that style).
  16. The first time I tried it something weird happened (might've been unrelated to script), but then I restarted VW and it worked fine in all subsequent tests. Thanks Raymond!!
  17. I only use gobos occasionally but I've always found them to be buggy / unreliable. Sometimes they just don't like to render 🤷‍♂️
  18. We need a way to turn off the display of lineweights for the contents of PDF objects. Currently all geometry is always shown with the full line thickness, regardless of whether the "Zoom Line Thickness" setting is on or off. This can make viewing and interacting with a PDF quite difficult at times. This could be solved in one of two ways: -Make the contents of PDFs respond to the "Zoom Line Thickness" setting like all other objects. -Or, have a checkbox in the PDF's OIP that says something like "Display lineweights" which could be turned on and off per PDF. (Not sure if this is necessary - I'd personally go with the first option, unless there's a technical reason for it to be OIP-based). Video below showing a PDF in Vectorworks and how messy it looks, versus the ability in Adobe Reader to turn off display of lineweights. PDF_Lineweights.mov (Obviously this would only affect vector-based PDFs) VE-101719
  19. I think I found a workable solution by combining this script with another one which I linked to in that thread to first insert all the symbols into the document.
  20. Measurable scale doesn't exist in perspective, so those dimensions won't ever work out the way you're expecting (Annotations is essentially a "flat" overlay that doesn't exist in the same 3D space as your model). To get the look you're going for where dimensions are in 3D, you'd have to dimension directly in the Design Layer. And if you need those dimensions to be visible or not visible in certain viewports, you could make additional dimension classes and turn them on and off as needed per viewport. A pain, but I think that's currently the only way to achieve this.
  21. This script is pretty handy, and still works pretty well despite being 22(!) years old. The only small issue I've encountered is that after the second row of symbols, subsequent rows are placed on top of the second row, rather than repeating the Y offset each time. Any thoughts on how to correct that? The script is still useful despite this.
  22. @MullinRJ - This is fantastic, and in fact is really close to what I was recently looking for in this thread. Any way to adjust the script so that it works on all symbol definitions in the current file's RM, rather than on selected objects? If not, this will make due in the meantime. Alternatively, I wonder if there's a script that inserts one instance of every symbol definition into the document, which could be ran first? [EDIT - This script does the job]
  23. Bump! Because this script is super useful. Also, it appears to work fine with the new Drawing Labels in 2021 🙂
×
×
  • Create New...