Skip to content

Chris

My feedback

2 results found

  1. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Chris commented  · 

    @Ton Thanks for trying to help. I think we can all agree that fixing the bug should be a priority for Adobe. Letting this bug exist for 7+ years is embarrassing.

    An error occurred while saving the comment
    Chris commented  · 

    @Egor I'm not looking for a workaround, I'm looking for the bug to corrected. I happen to be a computer graphics software developer myself. If your/Ton's explanation of Illustrator's rendering implementation is correct, then the rendering implementation itself is incorrect. Vector graphics should not be dependent on an underlying pixel grid. Instead, they are geometry that exist in 2D space and then the Illustrator window, the artboard, or an asset export are the viewport through which we view, sample, and rasterize them. If my viewport is an integer size of NxN and then I render it scaled at integer SxS, then the output dimensions will be integers NSxNS, not NS+1. It doesn't matter whether you super sample or not.

    Imagine applying your logic to 3D graphics where the viewport is defined by a camera and the output dimensions are defined by the frame size. Your bug is that as the camera moves the dimensions fluctuate every frame. Clearly, that's not correct.

    My expectation for a bug fix is that the output dimensions of an asset or artboard do not fluctuate based on coordinate position or anchor point, just based on their dimensions. Of course, assets or artboards with a decimal dimension (width or height) will round up 1 pixel.

    An error occurred while saving the comment
    Chris commented  · 

    @Egor Thank you! Yes, these artboard and asset export issues are basically the same problem. Also, for a little further context with my example, if that 5"x5" square is placed at (10.5", 10") then exported at 25 PPI, the resulting image is a rectangle of 125 x 126. It's not even a square anymore.

    It sounds like you understand the problem very well, but please let me know if there is any way I can be helpful to get this issue resolved. I'm happy to provide further files or additional information.

    Chris shared this idea  · 
  2. 168 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    This issue is probably happening because the artboard dimensions are not appropriate for raster export (i.e. are in decimals).
    If you make x and y values as the whole numbers in the transform panel (not in decimal), then the extra pixels will not be added to the exported image.

    That is the workaround, and it’s reported that it’s not always the case.

    At the same time — Ai knows the size of artboards to be exported and yet it does not deliver the set sizes, which is not fair. The team is going to rethink the algorithm.

    Chris supported this idea  · 

Feedback and Knowledge Base