Jump to content

Search the Community

Showing results for tags 'surface hatches'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs

Categories

  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Occupation


Homepage


Hobbies


Location


Skype

Found 1 result

  1. Past week I was working on a project where i needed to use surface hatches. I think it can be implemented beter. When i was thinking about this i realized its 'bigger' then only the surface hatch part. To be honest i think there should be an overhaul of how classes work an what you can do with them. In general classes should have to ability to work as materials. This would mean you would create a class for every material with al the specifications needed (including R-ratings and other properties like weight/m3 etc.) With the new forum its easier to look for previous comments and discussions about this. I will included these because some things i borrowed from there. MOCKUP AND WISHES: ability to create 1 material / classes that you can set to use different settings for different scale. When you create a viewport (1:10) on a sheet layer that's different then the scale on your design layer (1:50) it automatically uses the properties of 1:10 instead of 1:50 This option could work as class overrides do now, but more automated. For every material you can set Lambda values so you don't have to do that in your wall style. The wall styles gets the options to use the values from your class or material or just use a different value. This should work like the attributes palette works: it can be set by classes, but it doesn't have too. Ability to use hatches and tiles in surface hatches. (I'm never been able to create in a simple way a hatch as I can with tiles) I don't like how hatches work together with textures. I think this should be 2 separate things that can work together but don't have to. It should not be part or your renderworks texture but something you can set separate. Beside that I think its confusing that you have a scale for the hatch in your recourse browser, as well in the renderworks edit texture. At the moment if you change the scale of your resource it changes in the renderworks texure as well. In someway this is logic but it worked unexpected for me. You should be able to change in % the scale of your hatch in the class/material without editing the resource in the resource browser. For a section and a surface we should be able to set different hatches without overrides, so lets split that up in different options. I wanna set the pen, fill, hatch, opacity, scale, thickness separately for: sections plans elevations

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×