Samuel Derenboim

  • Content count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About Samuel Derenboim

  • Rank

Personal Information

  • Occupation
  1. While i agree with the idea that it should be implemented with the viewport, my best guess is integrating existing tools is the quickest method to get what you need. I'm afraid an overhaul of the system would be required if they did it the way you wanted, and that means more time for development. we want to try to get the best features with the least time of development.
  2. Does VW preload any files other than its native format when checking? when creating a library I have multiple files in the directories other than vector works for reference ( code related info) is that cached during startup I’d say I have a shared library? And if so, can it be ignored? i knew it was the caching, I just thought it had too many files in there.
  3. + 1 for me! I can’t work in multiple files for this reason at this time. At least multiple large files ( I noticed it did this when I had one large file open, and one small one) so thought it could be a caching or memory usage bug.
  4. Oh, you mean something like dynamic elevation markers. Now I understand. i agree, currently there isn’t something like that you can do in an annotation viewport. Having a dynamic benchmark tied to levels/stories would be very useful. In fact if the can be interchangeable - I.e. change level / move the benchmark or change the benchmark move the level could solve a lot of problems. all that would have to be done is to have an option in the benchmark oip to tie it to a story / level (for display, not change) and another to tie that particular benchmark to that particular story/ level that if you move it vertically, it will change. - or when creating a section viewport they would already be integrated into that drawing. I just see pros and cons with both versions. Developing an idea for programmers to work around could prove to be challenging.
  5. Odd, I've never had a problem, neither in 3d nor in 2d. I just double checked right now. Are you using the latest version?
  6. Matt, in order for it to work, you have to use BIM. When you reference a live section in a BIM model, those elevation benchmarks will reflect the elevation. Also, if you are doing a 2 dimensional drawing, you can use 2 methods. 1st is use Y value relative to reference elevation. This means that the ground plan (0) elevation must be where y value is zero. In case you need to find it, notice on the benchmark elevation there is an x and y mark location (that is its location in the grid). Now change the number in the Y column to zero and youll notice that the benchmark automatically shows 0'-0" as its elevation. 2nd is to use a control point. So you change the location of the benchmark, but modify the control point to the ground plane in order for it to measure the distance from it. Both methods work, but the 1st one and BIM versions are automated.
  7. Hi Andy, Thank you for the tip. I'm aware of this trick, but there are four main reasons this is a little bit of a cumbersome workaround 1. Cannot see the size of the text change while you're designing in design layer viewport. It would be important to understand the scale difference while youre designing that way you konw that it will be in the right locations and fits inside the rooms properly. 2. As text size changes from the Viewport scale, it tends to move. When it moves it can obstruct important elements in the drawing, and consequently you still have to go back to the design layer to change the location. 3. It doesn't export properly into Autocad. Meaning - any modifications you did to the plans will most likely not reflect in any other program. An embedded function inside the text style would and could take care of that. 4. It generally slows down workflow because you constantly need to check if this option is turned on. Its very prone to user error because a user can forget to go into the viewport options. Additionally, with the trick above - you can implement it one of two ways (using the chart). Either you set the class to have the custom size of the annotative scale that you need and use that class for annotation on that particular layer. That would mean creating one additional class and one additional text style at the appropriate size, and distinguising which classes needed to be used on which design layer viewport. (this eliminates flexibility) The second method is to provide the appropriate text styles representing each of the conditions as shown in the chart above. so that would mean if you use 1:1 scale, 1/8, 3/16, and 1/4", 1 1/2" scale for sheet layer viewports and say 1/4" and 1 1/2" for design layer - with 4 varying text sizes for annotation - that would mean you need 12 different text styles representing each condition. Unfortunately very laborious. That and, difficult to change font and variability globally as well. Note - this is similar to annotative elements in autocad, but i personally think it would be easier to implement if you just simply check an option to show viewport lettering size of the appropriate scale inside the text style as a drop down - you simply select the scale this drawing will be displayed in via sheet layer viewport scale.
  8. When you use BIM, as far as i know, I've always used the elevation benchmark tool. It's dynamic, it sets the elevation automatically once you're in the sheet layer viewport annotation area. (when you double click a viewport in sheet layers - pick the annotation option) it will give you the opportunity to call out any elements of the elevations / section in real time. Hope this helps.
  9. Also, in case anyone wants to use these as a reference, i'm adding a dynamic excel template for you guys to play around with text size. Let me know what you think. Text Size Reference.xlsx
  10. Good evening everyone, Wanted to list a new request for future versions because i've been having a problem for a bit of time now. I've been standardizing my firms sheet standards, symbol standards, and template standards for drawing types. One thing that i have ran into while drawing in vectorworks is the problems with text scale and consistency of text size. To give a bit of background - we know that we have two different types of scales that we all draft in - design layers and post the information in sheet layers. Both however, are governed by scales. Design layers have a scale for line types, etc... and sheet layers reference design layers in the viewports. One thing that I love that Vectorworks did was the text style tool that standardized all text used in a file. Meaning, if you said that a text style for a particular drawing is to be size 12, you can use that text style consistently. However, the team didn't take into account one minor detail - Let's say your design layer scale is at 1/4" = 1'-0" and are using a viewport in a sheet layer viewport scale at 1/4" = 1'-0" with a text size of 12. The way VW is programmed - the nice thing about it is the size of the text stays consistent - it appears in sheet layer at 12 as it would for 1:1 scale. However, the complexity increases when the variables change. Let's say you have the same design layer scale at 1/4"=1'-0" but have a sheet layer viewport scale at 1/2"=1'-0" - what happens? the same size 12 text appears as size text 24 - because the viewport is showing the text 2 times the size of the design layer viewport. Now for the request - since we like to allocate different sizes on the sheet layer scale - is it possible for the text style scale to have an option to appear the size of 12 in the Viewport scale and scale the size of the text in the different design layer viewports accordingly? In the end - we inherently want all of our text to appear consistent throughout all of our drawings and the way we see from our eyes is at 1:1. So all we have to do is pick 5 or 6 different sized text sizes rather than dozens (if not hundreds) if we increase the variability of our text sizes in sheet layer viewport scale vs design layer scale. Heres a chart below for some more information regarding the ratios.
  11. HOLY (*&#)$(*&#($*&#$ !!!!!!!!!!!! Gerard, you are THE MAN! This works like a charm!!! Just curious, did you learn to code in Vectorworks? or did you know python prior to??? How hard is it to learn? Either way, Gerard, This script is excellent. Don't know how to thank you enough. Gerard, Thanks with this tool, I would be able to create an ample resource for libraries for light fixtures, FF&E, proprietary specifications, and even custom callouts for details (if i can get the callout tool to work for symbol definitions). Do you work for Nemetschek / VW? I can share some of the libraries with you later if you like. Integrating this into project management saves a substantial amount of time on the production of CD's !
  12. Gerard, that process is for a symbol instance. That’s the easy part. Now try importing the same symbol from the resource manager into another file, you’ll see the record information is empty in the symbol, and even if you apply it, the record fields need to be re entered. In in order to avoid that, you need to write what’s in the symbol instance (An example of what you’ve shown) to the symbol definition (resource manager). That way if you make a shared library in the resource manager you can drag and drop with the desired resource information without constantly having to refill it. Currently the only method of doing that is by right clicking every symbol definition and modifying its record information from the resource manager, which is very cumbersome, and wanted to ask vw or someone to help me make a script to write the information from symbol instances to their respective symbol definitions. any help from vw?? 🤓😇
  13. Really? you have a script that can write instance record information to symbol definitions? You already have a ready script? or are you saying it's just possible ? I just wanted to add this request to the wish list since i too don't think this is an impossible feature.
  14. It doesn't work exactly the way you mean. Yes, you can write record information to a symbol from a worksheet. The problem is - it will not write it to the symbol definition for use with different files or integration into the resource manager.
  15. Hi, Many a time where you happened to want to create a library but found it too cumbersome because the record information must be written directly in the resource manager rather than a spreadsheet? Is it possible to write existing record information inside of a symbol to the symbol definition please? This would tremendously expedite symbol and library creation.