Jump to content

M5d

Member
  • Posts

    460
  • Joined

  • Last visited

Posts posted by M5d

  1. 9 hours ago, Mykbee said:

    Hi,

     

    Apologies if this has already been answered, or is really obvious, but I can't work it out.

     

    I haven't made the leap to VW2024 yet, so I cannot speak for the latest edition, but this is a known limitation of the software. 

     

    There's a (cumbersome) workaround for the problem and a wishlist item from 2018 in the posts below. 

     

     

     

  2. Same here, Mac Studio + Studio Display. If Vectorworks is left as the current desktop of Spaces and the screen saver activates, the monitor will (often) go to full brightness and the brightness keys will stop working. 

     

    I did contact Apple soon after purchase in 2022, but they had no other reports and I soon worked out the bug only occurred with Vectorworks.

     

    Most of the time you can just switch spaces and the brightness keys will start working again, occasionally not, at which point I just close and reopen Vectorworks. And if you can remember, switching away from your Vectorworks desktop before leaving your computer for any length of time will prevent the bug happening. HTH

  3. On 9/21/2023 at 9:11 AM, CW2020 said:

    What are some of the uses for naming a viewport?

     

    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. 

    • Like 1
  4. 2 hours ago, line-weight said:

    I don't quite see how control of class or layer visibility could be part of a viewport style. Because styles are independent of individual files, but two files can have entirely different sets of classes.

     

    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 . . . ?  

  5. 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.

     

    MapType.png.617fb230c36be99058b905e694675b9a.png 

    • Like 1
  6. 23 hours ago, Matt Overton said:

    Yes so far...

    - UI 

    - Viewport styles

    - Fence tool 

    All great 

    I guess by the icons and roadmap

    - Cabinet tool 

    - Teapot so so rendering - Shaded render improvement.

     

    The Roadmap is leaning mostly towards enhancement at the moment, an interesting (positive) shift of emphasis maybe . . . 

     

    Scheduled.thumb.jpg.dfae8e75756245b5138c09baf301d7fb.jpg

     

    InDevelopment.thumb.jpg.8d83a32406583ebef48abe4d4bbdd0a0.jpg

     

    • Like 1
  7. 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.

     

    ShowSnapOthers.jpg.ed5a6c1b7d39660136f0fc66a72e2374.jpg

     

     

    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.  

     

    SenttoBack.jpg.65f0e5783d661bae1d641fa1fcd4594c.jpg

    • Like 1
  8. 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.   

    • Like 1
  9. 3 hours ago, BG said:

    Try setting the offset (3) to the same thickness as the window frame member thickness. This eliminates the offset for us.

     

    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?  

  10. 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!

     

    • Like 1
  11. On 6/2/2023 at 7:23 AM, SharonP said:

    Does anyone know how to do a windoor object that has one door sliding each way like this but not being cavity sliders?  I can't seem to work that one out.

     

    • 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

  12. 7 hours ago, jeff prince said:

    Thanks for the explaination!  Though it is a shame.  Perhaps if they realized that landscape architects like me are more likely to spec their product if I can easily represent it in my models they would change their tune.  I've passed on several stone veneer and paver companies because they would not make their textures available beyond what was shown in their catalogs.

     

    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. On 2/23/2023 at 1:15 PM, Ben Beaumont said:

    Keep an eye on Globe Plants. They are doing great stuff, with Vectorworks content also. 

     

    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.

     

    1612289567_RotateinWall.thumb.png.e09881d1edb61d0ccda76a641b9246f0.png

     

     

    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.  

     

    1975270512_ByComponentTexture.thumb.png.6011a337473cc1bec47f54f799d9039b.png

    • Like 2
×
×
  • Create New...