Box2d Revisited
j15r.com
Box2d Revisited
1–10 of 44 posts
Re: Box2d Revisited
#2http://farseerphysics.codeplex.com/
:(
Re: Box2d Revisited
#3Not too useful as does not include one of the very popular ports and an additional major platform: http://farseerphysics.codeplex.com/ :(
Re: Box2d Revisited
#4Not too useful as does not include one of the very popular ports and an additional major platform: http://farseerphysics.codeplex.com/ :(
Re: Box2d Revisited
#5Not too useful as does not include one of the very popular ports and an additional major platform: http://farseerphysics.codeplex.com/ :(
I don't get this comment. This is about performance in browsers, not different physics engines...?!
Re: Box2d Revisited
#6Re: Box2d Revisited
#7Not too useful as does not include one of the very popular ports and an additional major platform: http://farseerphysics.codeplex.com/ :(
I must admit to being unfamiliar with Farseer, but if you feel like submitting a pull request, I'll figure out a way to run it on my Mac (I presume the "platform" you're referring to is .NET, or perhaps WinMo).
Re: Box2d Revisited
#8Re: Box2d Revisited
#9I can't zoom on this page with my phone and, due to that, can't read it at all except with the "Reader" function.
Re: Box2d Revisited
#10I'm curious whether the performance varies if you used a C compiler from the last five years -- GCC 4.2.1 was released in July 2007. (I'm not claimed the author of the post is unfairly biasing the results, I'm just honestly curious.)
gcc 4.6.3: 3.554688 +/- 4.786550
clang trunk: 3.593750 +/- 4.798172
Chrome: 41.03515625 +/- 9.331709130062185
Which puts Chrome at about 11x these native compilers, consistent with the blog post.