Wesley Burrows

Same for me. Constant force-quitting, hangs on the simplest of tasks. More beach balls than spring break.

Nice tutorial Evan! I really enjoy seeing others perspectives and solutions to problems. I hope you do more! I'd love to get your take on your VW to C4D workflow, texturing, lighting etc. Funny enough, I was watching JC Superstar Sunday Night and was envisioning the person who modeled/drew that. And of course, you had a hand in it. :-) I also just saw your new renders of it. Those look like they have Corona Renderer all over them and they look awesome! Great work man! Now, if you'll excuse me, I need to go practice, or find a new career ;-)

Most recently I was doing this in a native 2018 file, and push-pull was borderline unusable. Only a small number of my projects end life in a different VW version than they began, so I haven't noticed.

I keep running into this also. Spinning Beach Ball of Death for days.

I too wish it was a constant rolling release. Pushing out hotfixes as they are available would be huge! The constant, "This has been fixed for Service Pack X", which loosely translates to "We've fixed the bug, but you won't see it for 3 months" is silly. I think that is half of people's frustration.

Interesting! I'll keep an eye on this and see how it affects my exports!

@markdd Thank you! Much appreciated!

Anyone have one? Tight deadline and haven't had great luck with timely responses from them. https://www.atomicdesign.tv/rental/category/backdrops/diamond/ Thank you in advance!

I usually have good luck with one or maybe two "Send to Cinema 4D" commands, (but I ultimately get the same problems when using "Export Cinema 4D) then it will (seemingly randomly) stop exporting the whole model, entire layers will be missing, geometry won't be updated, restarting VW fixes it for me for another 1 or 2 "Send to Cinema 4D" operations then rinse, repeat. Contact tech support about it. They have been able to replicate my issue (and I guess a few others having this problem) but I haven't heard back about it in months and I can't get responses to my follow-up emails, Last response was December 5th. I've been dealing with this issue for quickly approaching a year now the the problem remains in 2018 SP3. Perhaps the more examples they see of what's happening the better chance they can get it fixed before it puts me in an insane asylum.

It appears to be included with Cloud Services. I see it as part of my account now.

Nice! I've been excited about this since seeing a demo @ Vectorworks Design Summit last year!

I was under the impression that "Reset Braceworks IDs" would fix this. But I just tried it and it did not.

My dropbox folder is on an external raid array, I am unsure how to tell cloud services where my dropbox folder is as I can't find a setting that allows that. Anyone?

@JimW I'm using 2018 SP3. I just rendered this viewport as Artistic Renderworks, it worked fine. I changed the scale of the viewport from 1/4 to 1/2 and now the viewport will return blank after "rendering". The below video shows the update failure with "Artistic Renderworks", but I also tried with FQR and it did the same thing. Hidden Line worked, and so did Open GL. Restarting VW's fixes it. Render Update Fail.mp4 Not the geometry issue at the moment, I'll keep testing, but another flavor of rendering update weirdness.

As mentioned earlier in the thread, I am one of those guys that incorporates Cinema 4D for my presentation/volumetric renders. I agree with the need for this feature "in-house", but here are a few related thoughts: For me, doing these renders often takes quite a few low-quality test renders to get everything how I want before cranking out a HQ final. It has been my experience in Vectorworks 2017 and 2018 that, for whatever reason, after handful of these test renders the renderer will stop showing new or changed geometry and will just keep re-rendering whatever the geometry was when it stopped recognizing updates. You then restart Vectorworks and the problem goes away for another handful of test renders, rinse, repeat. I don't know how widespread this problem is, but I know it's not isolated and restarting Vectorworks every 45 minutes or whatever to "deal" with this gets to be pretty irritating. Another thing, there isn't always a real way to cleanly abort any render immediately for whatever reasons you may require. You have to wait until it allows it, or worse force quit. It kinda reminds me of older windows versions where explorer (the host) wasn't really in charge of it's processes, they more or less controlled it, versus something like Linux where it is basically always the boss and can kill a process immediately upon asking. My point is, I think there are some overall stability/control issues that need to be addressed to really make the requested features as useful as everyone wants. I don't intend for this to be a C4D commercial but when you are rendering it's nice to have a platform that simply doesn't crash. Always updates the geometry in renders, even after hours of changes. Can abort any render, at anytime, for any reason. Just some thoughts... -W

The visibility tool (the "v" key is also the default shortcut), will show them if you mouse over stuff. The below video is a DLVP of a reference'd file. Class Visibility.mp4

Just a friendly bump.

@zoomer, Could we maybe update the title of this Wish to more clearly reflect what we're after? Something like "Enhancement Req - DLVP Crop should be assignable to layer plane" or something. @markdd Would you mind up-voting this thread if you'd like to see this implemented? -W

At the risk of sounding like a complete idiot, is there an official enhancement request channel or is this forum it?

If you are referring to this: (2D DLVP crop of entire venue down to the space I want) Looks like this in top/plan: (As I want and would expect) When switching to an ISOMETRIC view or fly over I get this: Then absolutely, this is frustrating. You are right, there is no way to force the crop to layer plane. (That I have found)

I know this thread is old but I was just helping a colleague troubleshoot a similar issue to #1 this morning with one of my models. Some of the geometry imported to MA3D was missing a side or perhaps it was transparent. For example: Stage PIO was missing the top deck surface (I'm not sure if it was missing or invisible). The frame/legs were all there. I also tried drawing a simple rectangle and extruding it to be the stage. Same problem. I had similar problems with symbols, which contained, you guessed it, an extrude. The problems went away when I converted any of the extrudes to Generic Solids, or Solid Additions etc. (You may have to use "Convert to Group" for PIOs first) Basically it seems to like most geometry that isn't a simple extrude. What I suspect is something similar to when I started exporting my VWX files to Cinema 4D for Lighting/Rendering/Texturing. If you are setting your own "user" origin (0,0) via mouse click it doesn't necessarily line up to Vectorworks hard coded un-moveable "Internal Origin". Cinema 4D uses the vectorworks "Internal Origin" as it's world (0,0,0), I imagine that MA3D does the same. If you go to "tools -> origin -> locate internal origin" you should see a blue cross-hair appear that is the documents internal origin. (this is the one that exports are usually based on) So I typically line up my DSC with this cross-hair set the User Origin to match it. Perhaps this will save others a few hours of frustration in the future! -W

I've encountered similar, though maybe not identical behavior. Basically whatever you initially insert the Motor as, say 1T the weight of the hoist/chain etc are taken from, then if you change the motor in the dropdown to 1/2T it will not update the hoist with the 1/2T's weight, it will retain the information initially loaded with the 1T (or whatever you initially inserted). The only reason I noticed is because is because of braceworks calculations and it's for sure annoying.

Drives me crazy too!

This doesn't happen every time, but much of the time, across different files. Anyone else? In the last 2 or so weeks, it sure seems like the overall stability of VW and general responsiveness of it really has taken a turn for the dumpster. It's conjuring up memories of 2017 SP0, SP1 and SP2. It seems like the latest security update for High Sierra and VW may not play well together.

I believe this was also an issue in 2017. But after a while of doing geometry updates and test renders shift + cmd + F on the design layer it eventually will stop rendering any new geometry changes and just re-render whatever was there when it stopped recognizing new geometry. Restarting vectorworks fixes for a while, then rinse-repeat. Why is this?