 |
Planned to start working on this after 3.2.4 and first studio alpha. We added support for Variable Fonts in 3.2.4, this is next. |
 |
The Slug Algorithm has gone public! What do you think about its use? |
|
|
It is a very good algorithm, but only for static vectors and requires a preprocessing step |
|
|
Just a clarification to my previous comment: Slug requires significant preprocessing of bands and bounding boxes, which is not very compatible with dynamic geometry. I haven’t experimented with it yet, but I plan to do so soon. My impression, however, is that this will be quite CPU-intensive. If we don’t precompute the bands, it will likely become very GPU-intensive instead. I understand that text is static, but we’re aiming for a solution that unifies everything—static paths, dynamic paths, and text—under the same technology. We’ve been working on this new architecture for quite some time. That said, we could definitely add support for the .slug format and use it alongside TTF. |
 |
I agree with Demond, when I made this post back in Jan 2024, MSDF was the best solution but that simply isn't the case anymore, Slug is. Yes it needs to be pre-computed, but I think this small tradeoff is worth getting resolution independent text and paths for users that need it. Slug isn't the solution for everything, so I don't think anyone expects it replace the new/current architecture but it seems it should be able to co-exist with it. |
|
|
We are working on this. Noesis 4.0 was focused on API stability to make the adoption of Noesis Studio easier. The next big thing is our new renderer: fully GPU-based, with pixel-perfect rendering in both 2D and 3D. Super excited about this, although it will take some time before it officially appears. |
- Anonymous
