When developing an asset system. In the context of wanting to develop my own model loading system to load different formats such as .obj, .fmx, etc from scratch because there are some bugs that I have found with assimp that has not been resolved. Another thing to note is this will most likely be done using modern C++ approach.What goes into a good model loading API, and in a professional sense how are they typically designed to handle generic types of model formats?What if I want them to also handle synchronizations, what problems can occur when wanting to handle synchronization when loading models? What internal details go into developing an API for loading models of generic formats?Here is an example of what I mean.If we have a backpack that is a .obj file, this is what I could see be done to load in that model. Where the idea would be using the adapter pattern to give us back the data for our asset.AssetObject* mesh = LoadModel("assets/backpack.obj");if(!mesh.IsLoaded()){ // Error Handling...}It would be great, if I could get some relatively some feedback on the different forms these kinds API's take, in reference to how others have designed theirs.
When developing an asset system. In the context of wanting to develop my own model loading system to load different formats such as .obj, .fmx, etc from scratch because there are some bugs that I have found with assimp that has not been resolved. Another thing to note is this will most likely be done using modern C++ approach.
What goes into a good model loading API, and in a professional sense how are they typically designed to handle generic types of model formats?
What if I want them to also handle synchronizations, what problems can occur when wanting to handle synchronization when loading models? What internal details go into developing an API for loading models of generic formats?
Here is an example of what I mean.
If we have a backpack that is a .obj file, this is what I could see be done to load in that model. Where the idea would be using the adapter pattern to give us back the data for our asset.
AssetObject* mesh = LoadModel("assets/backpack.obj");
if(!mesh.IsLoaded()){
// Error Handling...
}
It would be great, if I could get some relatively some feedback on the different forms these kinds API's take, in reference to how others have designed theirs.
Trending now
This is a popular solution!
Step by step
Solved in 2 steps
