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

Font antialiasing value is not stored in scene #28537

Closed
p10tr3k opened this issue Apr 30, 2019 · 7 comments
Closed

Font antialiasing value is not stored in scene #28537

p10tr3k opened this issue Apr 30, 2019 · 7 comments

Comments

@p10tr3k
Copy link
Contributor

p10tr3k commented Apr 30, 2019

Godot version: 3.1.1

godotbugwithfontantialiasing

Also changing this value does not refreshes it state

@KoBeWi
Copy link
Member

KoBeWi commented May 23, 2019

Seems like Antialiasing/Hinting is a property of .ttf resource and there isn't any way to legitimately edit them (?).

@p10tr3k
Copy link
Contributor Author

p10tr3k commented May 23, 2019

I just want to notice that when I make font "dynamic" I was able to disable antialiasing

@volzhs
Copy link
Contributor

volzhs commented May 23, 2019

you mean on and off it while running game?

@Calinou
Copy link
Member

Calinou commented May 23, 2019

Seems like Antialiasing/Hinting is a property of .ttf resource and there isn't any way to legitimately edit them (?).

You can, but you will need to save the DynamicFontData resource (not DynamicFont!) to a .tres file. That file will only reference the TTF/OTF font file (and will be able to store metadata such as antialiasing and hinting settings), so it will remain VCS-friendly. This needs to be documented better somehow.

As for changes not being displayed immediately in the 2D view, this is already reported in #27106. As a workaround, you can change an unrelated parameter in DynamicFont to cause the font to refresh.

@KoBeWi
Copy link
Member

KoBeWi commented May 23, 2019

You can, but you will need to save the DynamicFontData resource (not DynamicFont!) to a .tres file.

Wow, this is possible? IMO it should be some import option. It's obscure, inconsistent with every other resource (like, it stores path to .ttf file inside .tres, even if technically it's the same resource) and doesn't make sense :/

@akien-mga akien-mga changed the title Font antyaliasing value is not stored in scene Font antialiasing value is not stored in scene Oct 28, 2019
@akien-mga
Copy link
Member

As for changes not being displayed immediately in the 2D view, this is already reported in #27106. As a workaround, you can change an unrelated parameter in DynamicFont to cause the font to refresh.

The "bug" part is thus a duplicate of #27106.

Keeping the issue for the other UX issue with DynamicFont/DynamicFontData.

@Calinou
Copy link
Member

Calinou commented Mar 16, 2021

Duplicate of #25626.

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

6 participants