Aristocrates

So with over six years since this feature was requested, has there been any progress? I'm so fed up with paying thousands of pounds for new versions of Vectorworks every couple of years, and fairly basic features like the one described here still not being available.

I would also like to import vector image files into Vectorworks, specifically SVG. SVG is a publicly available web standard, and should be very easy to convert to Vectorworks forms of data. They are very well defined, so there shouldn't be any ambiguity about what the result should be. I feel like it's just laziness on the part of Nemetschek that they haven't implemented such functions.

I've updated to SP5 and this issue is still present. Not that I was expecting it to be solved this quickly, but just want to keep the pressure on to get this sorted.

After what might have been a year or two of relatively stable Vectorworks use (by which I mean no crashes, not absence of all sorts of other bugs), SP4 has suddenly started unexpectedly quitting with no notice, and seemingly always the longest possible time since the last autosave (indeed, it might even be it attempting to do an autosave in the middle of performing another task that is causing it). I'm sorry I can't be more specific about what I was trying to do when it crashed. It happens so suddenly and so unexpectedly that it really caught me by surprise. Anyone else having crashing issues since SP4 release?

Yup, I've been getting this too. It seems as though Vectorworks has recently become infested with bugs. Really not what you'd expect when paying the amount we are.

@Adam Robinson Any news on this issue? By the way, this happens with me even with a blank file (obviously populated with a viewport to a design layer).

...provided they fix this issue!

OK, it turns out I just needed to select my custom workspace from the menu. Still, it's annoying, when none of this is due to anything that I've done. I was just trying to use the program the very same way I always have.

Doing this has meant I've lost all my key mappings, and even after reversing this process and transferring back to the old settings folder, they're still not back. You see, this is why I hate updating Vectorworks! It's more trouble than it's worth! I've spent what, three hours, so far, trying to sort out this problem, which is well over a hundred pounds worth of my time, and it now looks like I'm going to have to spend another hour or two reconfiguring my key mapping, or figuring out how to get my original key mapping back. I'm so frustrated, and it's only 9:55am. 😠

This changed something, but it just caused different weird stuff, rather than stop the weird stuff. Here's another video. I'd prefer not to share the file on a public forum. Can I email it to you? Screen Recording 2019-08-13 at 09.18.31 480p.mov

@Adam Robinson Yep, here you go. The first one of these didn't work because file size too large. The second is Low resolution for small file size but you should get the gist. Yes I get the same behaviour in other files. I only have one computer with Vectorworks 2019. Screen Recording 2019-08-12 at 17.28.22.mov Screen Recording 2019-08-12 at 17.28.22 480p.mov

Update on this topic: This now seems to have been corrected.

I dread updating Vectorworks, since every time there seems to be some new bug introduced. This time, here's what's happening: I am in a drawing in sheet view, and edit annotations to edit some of the annotations. From here, I enter the viewport design layer to edit something on the design layer. So far so good. Once I've finished editing, I press the "return to viewport" link at the top right of the page to return. Upon returning, it returns into annotations mode, as I would expect, but I can't select any existing annotation, and any new items I try to add come out at the wrong scale in odd ways. In exasperation, I press "Exit Viewport Annotation" to get back to proper sheet view. Once I've found my viewport again (since for some reason leaving viewport annotation will mean that the centre point of the view also jumps to somewhere completely different to both where I was previously viewing or where I was viewing when I pressed exit annotation, but this is a topic for a whole nother topic, and has been going on far longer than this recent update), I can then enter to edit annotations again and it operates as expected. This is incredibly disruptive to my workflow. What are you playing at, Vectorworks? Vectorworks 2019 SP4 Build 490894 on MacOS Mojave 10.14.5

Unfortunately yes, although that has led me to find an interesting behaviour, which is that the full text does actually appear, as long as there is at least figure 1 in the number. So 0.13, 0.18 and 1.00 appear in full, but 0.05 or 0.35 get replaced with ellipses. This suggests that the space allowed for the text is just enough when the character is narrow (i.e. 1). but not enough when it is larger (i.e. any other figure).

I've now updated to the latest version. Didn't help at all.

I'm getting a problem with the attributes tools in Vectorworks 2018 (SP5 Build 458934) on MacOS Mojave 10.14.1. It's fairly difficult to explain, so probably best just to see the attached video, but basically the problem is that you can't read the pen size when an object is selected because the text overfills the box and it replaces it with ellipses. You have to go into the pen size menu just to tell what pen size you've got set. Whilst you can stretch the box, and it does appear, as soon as you select a pen size, it reverts back to a size which means you can't tell the pen size again. This is beyond irritating. Can anyone tell me how to fix this? Or file a bug report so that this can be sorted out in an update? Screen Recording 2018-11-19 at 09.57.19.mov