Timeline for Open model file format that supports skeletal animation
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3 at 18:33 | answer | added | Theraot | timeline score: 3 | |
| Jul 31 at 3:19 | comment | added | DMGregory♦ | I think you're making this much more complicated than it needs to be. No one will buy your proprietary file format when open standards exist, so don't let ideas about selling your format complicate your plans. There are no particular legal hurdles you're likely to encounter when writing down numbers in a file in whatever arrangement you feel like, as long as you're not directly copying some patented format. Make your own decisions and you're in the clear. For what you describe, you don't need an existing format to fork or build on - you can just make up whatever feels good to you. | |
| Jul 31 at 2:41 | comment | added | Opengraphicspros12 | I was looking for a free to use this way format though so I could possibly sell it too. Maybe theres an ancient file type constructed this way legally that I can fork or rebuild. | |
| Jul 31 at 2:39 | comment | added | Opengraphicspros12 | Well it would be cool to use it in an alpha or beta version of a game while I work on it. Im not sure if its legal to make a plugin for blender, it might take building a new object editor. If you know if its legal to invent the format but use blenders bones id like to know, or if anyone else does. I want to export a obj file as a vertex containing file with keyframes from blender using blenders bones. Ill also be using the weights that blender has with their bones to know how much movement a triangles or quads vertex gets from a motion. | |
| Jul 31 at 2:20 | comment | added | DMGregory♦ | If you're interested in making your own file format, then why not just make your own file format? What functionality do you need from your format that glTF / Collada do not provide? And if they're lacking in this way, why would you want to use them as a basis rather than just making your new format from scratch, custom-fitted to your needs, as games very often do? Since you're making incompatible changes, using a standard format for interoperability is no longer an advantage anyway, so what's making you want to tie your custom format to something existing? | |
| Jul 31 at 2:15 | comment | added | Opengraphicspros12 | If you edit the file format to make your own format you probably have to give them trademark exposure by shareing their license that you cant modify. Like if I wanted to edit either glTF or collada inyo a new file type and distribute it as my own software and make it open source I can't because they have their trademarks and licensing that cant be modified if redistributed. They do this to keep the file format free but they dont let you edit theirs into your own version either. | |
| Jul 31 at 2:05 | comment | added | DMGregory♦ | What do you mean by "distribute their work"? If you implement the spec in a save/load routine that's your own code, it's your work, not theirs. Their trademarks are things like the word "Kronos", so as long as that's not shown in your game, you're not using their trademark. What specific action are you worried would exceed these licence terms? Is it maybe the case that you're not just looking for a format, but you want a library: someone else's code that already implements the spec for you? Using a library often brings additional licensing requirements, even if the format itself is free. | |
| Jul 31 at 1:51 | comment | added | Opengraphicspros12 | You have to use their trademark if you distribute their work | |
| Jul 31 at 1:30 | comment | added | DMGregory♦ | What specific licence restriction do you find unpalatable with glTF or Collada? glTF allows you to "use and reproduce the unmodified specification for any purpose, without fee or royalty". Collada allows "usage in commercial and noncommercial applications, without restrictions". It's only use of their trademarks that demands an additional agreement - so if you were making a 3DCC tool with a menu option labelled "Save as Kronos glTF", you'd need to jump through an extra hoop for that. Just implementing the spec yourself to read a file does not require any extra credits. So, what's the issue? | |
| Jul 31 at 1:24 | history | reopened | DMGregory♦ | ||
| Jul 31 at 1:13 | history | edited | DMGregory♦ | CC BY-SA 4.0 | Clarifying |
| Jul 31 at 1:07 | history | edited | Opengraphicspros12 | CC BY-SA 4.0 | edited title |
| S Jul 31 at 0:57 | review | Reopen votes | |||
| Jul 31 at 1:27 | |||||
| S Jul 31 at 0:57 | history | edited | Opengraphicspros12 | CC BY-SA 4.0 | added 173 characters in body Added to review |
| Jul 31 at 0:34 | history | closed | DMGregory♦ | Needs more focus | |
| Jul 30 at 23:59 | history | asked | Opengraphicspros12 | CC BY-SA 4.0 |