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

Procedural Text without generating new textures? #25

Open
KTRosenberg opened this issue Apr 17, 2021 · 0 comments
Open

Procedural Text without generating new textures? #25

KTRosenberg opened this issue Apr 17, 2021 · 0 comments

Comments

@KTRosenberg
Copy link

I need to render text procedurally in every frame of my application’s runtime. It seems that nanovg generates a new atlas every time I have a new text line or zoom. That causes major performance and memory issues. Is there a way to circumvent this?
Also, I did look into the original nvg headers, but it’s unclear when the redundant texture generation happens. I always thought for procedural text you’d just render a quad per character in the correct space, not generate a bitmap and texture per text line.

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

No branches or pull requests

1 participant