PVA - Admin

Still discussing this at length with the industry specialists/architects here. This will likely be broken up into multiple wishlist items, however I will keep you posted.

This effect should be achievable by altering the value of Indirect Lighting in the custom Renderworks options, to the best of my understanding. If there is a difference between that and ambient occlusion's effect that it isn't capable of creating, let me know the specific differences and i will look into it.

Unless im misunderstanding the question, in the symbol thats used as the base of the instrument, the 0,0,0 point should be where the instrument will insert. Do you have the "bottom" of the geometry inside that symbol at that location or slightly above it?

^ That is what I would normally suggest, but I was confused by this part: I couldn't discern if they just didn't have foreground AND background renders on a single viewport in use, or the sketched lines were rendering improperly.

I just tried to do this here and couldn't complete it either. The unequal sashes weren't a problem when using the Custom sash style, but you're right, the muntins aren't individually controllable. I was able to recreate the same sash configuration as your image, but then the muntin sizes could either all match or be disabled, which was incorrect. If anyone has figured out a way to do this, please let us know. Otherwise ill move this to a wishlist request.

I think this is an issue we are tracking where libraries are not being installed properly. Working with Christiaan in another thread on it currently: http://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Main=38460&Number=190210#Post190210

I agree it would be a good addition, however I must say that it is unlikely anything like this could occur soon, the very act of Vectorworks crashing breaks the components needed to alter how the next reboot of Vectorworks will occur. You've probably seen similar problems if you've changed Vectorworks Preference options, then not restarted the application and had a crash, it will be right back to the settings it was before the crash, as they aren't saved until Vectorworks is closed. This is different than Document Preferences, which do save when the file itself is saved, but unfortunately document preferences wouldn't be able to dictate to Vectorworks which files it should open. I am not saying this isn't a good idea, just that the way things are arranged now, it would likely be far off. (Also the whole logic of "make Vectorworks not crash in the first place." instead ) Either way, submitting now!

I agree! I am pushing for something similar at every opportunity.

Woops it was in 2014, my mistake. Here:

Download and install this driver, the one on your machine currently is a few years old and updating that would be the first step: http://www.nvidia.com/object/quadro-tesla-grid-win8-win7-winvista-64bit-320.92-whql-driver.html That card should be more than capable of handling OpenGL. However, if after installing this driver and rebooting, Vectorworks is still behaving slowly, contact us at Tech@vectorworks.net and we will continue troubleshooting there.

Could you reply back with a screenshot of what you are getting using the foreground render, please? http://kbase.vectorworks.net/questions/892/How+to+take+a+Screen+Shot

MichaelK is exactly correct. Usually for presentation you can keep a sheet layers DPI around 150. For quick test renders 72 is fine but will be a bit pixellated/grainy. Most of the time you would not need to increase DPI past 300 at all except in the case of extremely large prints.

I feel Save Viewport Cache should be ON by default. I can understand the reasoning behind leaving it off in the past, file size used to be a major issue. However, most machines now come with a minimum of 500GB of storage and the convenience of not having to re-render (in some cases dozens of viewports) each time a document is opened far outweighs the file size reduction. Submitting now.

Does this occur even in a new blank document with a few 3D objects (spheres or extrudes) placed in it, then rendered in OpenGL? Or does the slowness only come with more complex files? Also, reply back with the following, please: http://kbase.vectorworks.net/questions/627/DirectX+Diagnostics+and+System+Profiler

I do. Also, please compare the size of the two files at the end and let me know if they match.

Mainly because we stretch across Mac and Windows, and that a set of 5 of our tools is as complex as most developers entire applications. Getting something like Evernote or even Microsoft Word rewritten for 64bit would be the equivalent amount of work of us doing it just to the Basic palette. Also, management has to balance where engineering resources go, I'm sure if we devoted all of engineering to this task it could be done rapidly, but then there would be no development of new features and every single tool and command in vectorworks would need to be completely re-tested for bugs and issues related to the conversion. Even Apple didn't convert its entire line to 64bit until the last year or two and there are still things left 32bit in OS X to this day. We don't even have a fraction of the personnel and budget they do for research and development.

I have had these problems with a number of users using the .vpkg installers, mainly with the ones larger than 2GB. Do you happen to recall which of the .vpkg files you used to install? Was it the "everything" one that was listed at the top?

This is as close as I was able to recreate from memory, I had better luck using the Plastic reflector and messing with Fresnel for the color to give it that slight bluish or greying tinge (whichever you're looking for) around the edges of curves. The attached file JUST has the texture in it, so you'll need to import the texture into a document where you already have objects to try it out. One of the tricks when trying to get a chrome/mirror/reflective texture is to make sure its tested completely within the environment you're going to put it in, anything over reflection 50% looks bizarre unless you give it a ground/sky and other objects to reflect. I know I ended up with a much better version before, i'll keep looking.

Does it not show up in the preview windows, or does it not appear both there and in the document itself? Does the same thing happen even in a new blank file on that Mac? A general note, but make sure you have the latest service pack for 2013, it should be SP4 as of this posting: http://www.vectorworks.net/downloads/ServicePack.php?major=2013&servicepack=4

Please do! I know there has been a huge amount of confusion, frustration and outright loss when it comes to feedback about wishlist requests and bugsubmits. Unfortunately I can't feasibly go back and find everything that may have been lost (I am going back and finding many, but I am sure I will miss more) but I will do my best to get everything submitted from now on into the proper channels and I am currently working to get a more automated/detailed feedback system regarding these sorts of user requests that will allow you to see the results of your work.

There were a few tweaks to this in Vectorworks 2014: However the above tips are still excellent for more control.

The above two posts roll in well with this thread: http://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Number=190081#Post190081 A more direct and complete-control method to map keys, even the ones that vectorworks has locked in, such as spacebar, esc, del, backspace along with a bunch of others. I'll be submitting it shortly.

I think adding a "Save As in Current State" or something similar is an excellent idea, maybe appending a date/time to the end of the filename? Submitting now. I am not sure how a tagging system would work cleanly however for tagging important sheet layers without risking losing some, that may be messier than a rethink on how the list is presented in the UI instead. However I will mention the topic in general.

Could you provide some specific examples of pain points using it currently? I know overall it does need a good bit of attention, but for these sort of requests I need to place specific task requests. (I completely understand that "Make it not clunky" is a perfectly reasonable request for some of the tools and commands, but wishlist items will be addressed MUCH faster the more specific they are.)

Even a Vectorworks Preferences option for "Make newly created Classes and Layers Active" would do the trick for this I think, do you agree? Or do you feel it should be on a case-by-case basis each time you create a new class or layer, the user is asked?