See #6991.
When Webots is running at scaled resolutions, the framebuffer (see WbWrenWindow) is rendered at the pre-scaling resolution and then upscaled to fill the frame. This leads to low-quality "pixelated" graphics. We should render at the post-scaled resolution so that we can take full-advantage of HiDPi displays. As noted in the linked PR, however, the code currently appears to make little distinction between Qt's input coordinates and display coordinates, so some work will have to be done to dis-entangle them.
See #6991.
When Webots is running at scaled resolutions, the framebuffer (see
WbWrenWindow) is rendered at the pre-scaling resolution and then upscaled to fill the frame. This leads to low-quality "pixelated" graphics. We should render at the post-scaled resolution so that we can take full-advantage of HiDPi displays. As noted in the linked PR, however, the code currently appears to make little distinction between Qt's input coordinates and display coordinates, so some work will have to be done to dis-entangle them.