Sign in to follow this  
Joshua Lamusga

Some zoom levels display alpha as "extra opaque"

Recommended Posts

Specs

Paint.net version 4.0.19 running on Windows 10 64-bit Home edition

 

Problem

Transparency of all pixels in paint.net's canvas is sometimes displayed at a higher opacity than the actual opacity of the image. This occurs intermittently at random when changing the zoom level, and no particular zoom percentage always displays this bug. If you take actions on the image, the transparency reverts to normal. Rectangle select refreshes the pixels under the rectangle you draw so those pixels display as normal. This leads me to believe this is a redrawing problem.

 

Steps to Reproduce

1) Open paint.net.

2) Set the primary color to black at 121 alpha. That's what I tested at.

3) Use the fill bucket to fill the screen with that color.

4) Zoom in and out until the bug occurs.

Though this bug occurs randomly, it does so at high frequency, so only a couple times zooming in and out should do it. You don't need to zoom to max or min.

 

Examples

Glitch.png.58878046ea235eea368531dd5666a7a9.png

Glitch2.png.12bfdc26eea7025a7c40680ca7d49088.png

Edited by Joshua Lamusga

Share this post


Link to post
Share on other sites

I've known of this issue for quite awhile but haven't taken the time to investigate it yet. It's been around since 4.0 (mid-2014).

 

This seems like a good time to debug this -- I've been fixing a whole bunch of little leftover bugs for the 4.0.20 update :) Thanks for the writeup!

Share this post


Link to post
Share on other sites

Sure thing Rick. To be honest, I've known about it since early 2016, but I didn't post about it until just now. Like that other bug I submitted and said I knew about for three years :). Hopefully I remember to post more often when I encounter these little inconsistencies.

Edited by Joshua Lamusga

Share this post


Link to post
Share on other sites

The double ("dark") alpha is fixed for the upcoming 4.1.2 release :) I had to write some custom pixel shaders but they were pretty easy (the rest of the code to integrate it was more problematic...)

 

It's now possible for me to have fixed this because of the upgrade to Direct2D 1.1 that I did for the Paint.NET 4.1 release (see also: https://blog.getpaint.net/2018/04/01/paint-net-4-0-22-and-windows-7-platform-update/ ).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this