Tom Klaber

Saved views do a lot of this, but +1 on the class binding. That would be really useful for demo, construction, RCP, finish, presentation, etcetera. The issue I see is that you are going to find quickly that you want certain classes to be in more than one group.

Having the close out button so close the most popular selection tool means that I accidently close out my basic tools at least once a day. It is no big deal - just now - over the last 10 years - really frustrating. Hopefully this is a change that could be incorporated into an updated UI with dockable pallets.

One of the major things holding us back from going BIM is interior elevations. Our projects tend to be on the smaller <10K SF. The idea of creating cropped section cut viewports for every interior elevation seems like a tremendous amount of work to create and maintain. It would be great if interior elevations could be automatically created using the space tool. Then a space tool bound to walls would be used to auto crop an elevational camera aligned perpendicular to each of the space's boundaries. It would be a good way to start to organize the creation of the 2d set.

Having types would expand the scheduling capabilities as well.

Allplan, Archicad, Vectorworks - these are all Nemetschek companies. If they really wanted to create a true Revit rival - it seems as if they could combine forces rather than fighting amongst themselves over the scraps left behind by Autodesk.

+1 I feel like this is submitted once a year.

-1 You still select the line type for an object in the same place on the attributes pallet. I think you might need to establish a globals file or template file so you are sure to load the correct styles for new documents.

Another question about project sharing: Is there any issues with cross platforms? Can both a PC and Mac share at the same time? Thanks, Tom

Most of this is over my head -but I desperately want a smarter title block. I have never been able to get the built-in title block to do what I need - so we use a custom symbol which works alright, but it should be so much smarter. I want the title block to auto fill from the sheet layer info both # and name. I want to establish better revision tracking that auto numbers all sheets with the .01, .02 rather than having to change that manually on all pages of a set. I suspect there are ways to make this happen - but it should be easy to design your own title block and then insert these capabilities.

I am quite interested! I would love to try it out. Thanks!

I am quite interested! I would love to try it out. Thanks!

You can edit these setting for all doors or windows at once. Just select all doors using the magic wand - then select 'Settings' from the object info palette. This will allow you to set the settings and class of the tag for all doors at the same time. After you leave the dialog you can set the font size from the 'Text' menu. I thought the ids used the current font settings when the door was created - but to be honest I am not sure. As for your last question - yes - all the windows can have the same name/id. There is no naming conflict detection. I guess whether or not you want to individually id each window is up to you and how you are constructing your schedule.

+1 For massive stair tool overhaul

1+

It helps some. The big one is centralized project resources. Still confused on what happens if somebody edits a schedule/worksheet that affects a layer that is check out. I guess all will be revealed in time! Thanks JIM!

Project Sharing...A bunch of questions.... I am wondering if this is the right name OR if I am off on the concept. It seems the usefulness is as much in class, resource, and set management as it is in team sharing. Right now, projects are split up among several files for a couple of reasons. 1 is project sharing to allow multiple users to work on the project at the same time. The others are to keep file size and complexity to a minimum. While the referencing system is a pain - the biggest headaches we have are with resource and set management. We have to go to 6 different files to print a set. Sometimes it gets confusing on what sheet should be in what file. (Some of our schedules end up in the plans file because they are auto-generated which is confusing.) How does this handle classes and resources? Do all checked out layers have the same master (global) access to a centralized project library? Is my whole set finally in one place? How do the schedules work? If I am editing the door schedule on a sheet layer, but somebody has the plan design layer checked out - does it still cross sync? If my hopes and dreams are correct - it would almost make sense to use this system even if you are working by yourself.

Another call for Window and Door Types. Just like wall types - it would be great if you could configure a set number of doors and windows types and then select them from a drop down list.

We are looking at our aging hardware fleet. Is VW16 going to have new required hardware specs? If so - are they going to be published ahead of the release?

Will there be a way to convert 2015 projects that use traditional referencing to use the new VW2016 referencing system?

You are right. It was poorly worded - coming from my web design side where z-value is a setting used to establish a visual hierarchy. What I meant I think was just expressed more clearly - that this would be a class setting - where you could establish a hierarchy. I guess "Always On Top" could work and then it would just default back to object creation order for conflicts between objects both scheduled to be always on top.

I am +1ing my own post. Come on Jim! This is a good idea! I just spent 15 minutes adjusting all the RCP and Construction plan viewports again. Eyedropper works well - but it is still a process that breeds error...

Sometimes you get into a situation where you have conflicting resources between two files that are referenced. Then every time you update you are asked if you want to substitute the resource - or how you would like to map the new wall style to the old wall style. The thing is - many times these are exactly the same resource. It would be smart if VW could detect identical properties and identify that there is no conflict before asking you how you would like to map the new resource to the old one.

1+ More options and control in general with PDF exports would be great. I have given up on trying to control it on the VW side. VW is pretty bad at the PDF conversion. Files tend to be very large and cumbersome. Unpredictable. Since the PDF format is so ubiquitous - it would be great if this relationship could be made better overall + smarter.

It would be great if there were something like saved views for viewports, or 'viewport types.' This way you could set the viewport as RCP, or Construction Plan or Marketing Plan, and that viewport would adopt all the settings of the type. Mostly, I think it would be classes and class overrides, but like saved views, it can be user controlled what settings are controlled by the type. THEN - if you need to make a change - like add a class or change the override display properties of a class - you only have to update the 'Viewport Type' setting and all the viewports of that type are updated. No more eyedropper! No more classes accidently left off of that one viewport. Even better would be if they were sharable resources so that projects could share across files (maybe no longer necessary and that the office could have these resources available by default in new project files.