PVA - Admin

Especially since the Add Vertices mode of the Reshape tool is selectable when you have a wall selected, but it does not allow for the adding or removing of a vertex. Submitting now.

If you mean the ones that used to install by default with the Vectorworks installer however, they are now added this way: http://kbase.vectorworks.net/questions/1170/Vectorworks+2014+Content+Library+Installation

However, a lot of what users think 64bit does is actually the realm of multithreading. http://en.wikipedia.org/wiki/Multithreading_(computer_architecture) Basically the use of ALL of your CPU cores for each operation, rather than the current state of many tools and commands where they can only utilize one CPU core at a time, making a 12 core machine move at the same speed as a 4 core machine for these single-threaded operations. Things like Hidden Line renderings and anything involving CineRender (pretty much anything Renderworks does) are already multithreaded. But the conversion of the various tools and commands need to be done essentially one at a time and may take longer than the initial 64bit rollout. BUT, all of this is indeed coming. A substantial portion of engineering is working on these areas constantly.

On OS X I use iStat Menus. It used to be free but I believe there is a price now. http://bjango.com/mac/istatmenus/

You can press the Delete or Backspace key to back up one step while still remaining in the tool. Similar to the polygon tool or wall tool, Delete will step one operation back in the series but not deactivate the tool.

Confirmed in your file, submitting now.

I agree completely. It is coming. If I knew an exact date I would tell you.

I tried a quick sample created in Vectorworks 2013, converted to 2014 and did not see the problem, I also couldn't get it to happen in a new blank file. Would you please send the file to tech@vectorworks.net with the subject "Attn Jim" and we can have a look.

We are actually about to have a meeting about things close to this. Ill bring these suggestions up directly. In any case SOMETHING is needed to indicate when new content arrives. The Video Tech Tips are sent out with the regular email/letter I believe, but the new VSS content should have its own alert of some kind since it comes more frequently but at odd intervals.

Confirmed, looks like those particular sounds are not working on Windows 8 at the moment. Working fine on Windows 7, Windows XP and OS X 10.6 and 10.8 here in testing, submitting this as an issue now.

Yes, saving them to an outside folder is absolutely superior and should be done whenever possible. It isn't only this type of issue specifically that we are having permissions issues with however, some tool defaults among other things will always need to write to these locations and I was trying to track down why they weren't able to. Sorry I didnt make it clearer in my questions before, this was simply a symptom of something else we're looking for cases of.

I did, yes. I wasn't sure that the result I got was correct however until I just heard from you, i'll let the others know as well! Thank you.

Not that one in particular, I may give it a try. The main problem was getting Vectorworks to "see" the QuickTime installation, even if i had them both installed in the same environment.

Submitted with these specifications.

Is there any difference in the source of the SHP files that corresponds with them working/not working? Or does it seem to be random?

Feature request submitted.

I had tried repeatedly and never got it to work. The furthest I was able to go was using Wine but I was not able to get past the reliance on QuickTime. It is possible that once that dependency is removed that Vectorworks could be rigged to run on a Linux distro, but thats completely a personal guess on my part. (However I will totally be trying it.)

I believe OS X Server can now be run in a virtual environment, but only as long as the hardware it is run on comes from Apple as far as their EULA goes. Im not certain which OS Vectorworks Cloud Services uses as virtual machines to accomplish rendering, however its most likely Windows because of the hardware restrictions.

Unfortunately it isn't only a matter of how many times things are asked for, before they can add certain features like these the groundwork within the software has to be laid. However i'll relog those requests immediately.

Normally in these cases it has been geometry we can locate and correct, please send the file to tech@vectorworks.net with the subject "ATTN Jim" and we can have a look.

What we are trying to narrow down is why this happens to some machines and not others. Also, the regular protection applied to Program Files/Program Files(x86) shouldn't extend to the user data folder locations, otherwise no workspace changes or library additions would keep after relaunching the app.

Confirmed in a bunch of test files here. Submitting as an issue now.

After speaking with one of the lead engineers for Window objects, it breaks down into a few different chunks: To start, the Window preview panes currently do NOT take the fact that windows are inserted into a wall into account. So the preview you see is -normally-) how the window will indeed look like it does in plan, if it is NOT inserted into a wall. This explains some of the discrepancy when looking at the preview. (I would argue that a window is 99.999% of the time inserted into a wall, but we will get to that in a bit.) Next, the previews default to two assumptions. The first is that the top preview pane will show the "front" or exterior of the window. The second is that the bottom preview pane will display as if "up" is the exterior of the window. This explains why when you have a window in plan where the "bottom" of the window is the exterior, it is shown flipped in the preview, which further explains a few more of the discrepancies. Also, the Sill displayed in the preview, since it does not acknowledge the wall insertion, will nearly always display inappropriately because the sill when its window is inserted into a wall will be locked to the wall. These are technically not bugs however, as this is how the features are currently engineered to work. Mainly because of the level of complexity required to add the wall to the preview, which would need to take into consideration wall styles, components, wall direction, wall end caps, features-in-walls etc. By saying all of the (verbose!) above, I by no means suggest that this is how it should ALWAYS work, just that these would be broken into feature requests instead. Mainly: 1) Add the ability to accommodate wall insertion in the window's preview panes. 2) Allow sills to operate/align independently of walls, mainly in regards to the preview. However, I am not even slightly an architect. This is simply how I have come to see the current situation regarding this initial post. If anyone has anything to add or needs to slap me upside the head, please do so now and we will get these added to the appropriate lists.

The main focus being that it would be desirable to have the Space object text specifically rotatable separate from the regular "Adjust Flipped Text" option? Would users always want it aligned a certain way, or would a between-0-and-360 sort of setting be better?

I have found a number of similar cases in our issue tracking system here. It is likely that this will be corrected in SP1 for Vectorworks 2014 due to a number of other corrections made to fix various other related issues.