Jump to content

Samuel Derenboim

Member
  • Posts

    432
  • Joined

  • Last visited

Reputation

134 Spectacular

1 Follower

Personal Information

  • Occupation
    Architect
  • Location
    United States

Recent Profile Visitors

3,222 profile views
  1. Can someone please verify - hardscapes do not support tiling in cross section? FYI I am using hardscapes in completely unique ways, however, on screenshot 1, the hardscape does not show tiles, but it does show hatches. Could someone confirm please?
  2. VW does sequential sorting, so depending on what you sorted first, it will use that as the primary sorting element. Unsort everything first, and then sort column a first, then column b. I think that should be able to work.
  3. @GatRed Ah i didn't notice your last post. Congrats!
  4. @GatRed Yea, I understand the frustration. Took me a bit of time to do it as well. The good thing is once you get it working, its a breeze after that. When you go into the iODBC driver options, is this what you see? Notice I have to pick a database name/table in order for me to access it. Also, do you have the tabs all the way at the bottom? (if not, click on the details button bottom left hand corner). Hopefully it's just your settings as iodbc connects just fine from the driver Also the error below i think means you didn't pick the database table to connect to. make sure they match names. I have a database table with the name window_catalog in it, and test your connection before closing as well. Maybe its just the table designation that's throwing it off.
  5. what version of mysql is it? can you post the docker / docker compose script? Also, try playing with the settings of the mysql driver. They also have 2 drivers, 1 uni and 1 ansi. maybe the ansi one works better on mac? Also, as an experiment, try recreating another connection via iodbc driver. There are also certain options you can use in the connection, maybe there is something in the settings that is in conflict with VW
  6. it seems mariadb is not supported https://app-help.vectorworks.net/2023/eng/VW2023_Guide/Database/ODBC_driver_information.htm https://mariushosting.com/how-to-install-mysql-on-your-synology-nas/ Just FYI, I started out with a Synology NAS as well, but after a certain point it became too limited for hosting options, which is why I learned to use Docker.
  7. can you show a screenshot of the error? It could possibly be the connection to MariaDB is not compatible with ODBC driver. If you want to use mariadb, try installing this driver. Mariadb was originally forked from Mysql, but i do not think they are the same. That could be another cause. https://mariadb.com/kb/en/mariadb-connector-odbc/
  8. Your dsn appears to be Gramysql not odbc 8.0 there error show that it cannot find the driver name. They have to match. Additionally since you populated it in your iodbx driver, it might not be necessary to enter it into vw. Repopulate available databases in the first table where you load the database. Gramysql should be there.
  9. @GatRed Are you running a mysql server? does it work via phpmyadmin? or similar? Have you created a database table inside the server? did you install the latest odbc driver for mac? Can you show us a screenshot of your DB connector window? FYI https://dev.mysql.com/downloads/connector/odbc/ Use the driver to connect to your database first. If it connects, you will be able to use it in VW. See above posts for referencing db info into VW Also, once you confirm connection via outside source (i.e. self hosted http access), try this connection (it should work the same, system independent) DSN=MYSQL_Uni;UID=sa;PWD=password; DSN : Driver name for mysql after you install it UID : Username (often its root, but if you create a separate user to access the db table, you can use that) PWD=password for username to access database table
  10. I agree, Graphic legend drawings do not export to dwg. Did an experiment on both exporting sheet layer to model layer and regular export with separate sheet layer views.
  11. 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!
  12. 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.
  13. @Nikolay Zhelyazkov Thank you for your help! also - wish list item added!! https://forum.vectorworks.net/index.php?/topic/101918-graphic-legend-feature-request/
  14. 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.
  15. I think it is an almost identical implementation of the new tool. I agree, Graphic legend feature will be a life saver!
×
×
  • Create New...