Andy Broomell

Yes, I think the term "embedded" better describes how it works. Although, one of my students recently asked "So it's like the camera gets sucked into the viewport if it's selected?" I said "Absolutely," and now might start describing it that way to begin with 🤣

This was implemented in VW2020. 🙂 In general I think Title Block Borders are one of the best improvements in the new version. You can definitely tell the team has been listening to user feedback to create a tool that works well. Thanks @Nikolay Zhelyazkov for your presence on these boards and for the hard work of you and your colleagues!

The ability to control this was added in VW2020 🙂

Interestingly, a small part of this wish was fulfilled in VW2020, but unfortunately not the most important thing. Essentially you now get a pop-up asking if/how the camera should be embedded into the viewport, but currently there's no way to connect a viewport's Point of View to a Design Layer camera. So I'm bumping this topic for VW2021. New pop-up: This is the part from my original post that we need (#1): Confusingly the new pop-up in 2020 also uses the word "linked"... It definitely got my hopes up when I first saw it. 😁

This is still wonky in VW2020. I would love for something as basic as editing an extrude to work properly. 🙂

Bumping this topic for 2021. Sexy: Not sexy:

One remaining use is if you're working in your Design Layer and have a perspective view set up (for a rendering), you can turn on Cropped Perspective which will allow to zoom in without actually moving your point of view forward in space. So your composition and perspective amount stay the same but you can zoom in closer to objects to work on them. Note that when using RW cameras the crop boundary matches the aspect ratio and framing of the camera object, which can be useful (and in fact, I like it better than the weird blue corner rectangles of the camera object). Typically though you'll want Cropped Perspective turned off when in general working mode.

Is the "Image Effects" button checked in the OIP? That might be desaturating the image as a post-processing effect. Or perhaps it's related to this bug? Though I doubt it since you're talking about RW not OpenGL...

The one thing you can't do is link the intensity of that glow texture to the intensity of the light. (Right?) I believe the lens geometry always renders at the intensity of the Glow texture.

@Lec - this should be possible without unstyling the TBB, but you do need to set up your Style to allow for changes in sheet size. Specifically, you'd probably want to set the "Sheet Size" and Title Block "Scale Factor" parameters to "By Instance." (And maybe "Width" and "Height" to allow for custom sizes.) For further details about how that all works, take a look at this tutorial I wrote for Title Block Borders. Doing it this way allows you to keep the benefits of having your TBB be styled, but also allows for individual changes. Hope it helps 🙂

I also learned today that in Photoshop you can set a file to "Image<Mode<32 bits/Channel" - then when you go to Save As, you can now choose "Radiance" which will save out a .hdr file. Obviously it's not saving multiple exposure information like a true HDR, but it got me closer and it's now working in Vectorworks 👍

@Luis M Ruiz Can we please get more details on this? I need to be able to make custom RW backgrounds of locations that we've photographed. It used to be easy, now I keep getting yellow backgrounds... Urgh.

I've seen this bug as well, particularly with cameras that are linked to / within a viewport. Didn't catch it immediately, and it really screwed me over when working with a director while we were trying to figure out camera lenses and placement for a show. Viewports would randomly switch from our custom FOV back to 59° without notice.

Bumping this topic for 2021...... This is an example of an inconsistency in Vectorworks which would be a small but very helpful fix. This should have the Resource Manager style pop-up to match the way the rest of the program currently works.

I've actually noticed a similar thing in VW2020 - 3D objects created with a Line as the source object end up not having the ability to change their fill type. This is different than previous versions, and I would consider it a bug. For example, draw a line and extrude it upwards. The extrude is stuck to having no fill. It makes sense for the line to not be able to have a fill, but the resulting extrude should be able to. Same goes for your sweep object. As a workaround for now, you can use the little triangle flyout at the bottom of the attributes palette, and choose "Make All Attributes by Class" (since the None class has a solid fill type). This seems to make it work, even though the Attributes Palette still displays a little wonky.