shorter
-
Posts
3,107 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by shorter
-
-
You have to buy Revit, export IFC, imprt IFC, check Revit file and then issue. We offer this service if you are interested.
-
We have been victims again of a 'bug' caused by indescriminate importing of DWG data.
Somewhere along the line someone probably imported a DWG containing a drawing we issued a few weeks earlier, i.e. a consultant did what we ask them not to do and send our data back to us in their DWG. Never understand this particularly when it is quite categoric in all BEPs I have ever read, and in all our CAD data exhcange protocols, that you simply do not issue data you did not author.
Anyway, the hidden record format 'Title Sheet Border Data' or somesuch, remained in a file that was referenced to a number of files containing title block borders and has corrupted the title block, removing data because the rogue record format was out of date. It is a common issue with resources. They tend to conflict if you don't manage them properly.
Ordinarily, we know how to fix this but in this case the issue was peculiar.
Ordinarily, we can edit the resource and ensure it is up to date. However, in this case we couldn't. The Title Block Border record format is invisible, and only edited via the Title Block itself. It kept telling us it was referenced even after we had removed all references and purged, insessantly, and there were no title blocks left in the file.
Anyway, after a couple of hours or detective work, we found the errant files and rebuilding them freed ourselves of the scourge and we we able to stabilise the sheets.
While the invisible record is a pain, and we were able to fix it, the issue I have is not that it's invisible or that we spent two hours of our lives that we are not going to get back caused by the original malfeasance by the autocad user, my grievance is with the way Vectorworks will think something is referenced when it isn't.
If I create a file A, and reference it to file B, I would expect any resource placed in file A to become a referenced resource in file B. However, in some cases, a resource in file A, that is 'inactive' or 'not in play', i.e. not placed in file A, becomes a referenced resource in another file. Why and under what circumstance would you ever want that to happen? If I reference a resource I do so deliberately and with aforethought. I do not want resources referenced 'by proxy'.
-
1
-
-
Out of the box, the template and default content provided by Vectorworks expects certain conditions in the model. They are trying to be helpful by giving you content that to some extent 'works' out of the box.
However, very few projects are 'out of the box' so you are recommended to develop your own content to suit how you delivery your architecture and stop letting software dictate how you design, which it so often does.
The discussions surround layer elevation and wall height versus storeys will surface again I fear, but I will say this. Sometimes you use storeys, sometimes you don't. There are no rules nor industry standards governing how you use software; only protocols to define how you name things.
Some will erroneously state you need storeys to deliver IFC.
Some will say you have to bind layers to storey levels.
These are all 'out of the box' mandates that should be ignored.
-
1
-
-
As I sit here, again, analysing a model prior to issue I wonder why we can't have a model tree interface, perhaps a unique workspace, that gives you an insight in the model by floor and object like Solibri and other clash detection tools.
-
1
-
-
Might I suggest organising the file and using layers for each plan/section/elevation/detail rather than one layer? You will find it far easier to edit the information in the design layer
-
Apologies… I come from a position of having to manage and correct this sort of thing so it hits a nerve! 🙂
-
1
-
-
I’d like to see the client’s face when that comes back from the supplier!
#badpractice
-
Is that not scaling the legs too ?
duplicate the symbol and create another table that’s the right size.
-
Design Layer scale 1:1?
-
In Vectorworks is listed
Classification Name
Classification Source
Classification Edition
Classification Edition Date
Item Reference
Name
Location
What is 'Name' intended to be used for?
Classification Name = Uniclass2015
Classification Source = n/a
Classification Edition = v1.29
Classification Edition Date = January 2023
Item Reference = Ss_25_10_30
Name = ?
Location = https://uniclass.thenbs.com/
Is Name related to the Clause Heading, e.g. Framed partition systems?
'Name' is not listed on the BuildingSmart definition of IfcClassification which is why we are asking.
Thanks.
-
1
-
-
On 3/4/2023 at 4:11 PM, jeff prince said:
You are creating more questions than answers 😉
@AndrewBeres there are a bunch of write ups here in the forum covering various methods of doing what you hope to accomplish. I’m biased towards my method obviously. Not only do you have to consider the file management approach, but also Stories vs Design Layers, layer/story bound vs discretely defined features, and a whole host of other complications.Touché!
-
It all depends on how you structure a file too.
the solution in a single file is different to a multiple file approach.
What you need to see on the drawing also influences the way you set things up.
If you are also prepared to step outside the ‘expected’ approach you will find some processes are actually quicker if you do not let the software or bim dogma dictate process or practice.
-
4 hours ago, Christiaan said:
That's how I feel about updating WGRing. And WGR is like a box of chocolates. You never know what you're gonna get.
sort of but you got to know how to always get the purple one. -
8 hours ago, jeff prince said:
and tore the vellum or gouged the mylar as it skid across the media without ink...
Halcyon days!
-
1 hour ago, jeff prince said:
Reminds me of the old pen plotter days 🙂
Print a sheet of details... enjoy a 2 martini lunch.
And come back to find the pen ran out of ink…
-
2
-
-
Sadly it’s even more complicated than this…
-
By the way, we are seeing similar setups in Revit in order to speed up the synching process but also keep file sizes down to project BEP limits.
I watched a practice using PS the other day and a small model, perhaps 50mb saved in Dropbox.
the time lost waiting for the files to save and commit and then refresh must add up.
we have heard of models taking so long to open even that everyone working on the model comes in early, open the model go and have breakfast and come back to the office to work.
how can that be efficient?
they are wasting hours.
all in the name of BIM
i would rename your post ‘still have all your eggs in one basket?’
😉
-
That is what is known as a bug, @Christiaan 😉
-
I should also add ‘it’s also a state of mind’ thing
-
1
-
-
Current projects include a 400,000 sqft model segregated into multiple models assembled into one to print and to export.
an eight building project with 6-8 floors shared with three other architects all on vectorworks split by building and architect.
large hotel project with a team of 5-6 architects similarly segregated.
just about to embark on another 8 building project…
these are all 3D. Projects were even bigger and more complex in 2D. No problem with wgr.
personally I think there is a limit to PS, not because of the software or the technology but due to the inability of people to keep their files clean and disciplined. There is therefore more mess in one file and that has to be a problem ultimately and back in the day we spent most of our time unpicking the various layers of user idiosyncrasies to even print the latest drawing from those ‘single files’. I would hate to go back there.
that fact that we don’t generally have problems with referencing is due to the way we set things up and manage things. There are rules and it willbreak if you don’t follow those rules so we make sure the rules are followed.
it is though a matter of preference. PS works for you. Great. WGR works for us.
it gives us a simple logical system that makes it easy to manage all aspects of the delivery of drawing, schedule and model.
-
1
-
-
🙂 which ever way you do it, @Christiaan you will never be satisfied.
-
1
-
2
-
-
5 hours ago, Christiaan said:
Hi Michael, welcome to Vectorworks and the forum.
Yeah that's a tough one. If it was just the lintels I'd tell you to model them and insert them into the wall as a symbol.
But continuous banding like that, up to the corners of walls, is not something VW easily handles as part of the solid model.
One way to approach it would be a similar workflow to Sketchup. You'd draw polygons onto the face of the walls, extrude them by 0.5 mm and then apply a texture to them. If you subsequently edit/move the walls you will need to manually update these objects separately.
This is often how we see them modelled in other BIM software, i.e. as appliqué. Same with rustication.
-
The Vectorworks appendix to the last issue of the AEC UK CAD Standards for layer naming under Uniclass 2015 - and where the AEC UK CAD Standard class libraries I supplied to Vectorworks in 2016 come from - used the hyphen to separate the field in the class name, rathger than the underscore in the Uniclass coding. I explained why I chose to do this at the time, but now we finally (!) have filters, the hyphen is no longer so useful, or rather filtering can accomodate the use of the underscore or hyphen, and why I refuse to use the ISO13567 variant...
The structure of an AEC class is
A-B-C-D-E
where -E is an optional 'presentation' field, e.g. 'CUT, FWD, HID, RFL
So a typical Wall class is
A-EF-25-10-M-Wall in AEC parlance
A being the author code
B being the uniclass code
C being the object type
D being the description
but could also be
A-EF-25-10-M-Wall-CUT ie. Thick
A-EF-25-10-M-Wall-FWD i.e. Thin
A-EF-25-10-M-Wall-HID i.e. Thin Dotted
A-EF-25-10-M-Wall-RFL i.e. Thin Dashed
This sometimes gets bastardised as
A-EF-25-10-MC-Wall
A-EF-25-10-MF-Wall
A-EF-25-10-MH-Wall
A-EF-25-10-MR-Wall
rather than adding the -E suffix.
Level of Detail or Drawing Scale is taken from the tables themselves
EF > Ss > Pr
ie. You use EF classes for planning, Ss for GAs, and Pr for details.
Of course, you all know this already but in order to remove any doubt... 😉
-
1
-
-
Yes they do, and so do we, or rather ours are split by line type, pen thickness, and level of detail.
Rogue Record Format
in Architecture
Posted
Unlikely...!
The only objects left in the source file were symbols. Of course, it would not be beyond the realms of possibility for the invisible record format to jump on to a symbol, but there were definitely no title block borders in the file, to the extent that once we had copied the data from the file into a fresh file, by referencing and binding, the record format magically disappeared.
Yes. I would not be able to replicate it on demand.