Hello everyone
I want to share with you my experience (positive) with Gideros
these days I had an extensive testing in Gideros comparing it with other SDK (Coro*a and Mon*ey)
well ... here are my (personal) impressions ...
Coro*a VS Gideros ... Gideros is far better ... (speed of executables and other fronts ...)
Mon*ey VS Coro*a ...
Monkey is faster...
- I converted in Mon*ey a few Gideros examples such as "Jumping Balls" but with 500 balls ...
Gideros on my Galaxy S works fine
but on a Samsung S5570 and Samsung S5660 runs at 5-6 FPS
while in Mon*ey the same code (on Samsung S5570 and Samsung S5660) run at 20-30 FPS
Gideros produces an executable nearly 5Mb .... monkey 250Kb ...
and here Mon*ey wins ...
after that not satisfied I had converted the examples of physics .... and here Gideros win with incomparable results (on my Galaxy S runs perfectly)
the same code converted in Mon*ey (using box2d) run at 2-3FPS on My Galaxy S!!
GIDEROS GREAT!
what I lack in Gideros is a support to sprite collisions and a particle system... (directly in gideros-sdk that i think is written using NDK)
I tried to make a sprite collision system and a particle system, but is very slow ....
from what I saw when it writes a lot of code in LUA (without using built-in functions gideros) the speed of gideros drop down!!!!
Gideros-SDK is very fast but the language "LUA" is terrible! (or the lua VM used in Gideros is slow!)
What do you think?
PS: I remain, however, the idea that Gideros SDK is one of the best around ... if only you could fix these little things ...
now remains for me to convert my old game and test (seriously)
The overall speed of Gideros ...
I hope you improve more and more Gideros ... (LUA and speed)
also because as soon as possible I would like to purchase a license ....
PS: sorry for my bad english! (i used google translator)
Comments
This is very helpful and insightful.
Thanks
So busy with plugin framework, but so nice results. Will blog about it in a few weeks.
that was something I always wanted to check myself. Using the other two myself, it is always good to see the results. About the collision issue. Did you try to use the physics and there sensors?
Michael
1. The Lua code to display and bounce balls may not be optimized
2. The Lua VM is slower compared to native code, so that's another point.
(2) cannot be remedied at the moment, but Atilim will check (1) if there's an issue with the algorithm.
I think there is still room for optimizing more. And your tests will help us focusing on these. Thank you again!
Now I'm at work ...
when I get home (tonight) I'll try to publish the sources ...
Thank you.
www.tntengine.com
sorry but how to allegate a file ? ">
www.tntengine.com
Mon*ey phisics test (81 falling boxes) ... you need mon*ey and diddy box2d modules to compile.
http://www.4shared.com/file/6-EDiTjd/b2Helper.html
modified gideros bouncing ball (500 16x16pixel bal)l
Gideros code...
http://www.4shared.com/file/IWLc3cZE/Jumping_Balls.html
Mon*ey code... (need diddy module)
http://www.4shared.com/file/Z8pzBP4h/JumpingBalls_monkey.html
hope it helps...
if you need APK for Mon*ey executables just tell me...
Likes: atilim, gorkem
www.tntengine.com
Likes: GregBUG