Boh
-
Posts
1,706 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Boh
-
-
Hey @JB_Tech3
I had a look at your file. This is interesting. It seems that when you decompose the polylines defining one of the extrudes in the 3d component of the "AC Outlet Horizontal", then some of the lines pop up in the Building-Doors-***Stage Access class.
However changing these lines to the none class and recomposing the polylines still doesn't allow the Building-Doors-***Stage Access class to be purged from the file. It somehow seems to be stuck to the symbol. No other decomposed geometry in the symbol showed up the Stage Access class.
To get rid of the class I had to rebuild the symbol - essentially copying and pasting all the 2d, 3d and wall component geometry into a new symbol definition. Attached is your file with the rebuilt symbol - now called "AC Outlet Horizontal - New". This file doesn't have the Stage access class in it. Phew!
So if you import the "New" symbol into your file then delete the old one, replacing all instances of the old with the new as you go, then you should be able to delete the Stage Access class. That's assuming there are no other symbols in your file displaying similar behaviour. Good luck!
-
2
-
-
@Asemblance Ah yes those check boxes don’t work on referenced dlvps. I guess this is because a ref dlvp could have an entirely different class structure.
To use ref dlvps with different visibilities you need to create a duplicate dlvp for each scenario.
To keep my files clean and manageable I put teach dlvp on its own dedicated design layer.
If there are going to be more than 2 or 3 duplicates I would consider changing to layer referencing or even just importing the geometry into the file.
@C. Andrew Dunning I haven’t seen this before. Can you post a file?
-
1
-
-
@Asemblance If you click on “classes” in the oip when a sheet layer vp is selected you’ll see near the bottom of the dialogue are a couple of checkboxes. They are options to use the class overrides and/or visibilities of nested design layer viewports. Does this not do what you want?
@C. Andrew Dunning I think when you click on edit for a sheet layer vp there is an option to use seperate class visibilties for the vp or just use the current file class visibility settings.
-
1
-
-
57 minutes ago, LarryO said:
The list was not populated with anything when I opened it, but I think I may have observed from your photo why that was so.
Yes the list will be unpopoulated by default with "None" in the "Back references" drop down. You need to select an option other than none.
29 minutes ago, michaelk said:@Boh I think you have an old version of that script. I'll have to see if I can find a newer one. (I'm pretty casual when it comes to script version control. I often don't have the most current version of my own scripts in my menu commands. 🙂 )
You can safely use that script on any sheet layer viewport except Section Viewports. It will semi break the link back to the section line. @Matt Panzer was kind enough to submit it as a VW bug, rather than a me bug. I still use it on Section Viewports and just deal with the consequences, if any.
That would be great Michael. I thought I had updated it a while back when we were posting about this on another string. Maybe that's why it's not working on detail viewports!
Cheers
-
5 minutes ago, LarryO said:
Now if I want to change that drawing number assigned to the viewport, I select the viewport and in the object info palette change the drawing number to 5 or C or whatever, then the prefix of the viewport's name will also change once you allow the OI palette to refresh but only under one condition. The suffix of the name must still match the sheet name.
Ok, I didn't know the default vp name could update like this. Not sure how useful it is if only the drawing number that updates and only if the sheet number hasn't changed. For software that boasts of 3d bim and auto coorodination etc this is a real failing. Viewport naming is essential for 3d work esp on larger projects and haveing to do it manually is just not really good enough.
I recommend using the script posted earlier. It may also work on section viewports but doesn't work on detail viewports.
-
1
-
-
I had a quick look at your file.
On 5/26/2021 at 9:51 AM, LarryO said:I have just realized that viewports do not automatically update their name when the sheet number is changed.
As mentioned, vp's don't auto update to changes in sheet number or drawing tile or vica versa. If you meant the Drawing Label doesn't update then I don''t seen this behavior in your file. The sheet number in the drawing label doesn't seem to change but as soon as you zoom or pan the label updates.
On 5/26/2021 at 9:51 AM, LarryO said:When I change the drawing title of the viewport in the object info window the Drawing label doesn't refresh to show the new name.
I don't understand this.
Your Drawing Label "Accord Primary" doesn't call up the drawing title.
Your Labels "Accord w back ref" & "Accord Secondary " updates ok when the vp is selected and the drawing title or number are
changed in the OIP. Are you seeing different? See attached screen recording.
On 5/26/2021 at 9:51 AM, LarryO said:When I manually change the sheet number in the viewport name field (because viewports don't seem to be updated when a sheet number is changed in the sheet layers dialog) that change is also not transferred to the new Drawing label.
Yes, vp names and drawing labels are not linked.
10 hours ago, LarryO said:the drawing number only updates when the sheet number is already correct, but it occurs after deselection of the viewport.
Can you explain this more?
From your PM: "When you go to page 03 having section A-A on it your will notice that the anticipated back reference to page HB01 has not filled in either."
You need to select which markers you want as back references. Select the vp and click on "Select back references". Best to choose "select objects from list" then put a check mark next to the marker/s you want to back ref..
If you want to keep your vp names to match the sheet number, drawing number & drawing title then @michaelk has developed a really good script which will name selected viewports. Posted below. Be aware that with v2021 it's probably best to just use this on top/plan viewports. You can see how it works in the screen recording. I use it so much I have put it as a menu command.
Procedure ViewportRename; {Badly Scripted by Michael Klaers. Updated Aug 2, 2015} {This script will take all selected viewports and change the name of those viewports to be (Sheet Layer) (Drawing Number) (Drawing Name) This version tries to force the name to appear immeidately in the name field, data tab, OIP when only one VP is selected. Prior to this version the new name appeared immediately in the Nav Palette, but not in the name field.} Var VPDwgTitle,VPName,BText,VPNum : String; h,hh: Handle; ViewportLayer: Handle; ViewportLayerString: String; Procedure RenameVP(h : HANDLE); Begin {*********** BEGIN Procedure ***********} ViewportLayer:= GetLayer(h); ViewportLayerString:= GetLName(ViewportLayer); VPDwgTitle := GetObjectVariableString(h, 1032); VPNum := GetObjectVariableString(h, 1033); ResetObject(h); { Message('Viewport Handle: ',h,chr(13), 'Layer Handle: ',ViewportLayer,chr(13), 'Layer Name: ',ViewportLayerString,chr(13), 'VP Num: ',VPNum,chr(13), 'VP Name: ',VPDwgTitle); } SetName(h, Date(2,2)); SetName(h, CONCAT(ViewportLayerString,' ',VPNum,' ',VPDwgTitle)); SetDSelect(h); {These two commands are just here to force the new name to appear in the } SetSelect(h); {name field immediately. They can be deleted w/o consequence} End; {*********** END Procedure ***********} Begin {*********** Main Program ***********} ForEachObject(RenameVP,(((T=VIEWPORT) & (SEL=TRUE)))); End; Run(ViewportRename); -
If @michaelkis right (which he usually is) then perhaps try a purge on a copy of the file to see if deleting unused symbols will also get rid of the unwanted classes.
The purge command gives you a preview of all the unused symbol definitions so that might narrow things down a bit.
-
1
-
-
There must be some symbol definition or plugin or something that uses the unwanted class.
Vectorworkaround: add a “zz-“ prefix to the class name. They will drop to the bottom of your class lists. Out of sight, out of mind!
-
Seems odd. Can you post the file to the forum? Happy to have a look.
-
3 hours ago, LarryO said:
When I change the drawing title of the viewport in the object info window the Drawing label doesn't refresh to show the new name.
Make sure you have "use automatic drawing configuration" checked in the File>Document Preferences>Display dialogue.
Just to clarify, "drawing title" and "viewport name" are two entirely separate things. The drawing label should update automatically to show the drawing title. The drawing label is not connected to the Viewport name which is at the bottom of the OIP window and, unless you use a script is only edited manually.
Nothing is new with this. This functionality is just the same as with the previous drawing label.
-
1
-
-
Well done Michael. Spot on. I just discovered that before you posted. I had a few erroneous objects way off the origin. Deleted them and now seems to be ok. Thanks! Not sure how they got there. They were literally miles away...
Cheers
-
1
-
-
I'm hoping someone can help with this.
I can't seem to get OpenGL to work. The textures on a file have gone transparent and locus points have turned "full screen".
This is what it should look like (ignore white rectangles):
But this is what I'm getting:
If I fiddle with the OpenGL render options it might work for a bit briefly on some design layers.
Unfortunately I just noticed it and I can't retrieve any backups.
This is a vw2021 project.
Any suggestions appreciated. Thanks.
So far it only seems to be happening on one project
-
There is no equivalent to the autocad "By layer" & "By Block" attribute controls in vectorworks. I understand this is a wish list item dating back for some time. I haven't found a workaround for giving different attributes to the same symbol using classes though you could try data visualisation to do this.
For controlling visibilities of symbol geometry, from experience I generally suggest you avoid putting differently classed geometry within a symbol definition. This means that you may need to have 2 or more classes visible for the symbol to appear correctly. If the symbols are just for your use then you can probably manage it ok but if the symbols are going to be in a library for others to use then unless you have a well understood office class standard then inevitably people are going to get the visibility settings wrong.
I have two ways I typically set up symbols:
1. Put symbol geometry on the none class with attributes controlled by object (rather than by class).
As the none class is almost always set to visible the visibility of the symbol is only controlled by one class - that being the class in which the symbol instance is placed.2. Put symbol geometry on different classes with attributes controlled by class (rather than by object).
I like to use classes a lot to control the attributes of geometry as it allows attributes to be overridden in different viewports and global control of attributes across a file. Sometimes I will also extend this to use different classes within symbol definitions however to avoid the multiple class visibilities issue I will only do this if the symbol instances are typically placed on the none class (i.e. the inverse of the previous suggestion) and the symbol geometry classes used are always set to visible. I tend to use this approach more in viewport annotations, such as in detail drawings, as the symbol instances can just be placed on the none class. This approach works well across a workgroup if there is an established class standard so everybody know what the classes are for and understands how to set their visibilities.
If you are making symbols that others will use and don't have a good class standard understood across the office then best use option 1.
-
Hey Elle.
If the palettes are on top of each other can you not just move them? Unfortunately the file you posed is the student edition so can't open it.
-
For the top/plan viewports, when you go from sheet layer to design layer via a vp, you can get vw to create a green outline of where the crop is on the DL. If you do this for each vp before moving everything it makes it easier to realign your vp crops back to where they were. All your vp annotations will need to be moved vp by vp unfortunately
For section vps, make sure there is a section line for each section vp on a DL. If the a section line is moved with the model then it’s vp should still be showing the same section after the move.
-
2
-
-
There is also Vectoworks University and also Ozcad who have aome good free instruction vids on their range of third party plugins included in the Australasia release such as the WinDoor tool.
-
Nice job! I did an old villa a while back and after 2 site measures couldn’t work out why the upstairs walls didn’t line up with downstairs - some walls were 100mm or so out of alignment. Finally figured out that the original high stud walls weren’t vertical but more recent reno walls were!
-
I only just cottoned on to this feature recenetly and now that I know why and how it works I really like it! It makes drawing polylines (with curves) so much smoother once you get used to it.
-
Not sure if there are any settings in the marker tool that will do this for you. A work around might be to edit the interior elevation marker style so that it fits in the room.
-
Additional snap tips:
You can create some custom tool scripts from the custom tool dialogue. I have one to set snap settings for detailing and another to set them back to my preferred defaults. One click trick!
Also if you hold the ctrl+shift while pressing the arrow key the selected items will nudge to whatever your current snap distance is. This is set in the preferences under nudge settings. Using this you can rapidly nudge stuff around your page set distances without having to type in any measurements.
-
2
-
-
What @zoomersaid.
Another tip is to get in the habit of using the shift key to help constrain line work to vert horiz and snap angles. If you have the floating coordinates set to be visible then with the higher precision tolerance you can see if line work is slightly off the correct angle as you draw.
Also if your work is mostly rectalinear then activating the snap grid set to say 5mm helps to keep everything tight. For detail drawing I set the snap grid to 1mm.
-
1
-
-
Thanks @jeff prince and @markdd.
My approach has to be all carrot!
As we haven’t been using record data and data base worksheets for scheduling in the office much no one has really got much experience on how to set it up. It would be good to get the bones of a basic workflow together which I can then take to my team as a starting point.
Keeping things simple I think is a gd idea. If anyone has any other clues to common pitfalls they have experienced working with records and database worksheets across an office workgroup that would would be amazing.
Thanks
-
Thanks @markdd.
Yes I use the attach record command which I think is going to shortly get a lot more use from me. If you read on in the thread of posts you’ll see I have taken advice from others about not using VW to manage data so while I plan to attach a custom record to symbols I won’t be doing a lot more individual editing of that data for each symbol. I can see now that it is not really worth the time spent.
Yes we already have a fairly comprehensive library placed in a workgroup folder as well as some pretty good project templates. This post was more about how to set up a system for presenting data attached to symbols in a file. Essentially finding the *best* way of combining the use of libraries, symbols, record formats, data tags and worksheets.
I take your point though about keeping templates clean. I take a slightly different approach and tend to include some default resources that I know are used on almost every project. We tend to recreate the templates from scratch each time we do a version upgrade (every other version) so we take that opportunity to clear out out of date stuff.
What is your advice with regard to setting up an office standard for record info/data.
Cheers
-
1
-
-
Thanks @halfcoupler & @jeff prince
Yeah so clear messaging there: simpler is better!!
@jeff prince I appreciate the “lone wolf” comment as I’ve been guilty of that in the past. Yeah I don’t want to spend a lot of time developing an amazing complicated system that only I will end up using. That said getting staff to appreciate the benefits of a smarter way of doing things is no easy task. No matter how significant or obvious the benefits of a different approach are sometimes people just resist change.
We do need to get a more coordinated approach to how we specify this stuff however. So I’m hopeful that, without spending too much time, and with help and advice from experienced users like yourself and @halfcoupler on this forum I can set up the bones of a basic system that will have the essentials in place and be accessible enough for others to appreciate its advantages and how it can work for them. If I can do that I will at least get the “buy-in” of the more progressive staff.
So to simplify things down then this is what I am now thinking:
Just have one main record format attached to almost all library fittings symbol definitions. (This would include plumbing fittings, equipment, furniture and even light fittings).
The record would have just two fields:1. “ID” (with “[ID]” as the record field default) and,
2. “Description” (with a blank as the record field default).
To avoid the data management nightmare, library symbol definitions would generally just be left with the record format defaults. Specific data would be added to the symbol once it’s brought into a project file where it can be tailored to suit the project requirements.
Custom data tags and preformatted database worksheets would be added to the project templates files.
The custom data tags would link to objects with the record format. The tags would just display the symbol’s “ID” field. (Different versions of this tag could be used depending on if the symbol is a plumbing fitting, equipment or furniture etc).
The worksheets would just have the two columns to report on I.e. the ID and description record formats. Worksheets could have criteria so they only call up records present in a sheet layer and/or alternatively, using classes, they could just call up plumbing, electrical or furniture fittings.
How does that sound?
Do you think this is still too complicated and could be simplified further? Please keep the advice rolling in! 🙂
@halfcouplerI really like the idea of managing the data outside of vw. Can I ask if you work in a collaborative office scenario with this system or are you a sole practitioner?
Also do you issue your indexed external spreadsheet with the project drawing set or do import the spreadsheet into vw or copy / paste the info from the external spreadsheet into a worksheet in your vw file?
Also how do you do your indexing? Do you use a script to index your symbols or do you do this manually? Are the index numbers used as identifiers on your drawings sim to my ID field? Or are they used purely for internal management of symbols?
Please if others have advice please chime in!
Thsnks
-
2
-
Wishlist - Viewport visiblity for sheet viewports of reference viewports
in Wishlist - Feature and Content Requests
Posted · Edited by Boh
@C. Andrew Dunning
I haven't found this to be the case when I opened your file. Mind I don't have vw2020 so opened it with v2021.
Have you played with these settings?