Jump to content

shorter

Member
  • Posts

    3,096
  • Joined

  • Last visited

Reputation

1,023 Spectacular

4 Followers

Personal Information

  • Occupation
    Architect specialising in Vectorworks Production Management, Sales, Customisation, and Training
  • Homepage
    www.stevenshorter.com www.modelity.co.uk https://www.linkedin.com/in/stevenshorter
  • Location
    United Kingdom

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. We don't use Roof Clipping.
  2. When I say 'it works' i was not referring to referenced DLVP... 😉
  3. To @Christiaan and @Tom W. re: referencing... It works. But you have to know how to use it properly. It only 'creates more problems than it solves' if you fail to adopt the correct protocols and fail to follow those protocols. It is NOT an adhoc workflow, i.e. you need to plan for it's use.
  4. @Christiaan The sheet number simply needs to be the n digits sequential/logical number at the end (e.g. 120100). The rest of the titlesheet should contain the fields required, and in conjunction with dynamic text fields in the titlesheet, and the publish command, generate the full ISO19650 document number by concatenation.
  5. We advise to never print direct, but to 'soft-proof' your PDF prior to issue or printing. A 30Mb PDF that takes an hour to print 'should' be raising alarm bells. 😉
  6. Out of interest, is this bug caused by an update, i.e. upgrading from an earlier version of Sonoma? Can anyone confirm if a clean install of the OS causes a similar issue? Too often users 'auto-update' and this causes the problem, rather than carrying out a clean install or updating with what Apple used to call a 'combo' update.
  7. my feeling is that users 'should' be familiar with the standards they are using and set them themselves and not expect a software vendor to set them for them. this setting should be off by default unless explicitly set by the user.
  8. It all depends on the complexity of the viewport. Tend to find @Pat Stanford's suggestion of convert to lines, etc, fails dismally, and and that strangely it is far more reliable to set up the Section Viewport in modelspace (i.e. place the section viewport on a design layer, and 'display flattened'), and export as a DWG and reimport the DWG.
  9. Only to reduce it further, but not to edit it. Have to select 'Edit Crop' to change it's shape.
  10. why don't you just use the clip tool? one click, done, and very direct. no messing around with entering the crop 'space' of the viewport. saves time and you are looking at the sheet when you do it.
  11. Try using the Clip Tool instead. Create the Viewport, then use the Clip Tool, in the 'Inclusion' mode. I recommend you use a section viewport when creating an elevation of a building. https://www.dropbox.com/t/4rnJvPlvRMrl4l16
  12. it would appear to me that like windows and doors, etc, there needs to be the option to 'offset' components within a wall. You can set top and bottom offset, i.e. the z value, but not the offset in the X or Y of the component from it's resting position within a wall or from the centre line of the wall or from the control line of the wall.
  13. @KJ_KJ No new perpetual, no. New licenses are only available via subscription (in the UK, at least), but you can generate legacy licenses when you take out a subscription. @Victoria Casey Fierro is referring to 'secondhand' licenses. Secondhand licenses will still be perpetual and can be sold between end users, but the 'service select' contract associated to the license, if any, cannot be transferred with the license, and you cannot purchase a new service select contract for the secondhand license. Note: 'Service Select' and 'Subscription' are NOT the same thing.
  14. That would be the most logical approach yes, but most find ISO19650 revisioning far from logical. Most practices use P, T, and C prefixes in front of their issue number, i.e. P01, T01, C01. Very clear and very logical. However, ISO19650-2:2018 UK NA 2021 only allows the use of 'P' and 'C' prefixes for revisions. It also has a status code and uses S0 (Work in Progress) S1 to S5 (Shared, non-contractual) and A1 to An, where n is the stage of the project. 'A' denotes the published 'Contractual' or 'Authorised' issue. So not only do you have to note the revision, but also it's purpose or status, so a drawing for coordination is status 'S1', revision 'P01', for example, but could be issued the next day as S0, revision P02.01, to denote a WIP drawing, working toward P02. The status 'B' used to be in the mix, but was deprecated a couple of years ago, if I recall. Refer to ISO19650-2:2018 UK NA 2021 Section NA.4.2, and table NA.2 for status codes and NA.4.3 It's a mixture of the two that give the stage to which the drawing is related. Status A5 would be a drawing authorised for use at stage 5, and this effectively replaces what many do when they put 'C' in front of the 'construction' issue. I was going to give a talk on all this and how to set up your own file naming protocols, if anyone is interested. I am not sure the above is what @Blinkglitter needs, tbh, unless working on a BIM project but by then the chances are these issues will have been written into the BEP.
×
×
  • Create New...