Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by M5d

  1. When you publish a drawing set as a PDF, the viewport names become the Bookmarks Adobe presents in its Bookmarks side bar. This makes navigating PDFs much easier.
  2. Been wondering the same . . . I think the problem with the eyedropper has been, it just treated classes and layers like numerical lists between files. Hopefully, this identifies like for like naming and notes the differences . . . ?
  3. I haven't switched to 2023 yet, but I have noticed this or a similar inconsistency in how mapping renders between the Shaded and Renderworks modes in 2022. Have a look at which Map Type the offending objects use, try using Auto-Align Plane if it is not, or just resetting it off and then back to Auto-Align Plane. That works with the 2022 Renderworks modes, but of course, it is not suitable for all geometry.
  4. The Roadmap is leaning mostly towards enhancement at the moment, an interesting (positive) shift of emphasis maybe . . .
  5. A couple workarounds to prevent the drain tool from selecting the loci: 1. Place the loci or guides on the Layer above the Slab with both Layers on and Show/Snap Others selected. The Drain tool will snap to the loci without deselecting the slab when you place the drain. 2. Use Sent to Back to place the loci behind the slab on the same Layer. Activate the Drain tool and use the 'B' key for X-Ray Select Mode to snap the cursor at the loci's position, then release the 'B' key before placing the drain.
  6. To use the Frame in this way, you can also use the Set Frame To: option in the OIP and select Wall Thickness. Setting the Frame width here makes certain the reveal is removed.
  7. Thanks, got it. The difference is I set the frame size and position to match specific window and door series, which requires the reveal. The offset is behaving the same either way though (from the frame), it's just that the architrave is fixed at half its thickness once Windoor creates a reveal.
  8. Hi BG, I had no luck with that. There must be another quirk or point of difference in your setting to get the offset working that way. Any chance you could post an example file with your all settings?
  9. If you're referring to the offset between the Architrave and Reveal, not that I'm aware of. The two elements do not have fully independent controls in WinDoor. It defaults the Reveal to the Architrave's thickness and offsets the Architrave by half. This is a common detail however, but independent thicknesses, the ability to recess the reveal into the frame and an Architrave offset control would have been great additions . . . not to mention custom profiles, alas!
  10. • In the WinDoor OIP, select the dropdown - Window/Door Type: Sliding Left Door or Sliding Right Door • Then, also in the OIP, select the dropdown - Number of Doors: 4
  11. If you want to go a step further, you can convert your transom window into a 3d symbol / geometry named WD-Symbol 3 (remove trim) and then have Windoor replace the upper opening with that symbol.
  12. That's true, but @JustinVH has just painted a stark picture of .vwx's standing in BIM, which I assume boils down to ROI? From the site he referenced: bimobject downloads
  13. Something does seem to have changed in recent versions though. There's an issue with desaturation via image effects reverting when exported to pdf (maybe related?) and all viewports now appear more saturated in the pdf versions. This is a recent development, they've always been very consistent between Vectorworks and Adobe in the past (on the same hardware that is). By contrast, when using Adobe to export these images out of the pdf and into an image editor, then back into the pdf, images remain consistent as viewed (roundtrip) between Adobe and other software, i.e. you get what you see from one to the other both as original and edited. Printing is understandably variable, but there shouldn't be an obvious and consistent discrepancy between two softwares on the same hardware, should there?
  14. Thanks, bookmarked. I'm hopeful we'll see the Mac version of Enscape / VW this year. Keep an eye on . . . as a possible future partner to replace the VBvisual Tool?
  15. Looks like it went into liquidation January 2nd. You'd expect NV would have been notified at the time. Hopefully the library gets repurchased by another entity and NV renegotiates or NV looks at purchasing it themselves. I assume in these circumstances, the remaining assets typically go to the highest bidder, but it would be a pretty awful outcome if the library simply ceases to exist.
  16. Not a hundred percent on the objective of your question, but I'd avoid having several walls as a means of representing a single entity. The hatches defined in wall components will stay relative to the wall's direction in plan, if the hatch has Rotate In Wall selected. And if your wall components are visible (with different heights) in elevation, you can give each component an individual texture with a Surface Hatch defined and set Use component textures as the default in the Wall Style's Texture dialogue.
  17. I continued to wrest with this. If I had to guess at a cause, I'd say the larger the image size (perspectives in particular), the less likely it is image effects will stick in an export. I also downloaded 2023 to check if the issue has been resolved, nope! Tried several tweaks before exporting, all in-date viewports, switching image effects off and on + minor adjustments, no luck. The solution is adobe acrobat and an external image editor. The way image effects have been implement on viewports makes them near inaccessible anyway. If you attempt to work in the background during a render, image effects get locked behind the out-of-date viewport.
  18. Moved to 2022 in December and have the same problem, image effects, desaturate, exposure etc, not exporting to PDF, strangely soft edges still works. I tried @line-weight's idea and raster without success, any other quick solutions / workarounds would be much appreciated.
  19. Couldn't edit my post for some reason; scratch the above, you have multiple sections of the same wall style, they'd all be wrong if it was the Core.
  20. Where you have the two wall styles end to end, you can use the corner (L) join mode. I tested your example though (in 2022), without using a join, and the slab tool still worked . . . so maybe check both Wall Styles have the same / desired Wall Components selected as their Core.
  21. If you want the stud and gypsum to remain at their default construction heights, deselect the 'Follow Top Wall Peaks' option in the Wall Component Settings, or in the Wall Style itself if you want this as the style's default behaviour. You don't need to do this before you reshape a wall, the stud and gypsum will reset to their default heights once you deselect the Follow Wall Peaks option for each component.
  22. No good solution unfortunately. What I typically do is create duplicate Structural members and have a separate class for the modified members. Then you can pull data and display either where appropriate, using viewport overrides. This has been on the wish list, as are many good things, for some years now.
  • Create New...