Boh

Thanks TKA, but that's not quite what I was asking... I'm talking about the dialogue box that pops up when you hit "File Expot Options..." You can add custom naming schemes for when you are publishing multiple drawings to their individual pdf's. Just can't figure out how to remove the naming schemes from the presets.

Ah yes I forgot to mention that they sometimes don't update. One of those little "issues". I take your method just updates one windoor object? I'd like to find a way to refresh all of the windoor objects so they display correctly (or at least all the selected ones). Overall though it is a pretty good tool. I think windoor has had a bit of work in vw2019 but I haven't gotten around to playing with it yet.

This is a bit of a headache. I've had issues trying to understand class settings with WinDoor with various things. Door swings suddenly having a solid fill was one of these things.This is what I do: I make sure that all my WinDoor classes (i.e. all the "WD-* classes) do NOT have "use at creation" select in the edit classes dialogue. You can then edit the attributes of the various WD classed objects in the settings dialogue so that they actually apply to windoor objects in your drawing.

Is there any way to remove items from this predefined naming scheme list? You can add them but I can't see how to remove ones I don't need or added by mistake?

My thought is that If it’s a live section vp then the section line instances need to placed in VP annotation space not on a design layer. Instances of live section vps placed on a design layer won’t show in othervp’s no matter what the class visibility settings are. Hope that helps.

Reference viewports can only be on design layers. Check you are not trying to put the vp on a sheet layer.

The notes database, keynote/callout tool desperately needs an overhaul. There are a few threads about databases & callouts, users either confused by how it works or calling for changes. I've been trying to find a way to effectively incorporate databases into my workflow. I do manage to use it though it is frustrating as it could work so much better. Integrating database notes with record formats and room finish data would be my ideal. At the moment I essentially have 3 sets of mutually exclusive databases all in the same program! For the aforementioned dialogue box, I get that occasionally though it does not usually keep repeating for the same note. That sounds like a bug.

Right click on the DTM and select edit crop. Delete the extg crop if there is one and draw a new one that is within the extents of your DTM. This will clip out the closed part of the contours.

It looks like you are in Wireframe render mode. OpenGL is good for working on 3d models, Hidden Line is good for sections/elevation views. Go to View Tab > Rendering or as per screenshot.

I went through this exact same process in our smallish architecture practice, trying to get everyone working the same, using the same office standards etc. We are still working on it... Re text size scaling I was really confused by this too. We had a similar issue with window id tag symbols, trying to work out which scale tag to use to suit different DL & VP scales. You might find the attached pdf useful as a reference. The id tags are part of the window objects so had to be on a design layer. In summary it is always best if the DL scale = VP scale. WinDoor ID Symbol Scale Comparison.pdf

In annotation means inside a sheet layer viewport annotation space. Text in the annotation space is not effected when design layer scale is changed. It will scale up or down if viewport scale changes however (but will not need to be repositioned). For symbols I generally try to avoid putting text in them for this very reason of scaling. However if you need the text and you often have these symbols needing to be represented in different scale viewports then I would suggest have text classes for each scale and control their visibilties by viewport class settings. You could link the symbol text objects to a record format so if need be you can edit all the text in one go via the data tab. hope that makes sense.

We also work in the way Jim does. Typically the only text on design layers are tags like room names, sanitary fittings names and the like which we want visible in multiple viewports. These text tags will have their own classes so they can be turned off in detail plans at different scales where they aren't necessary. Though you are looking at 2d drawings, notes in annotations is how you would also work for 3D live section viewports and elevations too.

I'll have to have a play with this! Thanks for posting.

I wish I could do this myself however if there is a script or scripter keen for a lttle challenge... Sometimes, though we try to avoid it, "classed" objects are placed directly onto sheet layers and when it comes to print these sheets the classes can sometimes inadvertently be turned off and therefore not print. Similarly we also have a bunch of classes with a " NonPlot* " prefix that all need to be turned off prior to printing. Additionally we occasionally need to double check viewport visibilities to ensure that these NonPlot classes also have their viewport visibilities turned off. At the moment I have a saved view I run prior to printing that turns on all classes except nonplot classes which are turned off. However this needs constant checking/updating as more classes are introduced to a file. A script that turns off all "NonPlot*" classes and turns on all other classes would certainly be useful to me and maybe to others too. If possible the script would also check the viewport visibilities of all " NonPlot-* " prefix classes are turned off (whilst leaving the viewport visibilities of other classes left unchanged). It is cheeky of me to ask, but I have been using the saved view method for a while and can carry on doing it that way. I just thought if it is easy and someone else thought it worthwhile then a clever little script to share on the forum would be much appreciated by more than just me :-). Thanks

Liking that Waldo technique! Thanks Michael. All seems to be working well!

Oh I didn't notice it was the opacity setting changing. Well spotted! I was looking at lineweight, pen colour etc. When I change the none class opacity back to 100% all seems to go back to normal. Will make sure I use this script only outside groups/viewports for the meantime. Cheers

Ok. Sent you the file. Hopefully you can see where things are going pear shape. 🙂 Cheers

So I just used the MakeClassWithObjAttribs script for the first time on an actual project file and it went weird on me. A whole bunch of notes & annotations all 'disappeared' from every sheet layer. They were still selectable but no colour or fill even though the attributes palette say attributes are still 'by-class'. Many, but not all disappeared objects are on the none class. The none class is not listing in the organisation dialogue but is listing in the navigation palette. Couldn't undo so need to recover file from backup. Hmmm......

My set up on two screens. The resource manager on auto hide on secondary screen with floating view pane below. Auto-hide script palettes at top of main screen alongside snap palette. OIP docked full height to right so minimal scrolling. Tool palettes to left of main screen. These have been customised to a standard office workspsce.

Sorry, I didn't realise that was an OzCad thing.

New to me! Found it in vw2016

There is already a hide objects command. Only discovered it myself recently.

Have you tried the reconcile notes tool? Not quite what you are after but might help. I've just started playing with it recently and haven't quite got the hang of it yet but it will pick up unlinked callouts which you can then update to or from a database.

You can turn the labels off in the settings dialogue.

Thanks Aspect. What about the inevitable revisions? Do you need to go through each sheet and update the duplicated notes individually or do you use the reconcile notes tool? I just had a play with the reconcile notes tool and yes it looks like it does two way updates on text & call outs. Still need to play more but it looks like it needs to be used with caution as it seems you could easily inadvertently change central database notes rather than a cloned project database.