Vectorworks User Interface Overhaul

[Thomas Wagensommerer 52]

 

brown - purple - yellow - blue REALLY?

 

Looking at screenshots from VW 2018 makes me extremely sad. Seemingly Vectorworks is the last application adhering to the kindergarten color scheme.

 

A design application must not use colors in the interface!

 

Look at any self respecting or professional design application and please get rid of those colors in the interface.

 

 

 

 

Edited September 1, 2017 by Thomas Wagensommerer

[mike m oz 256]

Zoomer, Texture seems to be a more common generic term in usage.

 

I've always understood a shader to be a machine generated texture pattern and a texture map to be an image based texture pattern.

 

Materials as a concept makes sense but only if you start talking about components of objects and defining their appearance in plan view, 3D views and sections in both linework views and rendered views.  Also their properties in terms of energy analysis, weight, strength, etc.  In Vw.  Isn't that what we tend to do with Classes? Classes are the what in Vw with materials being one of the what classification systems.

[Tom Klaber 550]

2 hours ago, zoomer said:

 

You mean in a Building Industry Term ?

I was thinking about Software Terms.

In any 3D and even CAD Software I worked with,

Renderworks Textures would be called Materials

(or "Shaders" in the worst case) and edited in a

Material Manager. Image Textures are called

Textures in short.

 

 

Not sure if it is needed to separate the technical from visual part

of Materials. Focusing on Visualization aspects, I wouldn't mind

much if my Render Materials would have additional cost and

energos data.

On the other hand, when applying BIM components to PIOs,

I would not need to recreate my Concrete setup each time I add

a component for a new PIO Style.

 

Well - to me - the intrigue and power of a concept of the idea of "Materials" is that they contain a myriad of information - as you say - price, weight, R-Value...ect - in which a 2D and 3D visual identity is one.  Therefore - it would seem that the 'texture' - as we call them now - would be an 'attribute' of material - one that would be user-defined - along with the other information and maybe behaviors.  

 

I think you are undercutting an otherwise really great idea.  I think 'Materials" are a new thing - not a reworking of Renderworks Textures.  

[zoomer 688]

I asked for a VW global Material System in VW a few years ago.

I am happy to use one in Bricscad. Archicad has one too.

 

So when I create a new Composition (VW = Wall/Slab/.. Style)

and add a new Ply (VW = Component),

I set basic Ply rules like (variable!) thickness and just pick a

Building Material from my Library with physical information.

So I can use the same enforced concrete, no matter if will be a

Slab, Wall or whatever Composition.

Such physical Material Setups will also have information for

Layer (VW = Class) and Render Material assignment.

Setup for Render Materials is done from Material Manager,

(VW = via Resource Manager)

similar to any Layer/Block/... Managers from global Drawing Explorer.

(VW = separated by Organization + Resource Manager)

 

[Thomas Wagensommerer 52]

On 8/25/2019 at 3:18 PM, Andy Broomell said:

 

As someone who teaches VW a lot, this is the truth. Most of my lessons involve "VectorWorkarounds" 🤣

 

Just open the Workaround Manager, hold down the Makeshift Key and select the Kludge Tool.😂

 

[Matt Overton 231]

13 hours ago, Thomas Wagensommerer said:

 

Just open the Workaround Manager, hold down the Makeshift Key and select the Kludge Tool.😂

 

Is that the new Workaround tool or the legacy Workaround tool?

[Andrew Davies 131]

I like the new workaround tool - but there are things I miss about the old legacy workaround tool so do sometimes find myself flipping between the two.

[Stephan Moenninghoff 221]

Is this latest discussion slightly off topic? I didn't start this thread so maybe I should keep quiet but it could be useful to have this thread for discussions about the *aesthetics* rather than core functionality.