michael's Forum Posts

  • Not fussed about Android - but starred and commented has been done!

  • This is sort of a ridiculous request. I know what you are after, but it's simply not possible. If anything Scirra would sponsor select developers to showcase their engine. That is what other industry software shops do.

    Well that is basically what I suggested in the OP:

    "Now I am not suggesting that Ashley stop working on C3, but that he oversees the production of this project. There are plenty of C2 gurus on this forum that may want to be enlisted, and I for one would even be willing to make a pledge to pay for it."

  • — I think it is being removed as an option for apps released to Google Play Store, another example of google breaking things!

  • Are you saying like a larger game, or a small game like what we have with the C2 example files? (Space Blaster etc.)

    Not sure on how large it should be, but definitely something beyond the scope of Space Blaster.

      I guess it would be something we as community could suggest and vote on. hehehe, I remember somewhere on the forums suggesting the image on the Scirra home page should be made into a game!

    I know that any project of this kind would not be a small undertaking - but I really think it would be good for both Scirra and the Scirra community.

      I myself am not the greatest artist, but could help make GUI elements, and would be more than happy to create them as a contribution toward the project.

  • This is a request for Scirra to make a game!

    Now I am not suggesting that Ashley stop working on C3, but that he oversees the production of this project. There are plenty of C2 gurus on this forum that may want to be enlisted, and I for one would even be willing to make a pledge to pay for it.

    Why Should Scirra Do It?

      * All of us here want to see C2 and C3 not just continue, but become the best 2D game dev tool around * There is a lot of discontent with C2 at the moment, this needs to be addressed * I can't think of a better way to prove the worth of this tool * Scirra are the only ones who fully know this product and it's potential - and if they can't pull it off then heaven help the rest of us!

    How would this benefit the C2 community?

      * It will show Scirra has confidence in their own game development tool * It would provide a showcase example of the power of this awesome product * It will demonstrate that this tool can be used to create cool games that the world can play * It would boost morale amongst those who have backed this product - that it is a viable development tool they can rely on

    How might it help the C2 community?

      * It would show that performance\bugs issues can be worked around * It could show that many issues faced by devs are in fact caused by devs misunderstanding the event system * The source code could be used as a study vehicle to learn how to use this tool correctly and effectively

    How might this help Scirra?

      1. When developing a game for the real world, beyond a few sprites and a couple of events, running in preview
        * It may help them understand better some of the issues their backers are facing with such a project * It may expose issues with the engine itself when used in this scope, which can be used to improve not just C2 but also C3
      2. When exporting a project
        * It could give valuable insight into the export options available to their users - i.e. make real tutorials available for great user PR * It would also expose Scirra to the issues faced with the most troublesome exporters - i.e. Chrome\NW - and give opporyunity to show Scirra community how to work around them * May also show that relying on Google is an exercise in futility
      3. It will either
        * Show that the issues\requests raised in so many threads about performance, native exporters, and the like, are not unfounded, and should be addressed * Or, that Scirra has been right all along, and the C2 dev community just has to get to know the product better

    What Target Platform?

    I would suggest two projects:

      One that targets Desktop
        Runtime objective; Silky smooth - fairly smooth is not OK
      One that targets Mobile
        Runtime objective: Smooth - at least on devices that have been out for 12 months

    So what do you C2 devs out there think?

  • Starring - for what it's worth!!

    EDIT: additional content removed in the interest of keeping this on topic after giving UberLou later comment some serious thought....

    After all we all love C2 and want these third party issues sorted.....

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Well, as I have said before, until a game is released that performs well on its intended target platform, C2 will not be taken seriously.

    The best dev for such a game is Scirra themselves, they are the ones who know the tool and its potential better than anyone. It is in their interest to publish a cool, well performing game, that not only showcases this awesome engine, but also proves that all the issues with performance\bugs are in fact caused by those (devs) who experience them.

    It may well also expose some issues with the engine, that only surface in projects with more than a few sprites and a couple events.

    The challenge of course is do Scirra have enough confidence in their own engine to take on such an exercise?

  • Well, I don't think Scirra can do any more than they do already, at least not until they expand somewhat - but that is their call.

    The sad fact is that the current export situation (chrome\NW) are woeful and will be for some time it would seam. But that is what you have to go with at present. C2 is currently for prototyping and learning tool - and extremely good one at that.

  • You do not have permission to view this post

  • For me none of the games up there actually play - just a white box.

    Tried in both Chrome and IE.

    Windows 8.1 64 bit

  • Current "Else" condition is the best example. If you put "else" in wrong place then you can't start the preview

    If you delete something important then highlight events with mistakes and don't let user do anything before fixing that broken events. If the name of that variable or something is an issue here, then why editor can't replace it with something. I'm sure C2 can handle making an internal temporary list containing names of broken variables and simply use these void names in events. And when user fix all broken events then the list could be removed.

    There's a lot of possibilities to make it happen without making a mess, question is if devs want to something about it, or leave it like other unfinished "features".

    This a much better way than just deleting a bunch of events.... if it can't be done with C2, at least put it in C3.

  • Hehe, what a cool read though - look how far C2 has come. Ashley is surely a coding guru!!

  • Oh you mean like this bug report that I totally didn't submit? You know this never got fixed either, at least fully.

    Well let's be realistic here: if you want an audio bug investigated, you can't have any other logic for other features of the engine in play because you have an audio bug!

    This implies that if there is a bug, it is likely something you did to cause it - like maybe a bullet is going the wrong way for audio to work correctly.

      But what is really happening is there is a glitch behind the scenes in the engine that is conflicting between audio and bullet. So if you submit a capx with just audio events, you won't be able to reproduce it, and therefore nothing has to be done except close the bug report - yay problem fixed!

    There have been numerous bugs with audio that can't be reliably reproduced with a dumbed down capx. And because of that they will not get investigated, let alone sorted out.

    That however doesn't mean it isn't a C2 bug, it just means you can't reproduce it with a couple of events and no other behaviours in the project.

  • If we go by what the market is showing us with regards to other game-making tools, as soon as you start writing native exporters, your product is frozen. Feature development slows to a glacial pace and all efforts are shifted to attempts to bring feature parity and bug fixes.

    C2 has all the features it needs now.

    Don't add more: fix the export problems, then make all the current features solid, then make an new Editor, and after that start adding more features if you want.

    As it stands C3 will just be C2 with a nice editor (which would be great) but still nothing more than a prototype/education tool - great if you are just a novice, but not so great if you want to let the world play your game.

  • You can use however many layouts/levels you want, and just attach the same event sheet for your game logic to each layout.

    IE one event sheet, many layouts/levels.