PVA - Admin

That is odd, I had thought something looked different with viewports since 2013 but hadn't noticed this specific change. I don't know of any specific reason this would have been done, since it doesn't seem to affect the snapping to annotations or other geometry any differently. Submitting now. If it turns out there was a reason for this change and it was intentional I'll post it as well.

Unfortunately I am fairly certain this is controlled by the operating system directly. Vectorworks can not control it on its own, since the most granular you can make this control on Mac is via the extension, which has been .VWX for all versions since 2008. I will submit this wish but I believe it is not possible outside of something implemented by Microsoft/Apple. However a trick you can use to see what version of Vectorworks a file was made in (iof you need this info in the future) is to open it in TextEdit or Notepad, it will tell you the version/build it was made in originally and the last version it was saved in as well, near the top.

Send that file in to tech@vectorworks.net with "ATTN Jim" as the subject and I can have a look. Mark which sheet layer I should be looking at if there are many, please.

Is it just the scale of the viewport that was altered, or in the Advanced Properties in the viewport Object Info, has the Text Scaling been changed as well?

What font specifically? Could you send me that font in an email? I can test it here and see specifically what needs to be changed and also if the main problem is the Adobe conversion to PDF or just the overall font handling. I'd agree with you flat out, but a lot of the time the custom fonts users tend to run into problems with are older (even older than 10 years) which is the cause of the issue and updating to a new version of that font (it sounds dumb, but its really a thing. They look identical but are built differently. ie PostScript, TrueType, OpenType.) can resolve it as well.

Submitted.

Next-click placement option for the Create Image Prop command. Submitting now.

I like that, a 3D align-and-rotate-and-scale-by-points. I'll take a closer look and submit.

OH duh, I get you. Measure once for old distance, then the same click-click measurement interface to set the two points for the new distance. That makes perfect sense. I need coffee. Submitting now. Well... after I get coffee.

What is the DPI of the sheet layers these viewports reside on? If you render in Final Quality Renderworks instead, are the results comparable and still worse on the reference, or do they more closely match in quality? Do you see the same quality issues when rendering in OpenGL with detail set to Very High? If you reference that same file into a new blank file, create the viewport and render, does it suffer from the same loss in quality?

I don't see what you mean yet, to clarify: Currently scaling with Symmetric by Distance has you measure the current distance, then enter the desired new value, (which I was considering the "new distance") So the user both knows what it is going to be and has control over it. Where is it that you would want to measure the new distance differently than that?

The tooltips absolutely need some serious polish. I'll have a 101 series out "soon?" :whistle: on Vectorworks Service Select that will cover the Renderworks shaders in great detail. They're very cool once you know how to use them, but with so much esoteric terminology in the Renderworks Texture dialogue box it takes a lot of explaining.

This is how I hear most users end up working with the Seating Layout object, using it as a more detailed method of Duplicate Array than anything else. I'll extract the individual wishes here, please let me know if I miss a key item: 1) Controllable numbering on-page per seat. 2) Custom geometry/Path object to determine the shape of a row. 3) Ability to remove and add single seats at a user-defined location. 4) Automated worksheet per-seating layout as well as an overall schedule. Especially the ability to read out how many seats are in each specific row. 5) Controllable Z height per row. 6) User-customizable location via the symbol geometry for measuring row-to-row. Currently it assumes the center of the symbol which is not always (or perhaps ever) correct.

Could you post a few sample images comparing the rendering in the source file to the rendering when referenced? It shouldn't be reducing quality simply because its referenced in, most likely this is a setting in the file or with a specific viewport we can correct.

It would still apply, yes, Python was added as another language supported for scripting rather than a replacement for Vectorscript. I have not heard of plans to remove the original language at all. However as far as which language to start with from scratch, most likely the newer language would make the most sense.

There are a few available here as well: http://resources.maxwellrender.com/search.php#page=1&mode=1&id=2107&search=vinyl&v1=0&v2=0&tipo=

Maybe, it might make recognizing different palettes easier/quicker, however then they may need to add color control to the text of palettes as well to keep things visible. There was a wish I saw awhile ago for a "Dark" mode for Vectorworks, making it look more like C4D or an AutoDesk product, but I am not sure what became of it.

What specifically are you having problems with or looking to accomplish other than with animations? (Which definitely need a revamp.)

Post that test file here and I can take a look. There are a few spots that are easy to overlook when working with overrides.

I see the same issues you describe with your door, but upon adding a new one it does not behave the same way. Have you updated to SP2 yet? (thats the one i'm using at the moment) I know a lot of users have opted to skip it for other reasons.

I mean, you shouldn't use those classes for the transom. Those classes should be left to the objects that auto-assign to them and not have additional objects added to them later, but I will test that with your file as well.

Request submitted.

That wish is in as well for the rest of the rendering modes.

There are a number of wishes to give this control to users at the moment, since you can not control them directly yet, unfortunately.

I do not get that same behavior here, (but if it were I would say it was broken.) Could you please post that window in a VWX file? I'll test it on my machines.