Skip to content
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

Pixelated Text when using Label #9444

Closed
JakeG-9191 opened this issue Mar 23, 2021 · 3 comments
Closed

Pixelated Text when using Label #9444

JakeG-9191 opened this issue Mar 23, 2021 · 3 comments

Comments

@JakeG-9191
Copy link

Issue: See the attached screenshot for example of issue that some team members are encountering, which are the dark pixels surrounding the label text. I have NOT been able to recreate this issue, but have been notified that multiple team members are encountering this issue both in development and in production. For some, it appears to be a consistent issue, for others, it is more random and only happens from time to time.

We are using a label to add fillColor as well as text to each of these objects, and the pixelation appears to be an issue no matter how near or far the user is zoomed. Any thoughts on what the issue is / some potential solutions are greatly appreciated.

Sandcastle example: N/A

Browser: Chrome 89.0.4389.90

Operating System: Mac OS | Big Sur 11.2.3

Screen Shot 2021-03-22 at 16 28 43

@dzungpng
Copy link
Contributor

dzungpng commented May 3, 2021

There is some discussion here regarding image scaling which you may find relevant: #7875.

In particular, setting viewer.resolutionScale = window.devicePixelRatio can help with the pixelation. I created an example here:
Sandcastle link.

Without viewer.resolutionScale = window.devicePixelRatio:
image

With the above set:
image

@lilleyse
Copy link
Contributor

lilleyse commented May 3, 2021

viewer.useBrowserRecommendedResolution = false is another way of telling CesiumJS to render at the screen's native resolution.

@ggetz
Copy link
Contributor

ggetz commented Nov 8, 2024

I think this is the same issue already documented in #4235. I'm going to close this issue to keep the discussion in one place. If you have any further input on this, please post it there instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants