[Composite Materials/Materials, K-values, Energos/Uvalues for assemblies in VW]

Currently I am in the process of recomputing many of the k-values for the materials that come shipped with VW there are quite a few things missing when regarding the calculation of K-values and R values - namely - Thermal Bridging.

 

In Ashrae Fundamentals and ASHRAE 90.1 / International energy conservation code - there are values that are calculated separately for :

1. Wood Stud wall assemblies (Cavity Filled insulation batt)

2. Steel stud wall assemblies (cavity filled insulations)

3. CMU Assemblies (i.e. weight/cores grouted, ungrouted, filled or partially filled)

4. ASHRAE Fundamentals (Chapter 26 and chapter 33 respectively)

 

There happens to be a predicament that is caused by composite materials vs traditional material types in VW

1. True R values cannot be determined from composite material k-values due to bridging calculated as noted in ASHRAE 90.1 and/or steel/wood reduction coefficients with insulated cavity walls, and / or concrete / masonry conditions with integrated insulation types. I.e. Masonry with grouted cores, or partially grouted insulated, partially grouted uninsulated, etc...

2. Do worksheets have the ability to subdivide composite materials in worksheets to show their respective counter parts? i.e. wood stud wall 16" o.c. w/ batt fiber insulation (is composed of two materials) - can worksheets show the composite material and their respective integral materials (i.e. batt fiber separate from wood stud wall partition)

3. Calculation of interior and exterior air film - is this automatically integrated into Energos? or should those components be added to each wall type?

4. Given that composite materials calculate composite k-value - based on the percentage of the respective components, an automated method's purpose of calculating UA values would be defeated (I think). Any ideas regarding this?

 

As a result, my question is this :

1. What are the benefits of composite materials? What is their purpose, and how are they helpful to Energos or Energy conservation code compliance - other than finding the percentage value of components in their respective assemblies and multiplying them by their respective k / r values?

 

This will certainly guide the material / composite material process - where i needed to decide to create CMU / grouted / insulated materials as a single material, or as a composite one?

 

I know this post is long winded, hopefully we can have a productive discussion!

Thanks in advance!

[ODBC Drivers / Purpose]

Try installing the latest mysql 8 odbc driver. The native one doesn't work, had similar issues. Also, use the universal driver rather than ansi

 

Also note that you can actually access the database and have your password and login correctly

 

I dont have Mac unfortunately, can't test it.

[landscape area section?]

@Nikolay Zhelyazkov

 

Thank you for your help!

 

also - wish list item added!!

 

https://forum.vectorworks.net/index.php?/topic/101918-graphic-legend-feature-request/

[Graphic Legend Feature request]

Recently ran into a problem in graphic legend referencing. In abstract, I believe the graphic legend tool has the ability to potentially eliminate drawing wall type details by about 50% if not more! Currently I am trying to use the Graphic legend tool to essentially do just that - create details for all the wall types, floor types, symbol types etc...to be used for current and future project in our office. I have succeeded in the most import aspects - extracting component and material information from these elements. There are just a few things missing - a scaling reference (one shown in GRAPHICLEGEND scale) and a number sequence for image cell numbers. It seems they already autopopulate the numbers given that each image can be previewed seperately as image cells (see below). These number can then be used as detail callout numbers from the plan (not necessarily referenced, but indicated / recorded).

 

I think this would be a huge timesaver for many people here.

 

 

DATATAG COMPONENT CALLOUTS.vwx

 

My wish is to be able to extract this information into the dynamic text properties (i.e. #WS_Objectdata(GraphicLegend#, scale) or something similar,

and

#WS_Objectdata(Graphiclegend,cell number) or something similar.

 

But here is the prefinal result!

 

 

I'm attaching my reference file to show the remaining information that can be extracted from PIO's.

[Implement Worksheet wrapping like this ...]

I think it is an almost identical implementation of the new tool. I agree, Graphic legend feature will be a life saver!

[Sorting in DBconnection (sqlite or ODBC)]

ODBC and SQlite remote databases is a beautiful feature in VW. In BIM Software in reference to Architectural Drawings and the entire AEC Industry has possibly become more about referencing information than just simply drafting plans etc...

This is proprietary or generic information about building products, light fixtures, furniture, etc... Managing all of this information from a single source (VW) is extremely difficult. This is why ODBC and SQLITE in VW is so useful! If information can be referenced externally, it can also be Managed externally. Additionally, it can give VW an upper leg on competition with Autodesk Revit given that much of the informational libraries for Revit have been created by Manufacturers themselves. This however can apply record information to generic symbol library and expedite the process of creating massive symbol libraries.

 

These databases can become quite large given the number of proprietary and standard building products. This information can include a lot of information including but not limited to specifications! Currently there is not sorting feature in ODBC and SQlite window. My request is to simply at a sorting function for record information, possibly similar to the way record information is sorted in worksheets database connection. I'm not sure if this is a big ask, but I think this could start the implementation of standardization in offices large and small that use VW

 

[Material Database Connection (Sqlite or ODBC) - Populate db info into Material record properties]

Creating a database of materials and specifications unfortunately is quite a tedious task and not always can be done inside of VW. Currently, when editing properties for materials, all physical / other properties need to be filled in manually. Given the number of permutations for material properties, the task almost seems unreachable when doing this manually (also especially when needing to update the information! )

 

What if we could populate it from a database (say that has a list of information regarding Building product information in HEAT, AIR, and Moisture Control in Building Assemblies - material properties from ASHRAE Handbook of Fundamentals,etc..)

 

 

 

[BUG - ODBC crashes VW2023 upon updating VW document or updating database]

UPDATE - VW crashes If i do not have a key checked off for proper record reference. If it is checked off, the database populates and updates successfully

[BUG - ODBC crashes VW2023 upon updating VW document or updating database]

As noted in the title, ODBC crashes VW after importing tables from ODBC, populating them to the required settings, and assiging the record to an object. When updating information, when I update the VW document from the attached database, it crashes VW. I have not tried this with an SQlite file. Process currently works in VW 2022.

[importing textures]

@Phil hunt

Actually there is, but the path is a bit convoluted.

 

I used sketchup as a stepping stone to import the required textures. If you know how to use it do the following :

 

after installing sketchup - go to sketchucation.com and download the store rbz plugin or find - fredo-import all from folder plugin.

 

What this plugin basically does is it imports all image files from a directory. (this is how i imported over 5,000 textures into my library, and i'm still not done!)

 

Once you import all the images, select all and explode them (that will populate the sketchup document file directory. Once imported and exploded, save the file.

 

Afterwards, import the sketchup file into VW without erasing the geometry inside of the file. Once you do that, it should import as textures.

 

Just be sure to input the correct names of the textures in the directory (especially if they are pbr textures) like texture a vs texturea_bump (I use an open source file renaming utility) etc..

 

Hope this helps!

[landscape area section?]

@Nikolay Zhelyazkov

Thank you! I'll double check the settings shortly.

 

Pardon that I have so many questions but this is quite new to me.

 

I did also want to ask

 

1. Is it possible to get the graphic scale of the image inside the graphic legend? I.e. if graphic legend image scale is at 1.5in =1ft, Is it possible to display it in the legend dataset ( I found it as a resource in the tag reference, but don't know how to call it out in #ws_objectdata# or #graphiclegend# / graphic legend image )

 

2. Is it possible to 'count' every instance of the graphic legend in sequence? (I.e. if there are 16 details, each has a number for reference)

I've been playing around with the database sequence settings, but I don't think it knows how to count every instance...perhaps there is a trigger?

 

Thanks so much!

 

Best

Samuel

[landscape area section?]

@Nikolay Zhelyazkov

 

🤯🤯🤯🤯🤯🤯🤯🤯

 

Mind = Blown

I've never seen a conditional statement like that before in any of the data tags. Is this something new? Is this the only datatag conditional statement format? Just curious if I can read up more on the properties of these conditional statements. There is something to note however, the number is displayed as fractional feet, but the unit of measurement is inches. I have to actually multiply the value by 12 in order to get the correct dimension.  Like so below :

 

#WS_COMPONENTTHICKNESS(5)##fi_14_2#*12@#WS_COMPONENTTHICKNESS(5)#>0:' ' thick @#WS_COMPONENTTHICKNESS(5)#>0:' '

 

Why does it display 1/12 of the dimension? Is it because of units in the document? I've changed the units, still doesn't seem to change the value though. I don't mind multiplying by 12, just curious why it does this.

 

Also, I have created a prototype graphic legend that intended to do the same thing, however, it doesn't work the same as it does for the datatag. One of the things that happens is that after the 1st line in the description, dimensional information reverts back to decimal and displays foot information rather than ft/in information.

I know it sounds confusing. Attaching the file here.

 

Nikolay, Thank you in advance! You're a tremendous help!!!

 

 

DATATAG COMPONENT CALLOUTS.vwx

[landscape area section?]

@Zsombor@Anders Blomberg

Good news,

You can enter conditional statements into data tags. The element you were concerned about was values being shown when they were zero.

See Screenshot below

Note there are only 7 layers attached.

 

Component Description - From outside to inside :

#WS_IFNA((OBJECTDATA('component', 'thickness', 1)), ' ')# #fi_3_2# #WS_IF(VALUE(OBJECTDATA('component', 'thickness', 1)>0), 'in thick -', ' ')#   #WS_OBJECTDATA('component', 'name', 1)#
#WS_IFNA((OBJECTDATA('component', 'thickness', 2)), ' ')# #WS_IF(VALUE(OBJECTDATA('component', 'thickness', 2)>0), 'in thick -', ' ')#   #WS_OBJECTDATA('component', 'name', 2)#
#WS_IFNA((OBJECTDATA('component', 'thickness', 3)), ' ')# #WS_IF(VALUE(OBJECTDATA('component', 'thickness', 3)>0), 'in thick -', ' ')#   #WS_OBJECTDATA('component', 'name', 3)#
#WS_IFNA((OBJECTDATA('component', 'thickness', 4)), ' ')# #WS_IF(VALUE(OBJECTDATA('component', 'thickness', 4)>0), 'in thick -', ' ')#   #WS_OBJECTDATA('component', 'name', 4)#
#WS_IFNA((OBJECTDATA('component', 'thickness', 5)), ' ')# #WS_IF(VALUE(OBJECTDATA('component', 'thickness', 5)>0), 'in thick -', ' ')#   #WS_OBJECTDATA('component', 'name', 5)#
#WS_IFNA((OBJECTDATA('component', 'thickness', 6)), ' ')# #WS_IF(VALUE(OBJECTDATA('component', 'thickness', 6)>0), 'in thick -', ' ')#   #WS_OBJECTDATA('component', 'name', 6)#
#WS_IFNA((OBJECTDATA('component', 'thickness', 7)), ' ')# #WS_IF(VALUE(OBJECTDATA('component', 'thickness', 7)>0), 'in thick -', ' ')#   #WS_OBJECTDATA('component', 'name', 7)#
#WS_IFNA((OBJECTDATA('component', 'thickness', 8)), ' ')# #WS_IF(VALUE(OBJECTDATA('component', 'thickness', 8)>0), 'in thick -', ' ')#   #WS_OBJECTDATA('component', 'name', 8)#
#WS_IFNA((OBJECTDATA('component', 'thickness', 9)), ' ')# #WS_IF(VALUE(OBJECTDATA('component', 'thickness', 9)>0), 'in thick -', ' ')#   #WS_OBJECTDATA('component', 'name', 9)#
#WS_IFNA((OBJECTDATA('component', 'thickness', 10)), ' ')# #WS_IF(VALUE(OBJECTDATA('component', 'thickness', 10)>0), 'in thick -', ' ')#   #WS_OBJECTDATA('component', 'name', 10)#

 

I'm still working on a tidier method however. Since there are conditional statements, its possible to make this a much more elegant solution!

 

@Nikolay Zhelyazkov

 

I was wondering regarding the information above -

 

1. Is there a function to call out component index ? i.e. 1, 2, 3, 4, etc...

 

I have looked through all the variables in the insert function context menu in the worksheets, but have not found anything.

 

2. Is there a way to display the dimensional information of values to fractional inches or feet rather than decimal inches / feet in the datatag layout

I tried to use  #fi_3_2#, but it doesn't work. Is there something that I'm missing?

 

Thank you in advance!

[Wall/Roof/Slab Component Centerline (for line types)]

With the addition of various materials and components, it would be nice to provide various hatches for insulation, (i.e. Rigid, friable, mineral wool etc... between centerline spacing) or various other configurations. I have attempted this with hatches and tiles. see below :

 

When using linear configurations, the tile can reverse positions in plan like shown above. Tiles also have an inability to be exported as hatches to autocad. Something to note!

 

When it comes to hatches -

 

A good example of hatches do not tile appropriately because they do not have a starting point. Therefore if the wall moves, the hatch tiles differently (in both world view as well as page view). The good news it can export to dwg.

 

Last experiment included using offset custom line types along component lines (left of right). However this has a major flaw - line types are reversed when using different section wall views such as this.

Here is an example.

 

 

The two section viewports are referencing the same wall type. However because the line type alignment is on one side, the line type reverses (as seen on the left) when the viewport switches direction.

 

As such, the request is to have the opportunity to provide a linetype for the Core or Centerline of the component to have a more variable ability to create wall styles\roof styles\slab styles\hardscape styles with linetypes that can be exported to autocad properly as well as beautiful looking wall styles. See example below

 

 

Given that vectorworks outputs the most beautiful construction drawings of any software I have used in the past, I would say this would make a nice addition with your approval!

[Is it possible to use Data Tags to tag objects inside symbols?]

I second the request. I would call this something like nested records

[linking records using marionnette]

Has anyone ever linked records using Marionnette tool? The reason I'm asking is - say you have an inhouse record management system and you want to synchronize it with IFC records? or say you imported revit symbols with their own record system, and want to update that with your record management and ifc. Has anyone encountered this problem before?

[Linking Custom Database to Parametric objects]

Has anyone had any experience using the data manager and parametric objects like windows and doors?

 

The reason for the question is to link external databases that have information on doors and windows to parametric objects without having to create styles individually. Going to manufacturer to manufacturer and custom make parametric objects is unfortunately very tedious, and wanted to speed up the process. Like for example Marvin and Pella windows - vectorworks created a great catalog however some information and sizing is outdated (particularly product names) which makes me feel a bit wary of using them, therefore i end up creating my own when i have the time. However there are also some other companies like anderson, and even European windows like zola etc... that would still need some kind of integration on the users behalf. VW obviously doesn't have the resources to produce something like that, and I don't expect them to since the features they're working on i believe should be the priority.

 

With my recent discovery that ODBC can be referenced remotely, I have a renewed desire to link database libraries to parametric objects. How would one go about doing this?

 

Has anyone experienced this? Any thoughts?

[VW 2021 Materials]

On 2/25/2021 at 5:40 PM, Ben Beaumont said:

We have constructed localised libraries of 100's, (pushing 1000's) of Materials. @Julian Carr has written a script to create Materials from Textures which helped enormously. There is also a Worksheet that can push other material values into Material Styles. This is a boon for building libraries with repetitive information. We have updated our Wall and Slab styles such that the external and internal components (only) use Materials. Typically the external face is textured with an associated surface hatch (eg; painted weatherboard) so the component has a discernable thickness. The weatherboard Material library has any given profile in multiple popular colours. There are around 5 common weatherboard profiles and 100+ popular exterior colours. I don't think we can reasonably use Classes to manage the attributes of 500+ weatherboard options alone.
We have constructed an 'Applied Finishes' Materials library with about 150 popular and fashionable paint colours from a leading paint supplier. The Wall styles have a 0.1mm internal Component for the 'Applied finish'. The slab styles (for ceilings) have the same. The Wall Styles in our libraries have 'Natural White' associated with them, the ceilings have 'Ceiling White' associated with them.

The Attributes of the other Wall and Slab components are still 'by Class'. We have a short list of (legacy?) Component Classes to control these attributes.  
It is a pleasure to use the Wall and Slab Styles straight from the library and to be able to simply swap out the Material with a preferred option (also straight from the library).
I hear the comments about the absence of Class override type control for Materials, but for me the flatter workflow of simply applying a Material to an object is a far lesser evil than trying to do it with Classes. Considering the ease with which a model can be 'painted' in some other platforms, Materials are a welcome development.

@Ben Beaumont

 

Are these scripts available? I have been searching for something like that for the longest.

 

1. Script to create Materials from Textures

2. Script to write info into the material settings

[ODBC Drivers / Purpose]

@elepp

 

I agree . Great potential.

I'll start another post later, but combing this with a web gui remotely will sky rocket it's potential.

 

May I ask, what do you use it for in particular ? Sorry about that, too early in the morning, didn't see you mention you used it for windows.

 

Do window sizes auto update upon selection of the record?

 

And can you lookup database tables to cross reference records in a worksheet? ( it's a topic I will start a new post on soon )

[ODBC Drivers / Purpose]

UPDATE 3

 

When you start stacking up with the ODBC datasources, you still need to delete the ones that do not work.

 

 

Go into administrative tools and ODBC Data sources and remove any data sources you do not need.

 

Also, if you want to set up new datasources flexibly without VECTORWORKS, this is the way to do it! In vectorworks you cannot modify existing ODBC databases. Here you can.

 

 

 

[ODBC Drivers / Purpose]

UPDATE 2

@ThomasW

@unearthed

@jeff prince

 

 

ODBC Works with MYSQL!!!!

 

There is a pretty convoluted way of getting it to work, however it all deals with the drivers.

 

PROCEDURE:

 

1. INSTALL UPDATED DRIVERS FOR MYSQL ODBC CONNECTION. This is important for successful connection. See link below.

https://dev.mysql.com/downloads/connector/odbc/

 

Both x86 and x64 drivers should work in the connection as I was able to set up an database connection using an ANSI ODBC Driver as well as the UNI ODBC Driver for MYSQL. (albeit with A LOT of trail and error)

 

2. Set up MYSQL server via localhost or docker. In my case I am running MYSQL over docker with PHPMYADMIN as the database connector. Additionally, I am using NOCODB as an airtable alternative in order to modify records remotely (i.e. via website). Additionally I am using Portainer to manage all of my containers.

As of this note: I am currently not using a remote WAN capability for mysql server, however it is possible to do with a reverse proxy. With enough votes, i can set up a tutorial on how to do that if there are enough people interested.

See screenshots below

 

 

Since I have used custom portforwarding - my container port is 3306, but the facing WAN port in this case is 4040. (This is going into the real of IT, but i recommend having a bit of knowledge on that front in order to do this. Otherwise use a locally hosted version of MYSQL server.

 

3. After you have recorded the information for connection, next thing to do is to connect to the database using a GUI or a hosted system. In my case I am using noco db

https://hub.docker.com/r/nocodb/nocodb

https://www.nocodb.com/

 

Setting up nocodb is pretty easy. But in this case, using PHPmyAdmin would actually be better because you have control over database names, and table names. I recommend using a compose file with mysql, phpmyadmin as a resource in order to access everthing. Ill provide the docker file/compose code soon.

 

4.

 

5.

 

 

7.

 

8.

 

9.

 

10.

 

 

 

11

 

12.

 

13.

 

Press the Test button for additional confirmation. If connection is successful, it should work.

 

14.  Press OK to create the connection. Here is the tricky part - after creating EXIT OUT database connections. It needs to repopulate the DATABASE SOURCES above the connection string.

 

 

14. Go back into connections

 

15.

 

The database should appear in this list.

 

16. REenter your credentials for the SQL server

 

 

UPON CONNECTION - YOU should see the database rows

 

 

Go back into record format connection to link the database to the internal records

 

 

 

 

DB should populate

 

 

Connect the record fields the the database record fields

 

 

 

 

 

 

 

 

 

It should auto populate your selection after you update vectorworks connections

 

 

For faster synchronisation

1. Create a shortcut key for vectorworks connection update

2. see below

and

 

Hope this helps!!

 

 

 

 

 

[ODBC Drivers / Purpose]

great news everyone, ODBC works for mssql . however I am missing something. I am still getting an error after setting up a connection after successful test via ODBC.

 

I used MS SQL server 2019. Am i to use an earlier version?

 

 I was able to set up a table inside the container and was able to connect via test connection when setting up ODBC parameters.

 

 

 

 

after setting up the connection - i get this error

 

 

 

Note - I have confirmed the sql tables work via noco database, so the problem lies with either the driver, sql version number, or something else. (see screenshot below)

 

connection currently works, i just don't know why it rejects the connection after successful test.

 

[ODBC Drivers / Purpose]

@jeff prince@unearthed

I'll do some experiments, stay tuned!

 

But here is the summary of what I've discovered so far (on a local level)

When using an sqlite file, I modify the sqlite file in an open source sqlite file editor - something like

https://sqlitestudio.pl/

 

I add tables to it specifically to what I need (I.E. product database with insulation characteristics, or pricing tables, or zoning / building code reference database and I link the database to record information in VW in read only mode.

 

When i assign that record to an object - it does not update immediately, i have to use the update vectorworks database in order for it to choose. The table above was an experiment of sqlite database reference - and in large databases, a search query or search by record would be fundamental to using ODBC.

 

The part that is annoying is that I can change a record in the sqlite file upon entering the information, but I cannot update the object upon selecting the record, which is a bit frustrating.

 

 

I'll try using ODBC with mysql hosted on a local docker vm and update my progress soon.

 

[ODBC Drivers / Purpose]

Also, Would adding a search function for large databases be possible?

 

 

[ODBC Drivers / Purpose]

Can someone please explain this to me? We can host SQL servers to carry database information???? 😁

 

Does that mean I can host an MYSQL Server on docker and use it for referencing and crossreferencing databases?