Christiaan

OMG, can't wait to try it. Sounds like a good start Katie but I think it's a shame NNA have gone for simple 'point to library' method. The problem then is that you become dependent on a network and a server. What happens if people use laptops in and out of the office for instance? Or what if the server or network go down? You're also increasing network activity unnecessarily. For these reasons I think we need a system that allows a manager to *synchronise* user resources with a central/master library. See my thread here on the topic: http://techboard.nemetschek.net/ubbthreads/ubbthreads.php?ubb=showflat&Number=64934

We were discussing 'v2008' at the pub last night and someone suggested this was probably the reason. It seems rather obvious now that it's been mentioned. And really disappointing, even though we've been through The Enlightenment, that we still live in a world where so many people are enslaved by magic, illusion and the supernatural, and afflicted by triskaidekaphobia. Well I, for one, will be referring to it as v13; sorry if that brings the wrath of 13 unto all. It's of some comfort to me that it's actually being released on the 13th. What a pity it's not a Friday.

I see. We haven't used this detail for a couple of years now, partly because of energy efficiency requirements and cold-bridging, but probably because local builders (i.e. London) are used to them too, as you say. Where are you based?

Yes it is possible. You need to use the plugin window rather than a plain symbol (as far as I know). - So, insert a plugin door/window into a wall (i.e. a wall which has 3 components), with the middle component representing the cavity. - Select the window and click on 'Settings' in the Object Info palette. - Go to the Wall Detail tab and add "1" to Number of Components for both Interior and Exterior (or maybe just the Exterior?). Having done this now select the window (in the wall) and drag the additional selection handles on each side of your window?doing so parallel to the jamb?to create the cavity closer return. By the way, you can also do insulated cavity closers by including them as part of your [plain] symbol and then adding 2 loci (1 to each jamb, inside the line of the cavity closers). These loci tell the wall where to draw to, instead of simply drawing to the outer extremities of the symbol by default. Surprised you're using brick returns actually. How come you're not using insulated cavity closers? (just curious)

Try 01, 02 instead of 1, 2.

Hope so, or it's still unusable.

You can also use the Split tool in Split by Line mode.

I've never got the logic behind calling software after a year. But glad to see this version is going to clear up a lot of long-standing issues: select and edit multiple windows and doors in walls (yes!), OSX Spotlight search integration, unlimited colour choices, rotatable 2d views (hope this includes the ability to produce site plans without layer links), classable wall components, object based opacity, cropped layer links and design layers, design layer viewports, CAD manager features and improved library management (how tantalising!)?"save changes in your resources directly back to office-standard libraries with one click" (fantastic!), wall components in sections, improved navigation between viewports and design layers, improved 2D stair graphic (I'm sure it's not the end of this one) Interested to see how the 2D rotate deals with legacy files. Two-way worksheets sound great too, if that means what I think it means. Looking forward to seeing these updated icons too (bout time!). And stuff still missing: advanced wall joining, advanced team workflow (aka AchiCAD TeamWork), single tabbed window interface, multi-storey stair PIO, date stamp for cloud tool. And, geez, the None class is still there! So NNA's been busy. No pricing yet for UK customers? The quote button, is that just for U.S. customers?

I could definitely agree to that.

For now we've resolved to put revision clouds directly on the relevant Sheet Layer. This has two advantages over putting them in Viewport Annotations: 1) less clicks between making your changes on the Design Layer and getting to the Viewport Annotations to add a cloud; you simply switch to the Sheet Layer and add your cloud, then switch back again 2) with all Class attributes in the Viewport overridden to be black the revision clouds drawn straight onto the Sheet Layer (and on None class) are coloured (dark red in our case), which helps keep track of them. Come the next revision we'll delete all clouds and start again. Can anyone think of a disadvantage in doing it this way?

object info palette

Well, to be honest bc, I kind of like the up down arrow as you've posted.

Well, think about a mid-level. You can go both up and down from the floor plan you're looking at. If you took this U.S. way of looking at it to its logical end you would draw both up and down arrows on a mid-level stair. Or is that what you're saying you do (per flight)? Yeah, I'm just taking the chance to have a dig at U.S. conventions, which often seem a bit baffling to me.

I've attached what I think is better double stair break graphically.

Also need the ability to independently extend left and right rails past last steps.

The British Building regulations get it correct for instance (see attached). i.e. the focus, dimensionally, should be on how humans use the stair rather than whatever makes sense mathematically to some computer programmer.

Then I would have said the rail height should be measured from either the edge of the nosing or from the point the riser starts.

I've heard little but praise for this device. I'll probably get one if VW supports it.

Oh yeah, and support for independent rail offsets: http://techboard.nemetschek.net/ubbthreads/ubbthreads.php?ubb=showflat&Number=84923

Can't find if I've asked this before but I'd like sophisticated support from the Stair tool for multi-storey buildings, including: - 'height-by-Design Layer' for more than two levels - double line breaks to show mid-level stairs (maybe something like the attached image) - handrails that can be extended onwards from the stair as landing balustrades in customisable directions and lengths - and maybe the integration of main-landing floors Well, I think that's about it for a day of head-butting the stair tool.

Sure, if you're actually standing at the top of the stair, but you're not standing at the top of the stair, you're looking down on it from above. The objective of the stair arrow is to show you which way the stairs go, not to help you pretend you're standing at a certain level, which is what you implicitly acknowledge when you put "up" on mid-level stairs.

In my opinion the basis for extending handrails should be risers not treads. Risers are more definitive than treads. So, for instance, currently if you put, say, 300mm in to extend the top handrail, it extends 300+1 tread past the last riser (so a 550mm extension if you have 250mm treads), i.e. it extends past the "top tread" that is part of the floor, rather than the last tread before the floor. So with my 250mm treads I need to change it to 50mm in the settings to give me the 300mm extension I need. Also, a minor bug: under the Handrails tab of the Stair PIO Settings it currently says: "Extend Top Rail Past Last Tread." But "Top" shouldn't be there, being that the tool is for extending past top AND bottom handrails.

Support for reinforced concrete would be good, as attached profile.

I'd like the ability to specify different offsets for the left and right handrails. In a multi-storey stair open down the middle, for instance, the handrail on the wall might be offset from the wall by 60mm, while the inner handrail sits flush with the stair edge.

It does this already doesn't it, when you use 'overall height by Design Layer'? I'd prefer that it gave the option for either or, because in the UK/NZ we always show the upwards direction. What do you do, for instance, when you're doing multi-storey? You don't have a upper and lower floors, you just have mid-levels (as above, we always simply show the upwards direction).