Jim Smith

Thanks for this Andy, I didn't see Perimeter in the Data Tag list. I would still like a Dimension line that one could follow a path as I illustrate.

I'm going through a really place right now with VW; & I'm generally a big fan. I have spent the whole day playing back-a-mole on a project that I should have been finished days ago. Ever since the intro of Storys the walls in VW are made of unicorn horns.

Thanks Kevin, but I don't see this as much use in what I need to do as it would take several more steps to give a result that's not what I really want.

Is there a reason that Walls do not accept All Attributes when the eye dropper is used? Several iterations ago (circa 2012 or 2014?) this worked. Now, not so much.

Ok, so a duplicate of the Spotlight cable tool but used to call out things like path of travel of perimeter

Thanks Allan, but not my first Rodeo. I'm just getting really frustrated with VW acting in a very wacky and arbitrary way from one file to another. My workflow is going out the window, as I'm forced to have multiple small, non template files in order just to see stuff like walls, roofs windows. I'm burning productive time & having to work on my own time to see client's project through. I'm frankly tempted to go back to working in VW 2014 or 16 as 17, 18, & now 19 are just not ready for primetime.

I would very much like a tool that's a cross between a Polyline, a Call Out, & a Dimension Line. Something like this:

Additionally I find that the size of the drawing defaults to the Primary monitor, not the one it was saved from.

I would like to see the following added to the OIP - 1) Area, & Perimeter of polygons to return values that may be copied - 2) Similarly with 3D objects, with the addition of Volume In item 1) I use this information to call out PATH OF TRAVEL on every project & this needs to be typed from a polyline onto a call out or free floating hunk of text. And often for both 1) & 2) I just need to know a quick volume or area measurement without having to run a spread sheet.

Milezee, perhaps you should write up a new Wishlist item so users can vote it up. Edit, Sorry I just noted you've bumped the thread!

I would like the option for the Wall Join command to work similarly to the Join Line tool so that walls will shrink back.

I've been working in a new VW 2019 file, added a roof object and now the whole thing isn't visible in 3D. I'm quitting for the day & will have to start fresh early on Monday to be ready for the client. I don't recall so many bugs in earlier versions of VW.

The files that I'm having issues with are all new, native 2019 files. EDIT: Spoke too soon, this is now happening with roofs. Sigh! Visible in 2D not in 3D but copy & paste into a new blank file - Viola. I don't recall this many bugs in other iterations.

I keep getting the pester to update to Mojave & have not updated. As this thread is 11 pages long I'm still really wary of doing so. Is the advice to avoid Mojave until VW2020?

Yeah I think there may be an issue with some files over a server.

Are you using the 3D tool set? From the little I know of Rhino, many of these 3D tools work in a similar way

Can this tool be made more like the regular dimension tool? I'd like to be able to take constrained lines & type the angle to mandate the angle. Also I'd like to be able to copy & paste this value from either the OIP or the text on the dimension line.

I don't use the tool often, but I think that the following would be an improved experience: 1) Alter the inputs for bearing to allow for a "Tab" to add integers and declination. One would be able to faster add & alter these values without over writing the degrees, minutes & seconds and allow for faster alteration of compass points 2) Add a Square as a choice for a corner point (almost every survey I've ever seen is called out in this fashion with a square BTW) 3) Add the choice to what elements have what attributes. I.E. separate the attributes for the text and the resulting poly. EG: Poly has no fill & lines are black while Text is RED & has a fill 4) Allow the tool to show parallel (or nearly parallel) lines to have the same declination 5) If #4 is too complex to achieve I'd like a "DUMB" property line tool that allows me to create a polygon first, the polygon would then generate the dimensions & I can type my own declination 6) If #5 is too much, I'd like a tool that allows me to add text on the lines that I have 100% control of. This would have other uses over & above the property line tool.

Thanks Rob, I've not attempted to make a property line by using the AEC command, (that I use all the time) for other objects; just never noticed property lines as a choice. Oh dopey me! Hi Neil, By using mental gymnastics I can get the tool to work as you & Vlado have pointed out, by going back. The issue is lines that are parallel are illustrated with the opposite bearing ie SxE rather than those called out on the survey as NxE (cue the mental gymnastics). 😁 I don't use the tool enough & generally we just want to get the setbacks for a lot. For the most part we either import a digital file or mark-up a PDF. I hate to give up on a tool, but as I say I don't use it enough. I do have some ideas that I'll add to the wish list.

Is this over a server? I have a colleague who inadvertently worked on a file on one computer that has Landmark installed, & saved it back to the server. He was then getting this error message when opening the file on another machine that only has Architect installed. His fix was to open consistently on the Landmark enabled machine. Perhaps there is another fix, but I'm not sure what that might be.

Thanks Valdo, but this tool just does not work for me. I had been using the tool more or less as you suggested in the past & really never been able to make it work. I've taken your suggestion & not imported the scaled PDF of the survey and after more than an hour my frustration is getting the better of me. The attached illustrates my frustration one may see that the tool is producing segments that have no basis in reality. The set of lines to the right is drawn on a blank file to illustrate the size of the anticipated property lines. The dopey thing on the left is what the property line tool is producing, and I think you can see that the line segment that's nowhere near correct. As you may also be able to see this segment says it's 179.33 M - but it ain't nearly that big. As I said in my first post & you can see from the screen grab I cannot get the tool to produce Azimuth that agrees with the survey call-outs. The tool doesn't work like surveyors work. The East & West survey lines are n7º 53'w but if the tool were to actually accept my inputs properly, to close the survey one would have to start introducing Azimuth that is the OPPOSITE of what is called out on the survey. Thanks for your help, but I'm going to just use lines & text and not waste my time on the tool.

My workflow is to use the Quick Keys to Rotate an object. What happens in 2019 is the object does rotate, but the rotation on screen is not seen until one moves or nudges the object. The truly odd issue is if one rotates an object by selecting the same tool from the tool palette this behaviour does not happen. This is what I see when I use the Quick Key, I can see that the object has been rotated but it needs to be "nudged" for the rotation to "stick"

Thanks very much Vlado! I'll be trying this technique later today.

One annoying thing that continues is rotated object don't "appear" to rotate until they are nudged or moved. Refreshing the screen by zooming in or out doesn't help. This can cause many mistakes if one forgets that VW actually did rotate the object, but the the rotation doesn't show up.