You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I can see, it looks like ofxFontThreeDee or the ofx demo has a different focus compared to ofxFontSampler, which centers more on sampling glyphs to manipulate / recreate their individual mesh rather than applying 3D extrusion on a string or glyph.
I mean bc you have used some third-party libs
Just to clarify, there’s no third-party library involved except for the ofxTriangleMesh addon used by the demo, libfontsampler is self-contained and doesn’t rely on other libraries so you might extend it as needed or create bindings for other frameworks.
Regarding the issue you might be correct. The library was initially restricted to handling type 4 CMAP TTF files, but there could be some missing edge cases. Do you still have access to the problematic TTF file? It would help to investigate further.
Hey @tcoppex ,
Do you still use this addon?
I am getting this error at \ofxFontSampler\libs\fontsampler\ttf_reader.cc:
it seems that detect some error in the ttf files...
There's a new OF example that could be a replacement to your addon, but I suspect that it could be more performant or better to use your addon. maybe? I mean bc you have used some third-party libs...
https://github.com/openframeworks/openFrameworks/tree/master/examples/3d/pathsToMeshesExample
I have seen also this alternative:
https://github.com/moebiussurfing/ofxFontThreeDee
The text was updated successfully, but these errors were encountered: