<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi, I’m a software developer (never contributed to blender) motivated (possibly?) to implement USD export support for one of Apple’s schema additions, namely Preliminary_Text: <a href="https://developer.apple.com/documentation/arkit/usdz_schemas_for_ar/preliminary_text" class="">https://developer.apple.com/documentation/arkit/usdz_schemas_for_ar/preliminary_text</a><div class=""><br class=""></div><div class="">My motivation is to allow a designer to create a USD file with text that contains the text <i class="">attributes</i>, not the final mesh (though I supposed it could do both). This would allow software to pull the attributes from the USD file at runtime, including xForm, material, font-family, etc., and use these attributes to render dynamic text at runtime with the same text <i class="">attributes</i> the designer intended. Think 3D user interface where text may change based on a view model.</div><div class=""><br class=""></div><div class="">Apple is thinking along these lines but, after diving into their tools, there seems to be more concept than implementation. They are pushing Reality Composer but I find it more a broken toy than a tool, so I am turning to blender.</div><div class=""><br class=""></div><div class="">Thoughts? Questions?</div><div class=""><br class=""></div><div class="">Best,</div><div class="">John Harrison</div></body></html>