Andy Broomell

Also for what it's worth, I think it's incredibly dumb that the default quality that users are presented with when viewing 3D models is "Low." It looks AWFUL and makes Vectorworks look unprofessional. With the state of modern computers and graphic cards, this default should absolutely be changed to "High," or at the very least "Medium." In 2020 I filed a request for this to be updated: VE-101264

The Shaded settings also get saved into Saved Views, so if you run a Saved View after you've changed this setting, that may be the cause of it 'resetting.'

@Kevin McAllister – I just noticed this behavior in 2023 as well: ViewportPosition_2023Bug.mov I filed a bug report: VB-191056

If this happens in the future, is there anything we can do in Vectorworks to help "catch" the issue before restarting the program? Some sort of log that an engineer could view and perhaps start to deduce what steps had lead to the issue?

@JuanP - I wonder if my VB-188809 might be related to this as well (it's marked as resolved, but is about EAPs not displaying section fills).

I’ve seen this a number of times over the last several years, and like mentioned above it’s always right after creating a new class. But occurrences are fairly rare and I’m not sure what other factors cause it to happen. Restarting seems to always fix. It’s definitely one class listed twice. I seem to remember trying to delete one and both instances went away, indicating it’s a duplicate listing.

Not in that particular regard, no. But there are other useful lighting-related improvements, such as the ability for Shaded [OpenGL] render mode to display more than 8 lights, lit fog, and basic reflectivities.

I've seen similar issues intermittently with EAPs for years, so perhaps it's not new to 2023 (?). But if you have a file that reliably renders one way in 2022 and a different way in 2023, that can be incredibly helpful for the engineers to help track down what the source of the issue might be. Be sure to upload the file here and explain what you're seeing: https://www.vectorworks.net/support/bugsubmit

What's that? Ironically, you CAN reference Bitmap objects, but not images used in Textures. It certainly would be nice to be able to do this some day, but since that's a fairly significant change in base functionality, in the meantime I wish they would at least make it faster to switch out an image manually. Currently it takes a minimum of 9 clicks each time. As a suggestion: I wish we could right-click a Texture in the RM and have an option to "Replace Image in Color Shader" (which would only appear for textures that already have an image in the color shader). It would skip the pop-up asking whether we want to import an image or reuse an existing one, since 99.9% of the time we want to import a new one. Then we select an image, click OK, and bam it's done. This would reduce the process to four clicks (right click, Replace Image, select Image in finder window, click OK). There are days when I'm replacing images constantly, so while a reduction of 9 clicks to 5 clicks might seem inconsequential, that cascades into huge time (and wrist!) savings.

Agreed. I think all these menu items should be accessible while the Home Screen is active:

I'm realizing this is a different thread than where this was recently discussed in the Beta forum, but just so it's stated here as well... Now that 2023 has a Home Screen, this command should also clear out the recent files seen there. Particularly since the Home Screen displays thumbnails, this can be an issue when screen sharing versus trying to protect content protected under NDA. Some companies (D*sney/M*rvel for example) are very strict. Even file names could give away sensitive info...

Yes, this needs to be implemented.

When you say the viewports become outdated, do you mean that they simply get a red hatch border indicating they're out of date, or do you mean that the viewports become completely unrendered (display as wireframe)?

I've seen this happen when there was another wall that was T-joined at that spot, but was then deleted. I assume this is what happened in your case, but if continues happening unprovoked, let us know.

This is how I do it: (Yes these endless nested dialogs are horrible)

You can get solid raster edges in Shaded mode here: But Hidden Line vector edges, either solid or with dashes, can only be combined with Shaded mode when using Viewports as Evan describes.

Am I just not seeing it? It seems like being able to filter for objects with a certain fill type (e.g. Solid vs Hatch) would be a rudimentary criterion?

This wasn't fixed in a Service Pack for Windows? If that's the case then it's certainly a bug and needs to be addressed so that it matches the Mac behavior.

Where are you referring to when you say this? There should be a "None" option at the top of the marker list in the Attributes Palette, but let us know if that's missing for you. Otherwise, if you're talking about setting up Class attributes, there never was a None option for markers in this window. One thing to double check: before drawing objects, make you sure to deselect everything, then set markers to None in the Attributes Palette, then try drawing things. Does this affect what you're experiencing?

Yeah that tool sucks.

I agree that it would be awesome if Drawing Label auto-positioning could be determined in a more custom way. I always want the Y position to be a certain distance from the bottom of the viewport geometry's bounding box, so I always have to move and adjust the label from its default placement. The default seems to be around 1/2" below the geometry, but I typically want 5/8" or 3/4" below. And for the X position, I want the default placement for my labels to align all the way to the lefthand side of the bounding box of the viewport geometry, and for the label's control point to automatically extend to the righthand side of bounding box. For example: One reason why it's particularly annoying to do this manually is all the extra clicking into and out of Annotations that's involved, especially when I'm creating about 150 viewports / week. If these defaults could be user-adjusted it would really streamline things.

Seems to work okay for me in 2023. Have you tried a full restart of your computer just in case that mysteriously solves it? And does it happen in any file including starting a blank file?

If the viewport has a Renderworks Background then the viewport will be fully opaque and obscure other viewports. However if there is no RW background, then any blank area should be transparent... assuming the Viewport Fill is set to None and this checkbox is checked under the Viewport's Advanced Properties in the OIP:

Happens to me too. Sometimes restarting Vectorworks fixes it. Other times snaps just refuse to work predictably, mainly when editing within containers...

It does seem unexpected, doesn’t it?