"I couldn't figure out how to Save As." Doesn't cut it. Stencyl outperforms the Canvas2D unaccelerated test, and the WebGL accelerated test doesn't seem to render properly.Ģ) There's no source code for the Stencyl version. Well, here's a couple things that bug me about this:ġ) The tests simply don't show the performance differences their tests seem to on my machine (Mac 2.8GHz Quad-Core Intel Xeon, 4GB RAM, latest Chrome 15.0.874.121). We're confident Construct 2 will come out on top each time if done fairly. We really would love to see other peoples tests/methodologies/benchmarks comparing products. If we have an aspect of Construct 2 that is quantitatively better than competitors we do want to tell people about it!Īlso if you read all the comments you will see that the alternatives posted in the comments section showing faster benchmarks were specially crafted to perform well in the benchmark which misses the point of the benchmark completely as it's not measuring overhead of the game engine itself. Construct2 seems good if you want HTML5 though but it's still no where near as good as flash really.Īdmittedly anything positive we post about Construct 2 is generally intended to help promote Construct 2. They clearly seem anti-flash also so i guess flash probably won't be a possible format either. While it's true HTML5 is getting better you still need to use the GPU to take advantage of that which not all players would have but flash is fast enough without it.Ĭonstruct 1 was quite good but always full of bugs and having looked at the forums recently for V2 they clearly no longer have any interest in Exe format unless it's in wrapper (which would be pointless). What seems funny is how someone posted a non scirra made stencyl version that performed better shortly after, plus it is not using the new flash stage thing which would probably be much better than WebGL anyway. It seems bias in my opinion, in fact most of the blog so far just seems like a big marketing plan. Ashley sums it up best in the other performance blog post: We think performance in games can be important (but not all the time!) as it can be a limitation on creativity. We've put a lot of effort into optimising Construct 2 for performance and it's perhaps one of its less known features which is why we did the blog post. But as there is no independent source to refer to we had to do it ourselves. Of course we knew that when we did it we would receive criticism for bias. Our full methodology is explained along with project files to download as mentioned above. Tom from Scirra here, this is all we're trying to say! There are currently no benchmarks out there comparing products so we thought we would do one, and we invite other benchmarks from independent sources as well! We'd love to see other benchmarks in this area. I'm not too versed in performance testing stuff myself but is creating as many sprites onscreen as possible before it starts lagging really the best way to go about this? It's probably a good test for just pure rendering but in the end for most applications each sprite will have to be executing some game logic, the majority of them won't be sitting there just displaying. Guys they posted their entire design methodology with links to the tests they used to measure each application, why not try to see if there are flaws in that instead of dismissing it based on "bias" or "credibility" or w/e
0 Comments
Leave a Reply. |