AM_Games's Forum Posts

  • Aye they do, unfortunatly it doesn't seem to work very well with C2 project.

    Much like you, I ran into the same issues of buttons not working using Cordova.

    Real shame about the Ouya though, looked like such a promising platform and the controllers are lovely (apart from exploding into batteries and plastic if you knock them off the chair lol!)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I'm currently teaching a BTEC Level 3 Games Dev unit at a college (16-19 year old learners).

    Currently been delivering it in VB.net / Visual Studio because this is what we have (learners have to create a space invaders style game).

    Going to be moving to C2 for next year for exactly this reason; going in cold with learners who don't know programming and 16 weeks to teach them "to make games" is very challenging if they don't have a programming background.

    In all honestly i've spent most of my time when delivering this unit fixing basic programming syntax problems rather than getting my guys to produce good results and working content. C2 offers a straightforward path into games dev that can be really easily built on in future if the students choose to, or provides them with a solid grounding in how game engines work and how to produce good quality content. It's worked extremely well with the group i've trailed it with and they've managed to produce in 2 weeks what the other groups has achieved in 10 weeks.

    For reference: my actual background is in UDK/Unreal 3/Unreascript with only using C2 for mobile games in the past but as a jumping off point for games dev it's pretty much second to none. Also Scratch is delivered as part of the curriculum in schools now, so the learners are already familiar with the visual scripting style and can pick up actual programming more easily later on.

    Anyway, as someone who is actually teaching games at the moment I thought my perspective might be helpful here.

  • How I do selections and locking (in this case for spaceships) is below:

    So "ShipSelected" is a global Variable as is "ShipsUnlocked"

    The green icons are for showing what ship is selected

    When ShipsUnlocked is greater than or equal to 1, then this ship can be selected, setting the ShipSelected variable to 1 so that this can later be passed into the main game layout and used to pick the sprite/name/whatever.

    When ShipsUnlocked is less than 1, a sprite is displayed over the ship (in this case a padlock icon) meaning it cannot be selected.

    This is pretty far from the cleanest or tidyest way to do this, but it is very easy to follow.

  • Always used CocoonJS for publishing to Ouya, works perfectly.

    https://cocoon.io/home

    It used to be a lot easier to use though, they've recently changed the UI and it's a right mess!

  • Lordshiva1948

    Brilliant, thank you!

    Found them on your Dropbox named "OuterGlow.XML" and "OuterGlow.FX".

  • chrisbrobs Been using this in a project but unfortunately file no longer available.

    Anyone have a mirror?

  • +1 for this.

    Also maybe an option to lock Pasting (Ctrl +V) into locked layers, or hidden ones.

    I probably waste half an hour a day looking for lost sprites this way.

  • With Greenlight on the way out, being able to publish to Xbox Live would be a huge boost. Having done OUYA games before the joystick/touch movement is very easy to integrate so would be lovely to work with joypad based experiences again!

  • Been using construct 2 for 4 years now and didn't know there was a "NewLine" function for text!

    Thanks LaDestitute

    Having worked with UDK and previously Unreal 3 in the past I thought i'd weigh in on this.

    At it's height, Epic had around 10 programmers working full time on the engine for each stable release and 2 Scripters working on the front end code not to mention the entire team that worked on Kismet function (the visual scripting part).

    Scirra has Ashley and

    My point being; the amount of time it takes to write new features vs the rate they're expected by the user base is vastly disproportionate.

    Either we have a stable engine that exports to a fair few platforms or we have a largely broken engine that has a lot of features (see the early days of Unity engine or the first few months of Unreal 4).

    There's always going to be limitations to what Construct can do and the guys are simply moving the engine in a direction that will allow Scirra to keep growing as a business and better develop the product we're all paying for.

    With only a couple of people working on the backend nobody can seriously expect everything in this thread to be addressed immediately and in the lifetime of C2 we've had a whole lot of new features and things the community has asked for, but everything takes time.

    Personally I don't like the idea of a browser based system, but that's just it, I don't like the idea of it. Nobody can judge C3 yet and I wouldn't expect it to be in a state where anyone can judge or berate it for at least the next 12 months.

  • Used CocoonJS for a few published games in the past. Never had any trouble with it at all, it just works brilliantly and their remote preview tools are excellent.

    When making "buttons" with cocoonJS you just need to use a standard sprite and have an "on Touch" action for it instead of a button object.

  • msha91

    Just done a quick Example CAPX file.

    You can get it here: https://1drv.ms/u/s!Au_xHg0ueCl3wQYVTUj0VorZRpMp

  • Best bet is to use a Global variable for this I think.

    Each time you shoot, add 1 to the variable.

    On the final shot, reset it.

    So your event would be something like:

    On Mouse click & BallNum==1 -- Shoot Blue & add 1 to BallNum

    On Mouse click & BallNum==2 -- Shoot Green & add 1 to BallNum

    On Mouse click & BallNum==3 -- Shoot Red & set BallNum to 1

  • Hello Zion,

    I have attached an example I did for another forum member the other day for showing and hiding layers using the same key, you should be able to adapt it to do what you need <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

    https://1drv.ms/u/s!Au_xHg0ueCl3wQVQVQShmJCgQBVh

    Hope that helps.

  • Ah, my mistake. Apologies