Text illegible on non-Retina display when using Rasterization options/non-HD fonts #502

New Issue

2019-01-31T18:57:47+01:00

kellylawrence commented

2019-01-31 18:57:47 +01:00

(Migrated from github.com)

I seem to be experiencing a strange visual bug on my current setup, where text is illegible when using the Rasterization options (Scanlines or Pixels) and non-HD fonts on non-Retina displays.

My current setup is as follows:

cool-retro-term v1.1.1
15-inch Retina MacBook Pro
Intel Iris Pro 1536 MB Graphics
Dual 1080p external monitors

On the main MacBook display, I can use a default theme like Vintage/IBM DOS, and things look perfectly fine, as seen in the image below:

However, if I move/open the cool-retro-term window to one of my external displays, the text becomes illegible, and can only become legible if I turn off the Rasterization options and change to an HD font. (Ex: HD: Hermit (Modern)).

Is it possible I'm just missing a setting, or maybe don't have access to the correct fonts?

I seem to be experiencing a strange visual bug on my current setup, where text is illegible when using the Rasterization options (Scanlines or Pixels) and non-HD fonts on non-Retina displays. My current setup is as follows: cool-retro-term v1.1.1 15-inch Retina MacBook Pro Intel Iris Pro 1536 MB Graphics Dual 1080p external monitors On the main MacBook display, I can use a default theme like Vintage/IBM DOS, and things look perfectly fine, as seen in the image below: <img width="1552" alt="screen shot 2019-01-31 at 1 45 04 pm" src="https://user-images.githubusercontent.com/815248/52074018-47e7b880-255f-11e9-8e15-a8d0289e7c3d.png"> However, if I move/open the cool-retro-term window to one of my external displays, the text becomes illegible, and can only become legible if I turn off the Rasterization options and change to an HD font. (Ex: `HD: Hermit (Modern)`). ![screen shot 2019-01-31 at 1 45 31 pm](https://user-images.githubusercontent.com/815248/52074240-d2301c80-255f-11e9-897f-e22d1620628b.png) Is it possible I'm just missing a setting, or maybe don't have access to the correct fonts?

👍 8

Swordfish90 commented

2019-02-02 18:35:12 +01:00

(Migrated from github.com)

Hi @kellylawrence ... I'm sorry, but I think this is an issue caused by the different scaling factors of the different monitors. It's a bug, and the only workaround that comes to my mind is disabling retina scaling for CRT.

👍 4

kellylawrence commented

2019-02-04 15:44:57 +01:00

(Migrated from github.com)

No worries! It's more of a novelty things, so I'm not really impacted by the bug. Just thought maybe I was doing something wrong on my end.

At least it's a known issue, and setting the "Open in Low Resolution" option via the Get Info window for the app seemed to solve the problem. (At least in the sense that text is now legible on all displays).

No worries! It's more of a novelty things, so I'm not really impacted by the bug. Just thought maybe I was doing something wrong on my end. At least it's a known issue, and setting the "Open in Low Resolution" option via the Get Info window for the app seemed to solve the problem. (At least in the sense that text is now legible on all displays).

miketweaver commented

2019-02-07 21:15:36 +01:00

(Migrated from github.com)

I have the same issue, "Open in Low Resolution" fixed it for me as well:

I have the same issue, "Open in Low Resolution" fixed it for me as well: ![image](https://user-images.githubusercontent.com/5581855/52440066-68bd8a00-2ada-11e9-8dcf-b50251e70a0b.png) ![image](https://user-images.githubusercontent.com/5581855/52440031-55122380-2ada-11e9-97dc-4be2229c3dd0.png)

👍 14

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#502