Jump to content

shorter

Member
  • Posts

    4,164
  • Joined

  • Last visited

Reputation

1,517 Spectacular

9 Followers

Personal Information

  • Occupation
    Architects specialising in Vectorworks Production Management, Sales, Customisation, and Training
  • Homepage
    www.stevenshorter.com https://www.linkedin.com/in/stevenshorter
  • Location
    United Kingdom

Recent Profile Visitors

12,542 profile views
  1. Is there a magic trick to getting Psets like Pset_LandRegistration Pset_PropertyAgreement to export as IFC4, in Vectorworks 2024, as part of IfcSite? Real-world answers on a postcard please.
  2. I was concerned there may be background activities reliant on web dialogs...
  3. You have components set to join in capped mode?
  4. Just looking at the requirements for Vectorworks 2026 compared to previous versions, and specifically 2024, and the only difference I can detect is that 2026 requires min. OS on the Mac of macOS 14 (Sonoma), and that Vectorworks 2024 is not supported under Tahoe. One would assume that since Vectorworks 2024 appears to run fine on Tahoe, and on the basis that the underlying hardware falls within the limits of the specification for both, i.e. 3.0GHz Intel Core i7, Apple M1 Max or higher, min. 2.0+ GHz Intel Core i7 or better. upgrading to 2026 would not be necessary simply because someone has bought a new Mac amongst a host of older Mac purchased in 2019 but meeting or exceeding the above specification?
  5. Odd, because it works in 2025, and in the help for 2024 it would appear to work. Vectorworks walls, arrive with an IFC data structure for IFC4 with IfcBuildingElementPart present too. Oh, well, we will just have to say we can't comply with their requirements.
  6. using a condition =IF(OBJECTDATA('Component', 'Function', T=INDEX)='Load-Bearing', 'IfcBuildingElementPart', IF(OBJECTDATA('Component', 'Function', T=INDEX)='Inner Finish', 'IfcBuildingElementPart', IF(OBJECTDATA('Component', 'Function', T=INDEX)='Outer Finish', 'IfcBuildingElementPart', IF(OBJECTDATA('Component', 'Function', T=INDEX)='Insulation', 'IfcBuildingElementPart', 'NoExport')))) fails. All components export as IfcWall.
  7. If I use the condition =IF(OBJECTDATA('Component', 'Function', T=INDEX)='Load-Bearing', 'IfcWallStandardCase', IF(OBJECTDATA('Component', 'Function', T=INDEX)='Inner Finish', 'IfcCovering', IF(OBJECTDATA('Component', 'Function', T=INDEX)='Outer Finish', 'IfcCovering', IF(OBJECTDATA('Component', 'Function', T=INDEX)='OTHER', 'IfcBuildingElementProxy', 'NoExport')))) the wall is converted to an IfcCovering and does not export as IfcWall at all. Think it may be time to delete preferences and start again?
  8. When you click 'Export Options - Export as Separate Instances' the Wall is exported as it's constituent parts but not as an IfcWall with it's parts as it is in IFC2x3. Each part is exported as IfcWall, not IfcBuildingElementPart.
  9. In IFC2x3, there is a button to export walls by component. In IFC4 is it more complicated. How would you set a condition to export all components as IfcBuildingElementPart, like IFC2x3 does?
  10. To further complicate things, I am trying to do this in Vectorworks 2024...
  11. Why, when I set a condition for a wall, as per the example here https://app-help.vectorworks.net/2024/eng/VW2024_Guide/DataManager/Data_mapping_examples.htm#h do the walls become an IfcCovering?
  12. ...or conversely the IFS sets you up to be able to change individual values... I am forever thinking 'WhatIFS?'...
×
×
  • Create New...