paradine's Forum Posts

  • Ashley

    Give me a sign if you have seen this information:

    Sure, capx of the simple test

    Also try Benchmark with many performance tests - run the HTML5 version, then try defferent types of export.

    To open the Benchmark install Chipmunk physics - if you are not interested in chipmunk test, just ignore the results of this test, and focus on the other tests in this Benchmark

  • Ashley

    Sure, capx of the simple test

    Also try Benchmark with many performance tests - run the HTML5 version, then try defferent types of export.

    To open the Benchmark install Chipmunk physics - if you are not interested in chipmunk test, just ignore the results of this test, and focus on the other tests in this Benchmark

  • Ashley

    Please, give me a sign if you have seen this information:

    intel XDK and crosswalk 11 - it runs 40-45 fps on my mobile device.

    The newest Intel XDK and the newest Crosswalk - it runs 45-46 fps on my mobile device.

    Native APK - it runs 57-58 fps on my mobile device.

    Subscribe to Construct videos now

  • well do it. i don't use physics nor do i have to prove to myself anything.

    Lol.

    Why are you talking about physics improvement if you don't use it

    Repeat three times "I will not post anything about things that I do not understand"

  • you could make the same example and try today with better hw, and when c2 has made loads of changes to physics, and not using anymore box2d slow physics.

    also why are people using box2d physics which is slow when you got chipmunk that works fast? and many more factors... but i guess you will whine it's about a native exporter <.<

    You have to prove that C2 has better physics now - create the same test with modern C2's physics.

  • Ashley

    Subscribe to Construct videos now

  • Dress up game in anime style.

    Features

    • graphics in anime style
    • 10 692 000 combinations of the appearance
    • many unusual items
    • cute cats

    Game:

    Play Online

    Video:

    Subscribe to Construct videos now

    Screenshots:

  • Ashley

    intel XDK and crosswalk 11 - it runs 40-45 fps on my mobile device.

    The newest Intel XDK and the newest Crosswalk - it runs 45-46 fps on my mobile device.

    Native APK - it runs 57-58 fps on my mobile device.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • the problem you don't understand is that native export won't fix it.

    IT WON'T FIX IT. repeat with me.. IT WON'T FIX IT. IT WON'T FIX IT. IT WON'T FIX IT.

    Have you read the previous pages?

    CPU bottlenecked games will work better.

    Reapeat with me "CPU bottlenecked games will work better."

    I have proved that CPU-bottlenecked games will work better with native exporters and even Ashlay agreed.

    And now repeat with me: "I will not ever post anything until reading the previous pages". Repeat it three times.

  • you proved that 80% of games you and your voting friend made have problems with the cpu - that actually proves nothing

    also you proved that 85% of your friends need native exporters... same as above

    I don't feel like I have to prove anything. I don't like wrappers but fortunately i learned how to use them properly and I don't have currently any issues neither with gpu or cpu bottlenecking on desktops, browsers and even on mobiles. If something works perfectly fine on my crappy old mobile then it will work fine and even better on anything else

    1. You have to prove that all of your games run 60 fps on every device - if at least 1% of all 177,817 registered users will say that your games run 60 fps on their devices, it will be enough.

    2. You have to prove that you are not the only one, who creates such games - show me at least 1% from 177,817 registered users who create such games.

  • lennaert

    I do not have time to post all the proves on every page.

    Read the previous pages and you will find all of my proves.

  • I don't need to create any pools nor I care about that.

    So far this post was seen by 13,874 "Second Constructors" but only a small few said they want native...

    About 100 users said that they want native exporters.

    Show me any topic where the number of vistors and the number of posts is the same.

    And if you really don't care why are you still in this thread?

    I have already proved that native exporters give much better performance than wrappers.

    I have already proved that 80% games are CPU bottlenecked.

    I have already proved taht 85% users need native exporters.

    And there are no proves from people, who don't want native exporters.

    I am really sorry, that I need to say that, but some of us begin to think, that people, who like wrappers, are just another account of Scirra's developers.

    Show me any reason not to create voting about C3 features on scirra.com?

  • 85% of 14 people that VOTED.

    And how many people voted for wrapper? Zero.

    How many people voted for any other improvement? Zero.

    Show me any other voting about C3 that has more than 14 people that voted.

  • So it's like ~20 people from 177,817 registered users asks for native exporter?

    85% of all developers need native exporters - I have proved it by creating voting on c2community.ru

    If you want to prove, that on scirra.com the results will be different you have to create the voting on scirra.com.

    If you will not do it - your words does not mean anything.

  • I have created thread about native exporters on c2community.com

    The results of voting:

    "Do you want native exporters?

    1. Yes - 85%

    2. No - 0%

    3. I don't care - 15%"

    My translation of russian developer's posts:

    Construct 2 must have native exporters to make export more simple and independent from third party companies. Also it should greatly encrease the performance and compatibility with the platforms.

    Native export is very important for me - independence and fast export.

    Native export - and we caught Unity. And Ashley do not want to make native export because of laziness.

    It is more easy just to change the interface of C3 than to write the complicated code of native exporters.

    I think the problem is technical. All conditions and actions are translated into HTML5. Creation of native export means translation into many other languages, tests of it, many changes.

    I can understand him, it's a plenty of work

    nighttrolley, there was a very cool suggestion to cooperate with gameclosure, add export. Besides gameclosure switched the Space Blaster to their engine and described all the steps in their blog.

    I think they are greedy. I don't understand their actions. I want to just forget)

    As a developer, I think, I have to be friendly to users and to do what they want

    paradine really speaks from all our community, because not all of us can express our opinion in English.

    A agree that sometimes problems with export and performance are developer's mistakes.

    It's another question. But it alsways takes many extra actions to export when we test our games.

    It's not hard, but it takes much time and it's boring.

    Also there is a dependence from third-party developers and restrictions of such exporters.

    There is not enough performance sometimes.

    Native export will make developer's lifes more comfortable. Construct was created for people who want to think only about gameplay. And, people who like extra problems, use accembler for your games - it will make you a true developer.

    P - performance

    I think, that non-native export is the first and the main problem of C2

    There is a strange situation. You have a very nice editor and you can create games, but there is no opportunity to create the end-product. The only opportunity is to use third party products.

    It's bad to depend from third party developers who don't care that you use C2

    The third party developer can change his platform every moment and C2 games will loose the opportunity to be compiled.

    Also there is a variety of problems with optimisations - also exporters work bad with physics.