Jump to content
  • 2
herbieherb

Always different number of pixels when rendering

Question

I made a somewhat strange discovery while developing my ExportImages script. It's that Vectorworks always produces differently sized images when rendering raster images. Most of the time, this only makes up a few pixels. But I still wonder why this is the case and if it can be prevented. For certain images, a pixel-exact export is necessary, if no changes should be visible during later layouts, e.g. in Indesign.

Here's the thread where we found the issue:

 

 

Edited by herbieherb
  • Like 3

Share this post


Link to post

7 answers to this question

Recommended Posts

  • 0

No change in 2021.

 

As far as I can remember, this has been an issue since the day I started using Vectorworks.

 

 

Edited by Andy Broomell
  • Like 2

Share this post


Link to post
  • 0

@Marissa Farrell you offered some help on @herbieherb's original thread about the image exporting script that this is related to. Are you able to offer any insight here?

 

This strange behaviour really causes some quite big problems when pixel-exact re-renders are needed. If there was any way around it, it would save a lot of pain.

  • Like 2

Share this post


Link to post
  • 0

For clarity, I think there are two distinct issues:

  1. Viewports often render pixels slightly different from one rendering pass to another, particularly around the perimeter of the viewport where the rendered pixels are offset slightly and inconsistently from the viewport's crop.
  2. Exporting the rendered pixels of a viewport is messy (i.e. impossible) as described in the thread linked above.
  • Like 1

Share this post


Link to post
  • 0
6 hours ago, Andy Broomell said:

For clarity, I think there are two distinct issues:

  1. Viewports often render pixels slightly different from one rendering pass to another, particularly around the perimeter of the viewport where the rendered pixels are offset slightly and inconsistently from the viewport's crop.

 

I've a feeling (would need to double check) that it's not just the pixels that change but somehow the underlying image will be very slightly compressed or stretched in the X or Y direction. In other words, you can't even resolve it by cropping the troublesome perimeter area out of the resultant bitmap.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...