Assimp for animations and commercial use

Started by
4 comments, last by bwhiting 9 years, 2 months ago

Is Assimp an acceptable library to use for commercial games (including animation models as well)? Does it stand with the standards, or should I implement my own (probably COLLADA) model assets import library?

Advertisement

A quick Google reveals that the assimp library is under the three clause bsd license.

This is perfectly compatible with commercial development, in fact some parts of windows were originally based on bsd licenced code, e.g. the ftp program etc.

I think attribution may be required though, e.g. a mention in your credits. You should double check, but you should be OK to use the code, statically or dynamically linked and even modify it without sharing your modified source.

The only real requirement of this license is that somewhere in your distribution, the copyright notice must be included. It doesn't have to be in the game itself, just in the documentation, or in a text file or something. If you distribute the source code, you must include a copy of the license, typically in a folder alongside all of the other licenses of software you've used, who require the same thing.

Thanks for your comments, but you didn't get my question. I know that I can use Assimp commercially, but I was asking if it's considered "okay".

Is it considered professional and fast enough for commercial games? Are there any games out there that use Assimp? Is it an acceptable library to use to animate models as well?

For commercial games, should I use Assimp or I better off implement my own library?

Typically you use a library like Assimp in your engine's tool-chain, to convert from interchange formats (stuff exported from your Artist's tools, which is designed to be flexible enough to be read by anything and contain every feature) into your engine's own model format, which is designed to be compact, load quickly, and support only the features required by your game.

So, both. Use Assimp to read from these interchange/export formats, and then write your own library that (one-way) converts data read by Assimp into your own format.

Was writing an little desktop app that does essentially hodgman describes not that long ago... must finish it.

Its a simple drag and drop import export, but the export is customized to what I want.

It is nice because by using assimp as the middle man, all the supported imports come out with the same structure.

(in my case, xml, json or binary)

A neat tool is assimp :)

This topic is closed to new replies.

Advertisement