PVA - Admin

No problem. In the future, if you get a similar error in OpenGL as well as in a Renderworks mode like Final Quality, you wont need to mess with drivers. If an issue is only in wireframe and OpenGL, but Renderworks works alright then its driver update/replace time.

If you completely close down Vectorworks and then re-launch it, then open that file and render, does the same issue occur? This test can often determine if it is a geometry problem or if the rendering engine has become stuck.

Double and triple posts are also a symptom of this delay. If it happens to you, don't worry, I will delete the duplicates I come across if you no longer can.

My Prusa i2 is performing my test work for the moment, we also have a MakerBot Replicator 2 onsite for testing as well used by the Industry Specialists. [img:center]http://i.imgur.com/7iiVYUP.jpg[/img] Im designing a much larger replacement for my own, a project which I will likely share here since it fuses Vectorworks and 3D printing nicely in that I will be designing the overall printer in Vectorworks as well as printing various parts of it from STLs exported from Vectorworks directly. I hope this eating-my-own-dogfood approach will help us get a lot of the kinks ironed out of the design > export > print workflow. So far it has already led to a few new features with STL export in 2015 but I would personally like to see many more. If any of you have any suggestions, feel free to wishlist them or post them in this forum so they can be poked, prodded and polished by the community.

It was indeed confirmed as a bug, even in simple tests we saw the issue. Luis submitted it this morning.

Got it appearing properly after performing a layer import. There seem to be problems with the conversions of a Roof object as well as some column structures, which you will probably see if you perform this procedure to bring your geometry into a new 2015 document: http://kbase.vectorworks.net/questions/790/Layer+Import However the odd aliasing issue was gone once I performed the Layer Import. I will see if I can track the issue down more specifically, Layer Import is a heavy big hammer of a troubleshooting step as it removes sheet layer info. [img:center]https://techboard.vectorworks.net/ubbthreads.php?ubb=download&Number=11219&filename=2d%20polys%20and%203D%20geometry%20in%20Fast%20RW%20test%202.PNG[/img]

Double and triple posts are also a symptom of this delay. If it happens to you, don't worry, I will delete the duplicates I come across if you no longer can.

No problem, we'll figure out which and get it sorted. Not to judge, just an FYI, I was told this by the head of engineering recently: They would rather have you submit bugs that turn out to be user error rather than not submit bugs that you aren't sure. I was pleased to hear that and my bug submissions went up 20% that day, hehe.

Getting the link from Luis now.

Thank you! I agree. The tech is still in its early stages as a prosumer/consumer product, but its coming fast. Just brought mine into the office, will be testing exported geometry from Vectorworks with a focus on getting Architectural objects, (Raw 3D geometry seems to export pretty well at the moment) printing as expected. At the moment focusing on a best behavior for exporting models with certain classes (specifically glazing classes for glass) turned off to make it easier to export models with "open" areas instead of solids if the user wants.

Moved to wishlist and submitting request now.

A dropbox link or using mailbigfile or another transfer service is fine.

Issue submitted.

The request is still active, I will add this thread to it.

Currently on OS X, the control of what cards power what is under the discretion of the OS if the software package doesn't control it directly, which we currently can not do. I think Apple's Final Cut and a few other packages can as of now. On Windows, the display of what is onscreen can only be one card unless the two or more cards are hardware linked via SLI or Crossfire. Some applications use the GPU as core for rendering but not display, which is where Vectorworks would benefit the most from in the future from what I understand.

Its bad. IT is still trying to track it, another thread about it here: https://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Number=202605&Searchpage=1&Main=40586&Words=forum+lag&Search=true#Post202605 I get the same issues here as well. I use the Active Topics section to track new posts for the time being.

You should be able to use the polygon without any conversion in the creation of the site model, are you not able to convert them to 3D contours?

Not so far, do you have the same issue after bringing it from the converted 2015 file into a new 2015 document via this procedure: http://kbase.vectorworks.net/questions/790/Layer+Import ?

Excellent! No problem at all.

I suspect you could drop Blurriness to Medium, not notice a difference in quality but dramatically reduce render time without changing any other settings. Its one of the most resource intensive render settings.

If that happens, email the file or a link to it to tech@vectorworks.net, we can have the cloud team look at it directly. Some of the issues that can occur are detailed here, but not all: http://kbase.vectorworks.net/questions/997/Cloud+Job+File+Failure

Well a Polygon would just be a polyline that was closed and had a surface to it. If you use the split tool to break it into edges that do not close it would be a polyline. For many purposes though, a polyline and polygon are interchangeable.

If they are connected end to end, normally yes. Select one of the line segments, then Edit > Select Connected Objects, if it then selects a number of other line segments, these can usually be combined into a single polyline via Modify > Compose.

Confirmed here as well. This seems to be the case in 2015 but not in 2014. Checking to see if this was intentional (though I suspect not,) or if it needs to be submitted as an issue.

With a polygonal object selected, you should be able to use Modify > Convert > Create Objects from Shapes. Some other workspaces have it listed under AEC > Create objects from shapes (or Landmark> or Spotlight>) You should be able to add the Space tool back to the workspace via the workspace editor, unless you have a localized copy that does not include it: http://kbase.vectorworks.net/questions/745/Workspace+Editor (I do not know if any localized versions omit the Space tool by default.)