<div dir="ltr"><a href="https://www.youtube.com/watch?v=OxlU5_beolw">https://www.youtube.com/watch?v=OxlU5_beolw</a><br><div><br></div><div>Forgot to add link to my work!</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 17, 2014 at 8:57 AM, Jacob Merrill <span dir="ltr"><<a href="mailto:blueprintrandom1@gmail.com" target="_blank">blueprintrandom1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Why not work on the bge?<div><br></div><div>with the exception of screen space normals, and efficient draw call batching, I don't see any fatal flaws with it,</div><div><br></div><div>What is stopping it from being great? it's not GPL, as far as I can tell, as most game developers are not writing anything that has not been done before, and if they are, it's not like someone can't copy the idea without access to the code.....</div><div><br></div><div>here is my own work in the engine, (almost alone at this point)</div><div>this is a walking ragdoll, that supports both ik animation, and physical scene interaction,</div><div>when bullet 3 hits the main stage as people upgrade video cards, you should in theory be able to run 100's of walking ragdolls.</div><div><br></div><div>why not a open project?</div><div>(I am biased) but my own project looks pretty good :D</div><div><br></div><div>I have worked for a year on this for free.....:P</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 17, 2014 at 8:01 AM, Toni Alatalo <span dir="ltr"><<a href="mailto:toni@playsign.net" target="_blank">toni@playsign.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">could Assimp help here? it has an internal format, and can read &<br>
write many formats to / from it. i don't know the format / internal<br>
structure but have understood that it's simple and straightforward and<br>
suitable for games.<br>
<br>
afaik they have a json format now but are interested in a binary<br>
format as well. i've used the json format succesfully with three.js in<br>
a test (converted from fbx to assimp2json)<br>
<br>
regarding Collada, glTF may address some of the problems by being a<br>
more restricted spec and by having an efficient binary format for the<br>
geom arrays (and json for other stuff, no xml). it might be even nice<br>
to just write glTF directly from Blender if the current solution of<br>
going via collada2gltf is problematic. at least those Khronos<br>
standards have open specs..<br>
<br>
2cently yours,<br>
~Toni<br>
<div><div><br>
On Wed, Sep 17, 2014 at 4:53 PM, Sam Brubaker <<a href="mailto:sam@worldsday.org" target="_blank">sam@worldsday.org</a>> wrote:<br>
> @JCS, I really like your ideas here, but I still wonder if a "15th Standard"<br>
> might be more strategically sound, even if it's totally insane.<br>
><br>
> My biggest concern about spending so many resources on FBX is that B-devs<br>
> would be working on something that does not belong to Blender or any<br>
> equivalent NFP organization. It belongs to Autodesk. Autodesk is free to<br>
> break its own format however it likes and nullify all the work we do<br>
> catching up, which is kind of scary. All FBX development on our end<br>
> indirectly helps a company that is not helping us at all.<br>
><br>
> Of course, our goal should be utility for users, not vindictiveness;<br>
> improving FBX support may be our best move in the short term. But what about<br>
> the long term?<br>
><br>
> On Wed, Sep 17, 2014 at 7:38 AM, Jens Christian Restemeier<br>
> <<a href="mailto:jens.restemeier@gmail.com" target="_blank">jens.restemeier@gmail.com</a>> wrote:<br>
>><br>
>> Another thought:<br>
>> What about porting Blender's FBX code into a clean C++ library, without<br>
>> dependencies on Blender or the official SDK? Blender could then use it<br>
>> through some Python bindings.<br>
>> Basically just a loader/writer, and a high level interface to go through<br>
>> the scenegraph or to build a scene graph. With an MIT or BSD style license<br>
>> to encourage people to use it over the official SDK.<br>
>><br>
>> That we we have guaranteed interoperability with anyone using the library,<br>
>> and improvements benefit both Blender and applications using it.<br>
>> And it would open a way to sneak in a better format at a later point. You<br>
>> could define a clean legacy-free format, and any application that uses the<br>
>> API just needs a recompile to use it.<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Bf-gamedev mailing list<br>
>> <a href="mailto:Bf-gamedev@blender.org" target="_blank">Bf-gamedev@blender.org</a><br>
>> <a href="http://lists.blender.org/mailman/listinfo/bf-gamedev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-gamedev</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> Bf-gamedev mailing list<br>
> <a href="mailto:Bf-gamedev@blender.org" target="_blank">Bf-gamedev@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-gamedev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-gamedev</a><br>
><br>
_______________________________________________<br>
Bf-gamedev mailing list<br>
<a href="mailto:Bf-gamedev@blender.org" target="_blank">Bf-gamedev@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-gamedev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-gamedev</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>