-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editor is scaled with visible pixelation on macOS when using multiple monitors with different scaling factors #89019
Comments
If you set the Font Antialiasing editor setting to None as shown in the screenshot, it's expected that fonts will generally look bad. It only really looks good for very specific fonts designed for a specific size. |
I see the same results using any of the Font Aliasing settings. The screen
shot just happened to have that option selected, but that setting has no
discernable effect for me.
…On Thu, Feb 29, 2024 at 2:38 PM Hugo Locurcio ***@***.***> wrote:
If you set the *Font Antialiasing* editor setting to None as shown in the
screenshot, it's expected that fonts will generally look bad. It only
really looks good for very specific fonts designed for a specific size.
—
Reply to this email directly, view it on GitHub
<#89019 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG3PK6OJ6SVCM33GM42ZNELYV6WVTAVCNFSM6AAAAABEATFDSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSGA4TAOJZG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Kevin Bruner / President & CEO / Bruner House, LLC
e-mail: ***@***.***
phone: 415-419-6620 / [image: Twitter] <https://twitter.com/kevbru/>/ [image:
LinkedIn] <https://www.linkedin.com/in/kevin-bruner-59a329/>
web: www.brunerhouse.com
|
And the fonts DO render correctly much of the time. I am generally seeing
10-40 seconds of "good fonts" followed by 10-40 seconds of "bad fonts"
regardless of various settings. Seems like perhaps an order of operations
or stale state problem.
…On Thu, Feb 29, 2024 at 2:49 PM Kevin Bruner ***@***.***> wrote:
I see the same results using any of the Font Aliasing settings. The screen
shot just happened to have that option selected, but that setting has no
discernable effect for me.
On Thu, Feb 29, 2024 at 2:38 PM Hugo Locurcio ***@***.***>
wrote:
> If you set the *Font Antialiasing* editor setting to None as shown in
> the screenshot, it's expected that fonts will generally look bad. It only
> really looks good for very specific fonts designed for a specific size.
>
> —
> Reply to this email directly, view it on GitHub
> <#89019 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AG3PK6OJ6SVCM33GM42ZNELYV6WVTAVCNFSM6AAAAABEATFDSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSGA4TAOJZG4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
--
Kevin Bruner / President & CEO / Bruner House, LLC
e-mail: ***@***.***
phone: 415-419-6620 / [image: Twitter] <https://twitter.com/kevbru/>/ [image:
LinkedIn] <https://www.linkedin.com/in/kevin-bruner-59a329/>
web: www.brunerhouse.com
--
Kevin Bruner / President & CEO / Bruner House, LLC
e-mail: ***@***.***
phone: 415-419-6620 / [image: Twitter] <https://twitter.com/kevbru/>/ [image:
LinkedIn] <https://www.linkedin.com/in/kevin-bruner-59a329/>
web: www.brunerhouse.com
|
Can you reproduce this issue without an external display connected? |
No. On my laptop's built-in monitor everything seems to render properly.
The external display is a Dell UltraSharp 38 @ 3840 x 1600
The built in display is:
*Apple M3 Max:*
Chipset Model: Apple M3 Max
Type: GPU
Bus: Built-In
Total Number of Cores: 30
Vendor: Apple (0x106b)
Metal Support: Metal 3
Displays:
*Color LCD:*
Display Type: Built-in Liquid Retina XDR Display
Resolution: 3024 x 1964 Retina
Main Display: Yes
Mirror: Off
Online: Yes
Automatically Adjust Brightness: Yes
Connection Type: Internal
…On Thu, Feb 29, 2024 at 2:58 PM Hugo Locurcio ***@***.***> wrote:
Can you reproduce this issue without an external display connected?
—
Reply to this email directly, view it on GitHub
<#89019 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG3PK6IAACBA6DDXADUXGE3YV6ZC3AVCNFSM6AAAAABEATFDSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSGEYTKMBQGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Kevin Bruner / President & CEO / Bruner House, LLC
e-mail: ***@***.***
phone: 415-419-6620 / [image: Twitter] <https://twitter.com/kevbru/>/ [image:
LinkedIn] <https://www.linkedin.com/in/kevin-bruner-59a329/>
web: www.brunerhouse.com
|
This is likely due to the same cause as #61357. |
Does sound like it might be the same. I'll see if I can help out on the
issue. Thanks!
…On Thu, Feb 29, 2024 at 3:12 PM Hugo Locurcio ***@***.***> wrote:
This is likely due to the same cause as #61357
<#61357>.
—
Reply to this email directly, view it on GitHub
<#89019 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG3PK6KD2GLYGUMDZQIRMTLYV62VHAVCNFSM6AAAAABEATFDSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZSGEZDSMJQHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Kevin Bruner / President & CEO / Bruner House, LLC
e-mail: ***@***.***
phone: 415-419-6620 / [image: Twitter] <https://twitter.com/kevbru/>/ [image:
LinkedIn] <https://www.linkedin.com/in/kevin-bruner-59a329/>
web: www.brunerhouse.com
|
Reproduced by the user paul on the developer's chat. Maybe it could help? cc. @bruvzg |
I came here looking for a fix for this; M2 Air + Samsung 30" external monitor. I noticed that clicking between the text editor area and the output/debugger below it would flip the fonts from proper aliasing to bad aliasing. I thought I could screen record > gif this, but if you try and capture it, it doesn't flip back to normal. I tried Quicktime, no dice it just looks bad all the time, and if OBS is running it won't flip back and forth at all (recording or not). So whatever is hooking into the screen to capture frames prevents it from going back to normal. edit: setting Editor Settings > Interface / Editor / Update Continuously = True seems to quash the bad aliasing. |
Am the quickest fix for this is to close the lid on the Mac which eliminates the “two monitors at different resolutions” situation, which appears to be the root of the problem. Sent from my iPhoneOn May 2, 2024, at 8:02 PM, noeldodd ***@***.***> wrote:
I came here looking for a fix for this; M2 Air + Samsung 30" external monitor.
I noticed that clicking between the text editor area and the output/debugger below it would flip the fonts from proper aliasing to bad aliasing. I thought I could screen record > gif this, but if you try and capture it, it doesn't flip back to normal.
I tried Quicktime, no dice it just looks bad all the time, and if OBS is running it won't flip back and forth at all (recording or not).
So whatever is hooking into the screen to capture frames prevents it from going back to normal.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
+1 (v4.3.beta.custom_build [705b7a0]) on macOS Sonoma 14.2.1. When the main UI window is interacted with, the pixelation goes away for a moment, but when it's idle, it returns to shoddy. As luck would not have it, this doesn't occur when recording the screen with QT (it remains terrible all the time), so please enjoy a phone video of a screen (possibly the only time in history doing that is a good idea for a bug report...). a.mp4
|
I'm experiencing the same issue since moving from Godot 4.2 to 4.3 beta 2. It might seem like a small issue, but the crunchiness flickers between levels of distortion and certain symbols become difficult to read. A few hours of coding like this gets very frustrating. This issue is not present in 4.2. I use an M2 MacBook Pro. The only way to use multiple monitors with the MacBook pro is to use DisplayLink and a hub to extend the displays. So I have my high DPI MacBook Pro screen and then two 1080p Dell monitors. The crunchy text issues occur only on the extended Dell monitors. Setting the editor to update continuously does not resolve the problem. I hope someone can figure out what broke the text rendering on Macs. |
You could look into bisecting the regression to precisely determine which commit caused the issue. I can't reproduce this on my end and it seems other users can reproduce the issue on both 4.2 and 4.3, so you would need to be the one bisecting the regression. |
I'll try bisecting the regression in the next few days as soon as I find the time. In version |
FYI. The Also there's some warning and error when running the local build (from source) in CLI:
Running the official build from CLI does not show the above error:
For dev4 official build, It seems that it also use OpenGL 4.1 Metal but the problem occurred.
For VulkanSDK, I tried both MacOS: Sonoma 14.5 |
I also couldn't compile a
https://docs.godotengine.org/en/latest/contributing/workflow/bisecting_regressions.html
V4.2 https://downloads.tuxfamily.org/godotengine/4.2/dev3/README.txt https://downloads.tuxfamily.org/godotengine/4.2/dev4/README.txt V4.3 |
Since this doesn't seem reproducible in custom builds, it's likely related to the toolchains we used for the official builds of 4.3.dev3 and 4.3.dev4. I updated all toolchains around that time, and based on what I wrote in godotengine/build-containers#138 (merged the day of the dev4 release, so I guess I used that version for it), the dev3 release still used the previous versions of the Xcode SDKs.
So this might be a change in behavior in the MacOSX SDK between 14.0 and 14.2. I'll try to make a build of the current |
Could you test this build which is the current master branch (25de53e) but built against MacOSX SDK 14.0? |
I also have issues with the otool check
current version |
The godot/platform/macos/display_server_macos.mm Lines 3487 to 3490 in 4ab8fb8
If I deactivate this calculation, then everything seems to be ok (on 4k and Full HD Display, Editor and Project) from PR: #56825. (not yet checked why exactly this change was necessary) Full HD and 4k Display
Only Full HD Display
|
can confirm that It worked 👍 Thanks! |
Tested versions
Reproducible in 4.2 and 4.3, MacOS 14.1.2 (23B2091), Apple M3 Max, external 3840x1600 display. Godot default settings.
System information
MacOS 14.1.2 (23B2091), Apple M3 Max, external 3840x1600 display.
Issue description
The editor will "flicker" (every second or two, not at a very high rate), between what is shown in the screen shot (poorly antialiased fonts) and properly rendered fonts. The "flickering" is not a constant rate, and seems to be impacted by moving windows, resizing, open/closing windows, etc. Generally changing the work Godot is doing in some way.
Steps to reproduce
This is happening continuously from opening the editor for me.
Minimal reproduction project (MRP)
no required.
The text was updated successfully, but these errors were encountered: