About my stuff
Introduction I am working on the Asset-Importer-Lib since 2006. At first, we were three guys who wanted to share their file-loaders in one library with others. If you have ever tried to import any kind of 3Dfile–format you know how much work, frustration, and pain this will cause. A lot of hacks and special implementations…
In this blog-post I want to explain a simple strategy how to optimize your performance when you want to render a 3d-model imported by the Asset-Importer-Lib ( see https://assimp.org/ ). When you have imported your asset by using the Asset-Importer-Lib the data-structure stored in the plain c-struct aiScene contains different data: The vertex-data like positions,…
For all who are interested in the language ports of Asset-Importer-Lib: I opened a poll which language binding will be preferred. So if you want to vote as well, feel free to participate our poll at: The Assimp language binding Poll
If you want to support my Asset-Importer-Work: here is my Patreon-Profile for the assimp-library: https://www.patreon.com/assimp I cannot promise that I will be able to work on Assimp all day. But for funding will help me to improve the underlying infrastructure like the webspace or some new hardware.
The problem: Think of the following situation: you want to import a model using Asset-Importer-Lib and store some values like the version of the current asset or the author / company. Or when you want to manage the models using modules for a much more efficient way for your SCM you need to store grouping…