Hi there,
This issue still seems to be present in Designer, both on screen as well as in the final output images, which is creating a major problem for me.
Does anyone know if a solution has been developed for this problem yet?
If not, I'd like to propose a couple of solutions that should address the issue:
Solution 1: When the user is exporting an image, allow them to specify a level of multisampling (i.e. 1x, 2x, 4x, 8x, etc). For instance, selecting 2x would internally produce an image 4 times as large as the one specified by the user, and then downscale it before writing it to the file. 4x would internally produce an image 16 times as large. This is something us users can do manually ourselves, but it adds a bunch of extra steps, so it would be nice if it was a build in feature. The disadvantage of this approach is that it only reduces the appearance of the seams, but does not eliminate them. I’ve attached 2 images to demonstrate the level of improvement of using x4 multisampling.
Solution 2: Have the program skip performing antialiasing on vector components entirely (bear with me) as it produces the output image, thus (presumably) eliminating the seams entirely. Then, as an alternate way to provide antialiasing, allow the user to specify a multisampling level (2x, 4x, 8x, etc) to use during the export process. This way a much larger image would again be produced internally, which would then be downscaled to the size the user requested before it gets written to disk. This should have the advantage of completely eliminating the seams discussed in this thread, while maintaining a decent level of antialiasing, which the user would control via the multisample level.
I think Solution 2 is a much better way to go, if it's possible to do it that way. You might even be able to apply solution 2 in real time to eliminate seams while we use the application.
If you have any questions about these ideas please let me know.