Rich's Forum Posts

  • Wow...

  • It's posted, hopefully it's dealt with soon.

    Thanks.

  • There's a discussion on gamepads/joysticks here:

    With regard to saving, you can use the 'quick load/save' and 'save to file/load from file' in the System Object, or create your own system via INI/registry etc.

  • I might be mistaken but I think that's possible already, probably just a case of modifying the plugins.

    In any case the way that controls are defined in the application settings means that when new methods of control (joysticks gamepads etc) are implemented it's just a case of inserting a plugin.

    DirectInput is the general standard which most new input devices support, so that'd be a good bet. (Has stuff like force feedback too, which is a plus.)

  • Hi kysan welcome to the forum

    There is a \languages\ directory under the Construct install, and I gather progress is gradually being made at making Construct fully translateable. It's not yet fully done though, so I'd hold off translating until it's ready. But it'll definitely be possible soon enough.

    A video section may be useful, but users can upload their .cap files or post links to youtube videos for now.

    Have fun using Construct

  • This is really well done, if anyone needs extras on platformers this is a great base.

  • Currently the translation system is about 75% complete, some elements are not yet translateable.

    You'll find all the files necessary to translate under the Languages directory, but I'd recommend you waited till it's finished.

  • Construct didn't ruin all your backups, object groups caused any file saved to not load. It's now fixed.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Make sure you're previewing all and not just previewing layout or that'll happen.

  • 1/

    For the actions, the possibility to leave the "pick an object" field blanc.

    Knowing the action then will do its thing on every object picked by the event.

    This will be very handy when the event is made with several conditions. And when the event picks more objects, not certainly beeing the same instances.

    This would quickly become annoying, consider if I wanted to use some System actions in a 'For each ordered', the object field wouldn't be there.

    2/

    A little more power to the event to compensate. Just 1 event more.

    "pick object (x) "

    to use like this

    (event) on collision between "bottom" and "ball"

    ___(sub event) pick "ball"

    ________________________________________(action) .x = .x * -1

    ___(sub event) pick "bottom"

    _____________"bottom" y < 100

    ________________________________________(action) flash 8 times 2 frames

    Why not just do:

    Collision between "Bottom" and "Ball"

    Ball: .x = .x * -1

    (subevent) "Bottom" y < 100

    Bottom: Flash 8 times 2 frames

    Or am I missing something? These objects picked in the collision will be accessible in the subevents too.

    We have no way to pick every object on a certain layer yet. And make an action adressing all those if we could pick em.

    You can use 'Object is on layer' to select every object on a layer.

  • What do you mean by individual event sheets?

  • Hahhahahahahhahahahahahahahhahahahahaha.

    hope it gets better soon

  • Ah really? Didn't realise it was as low as 2000. Guess that needs changing somehow.

  • Depends on if your definition of impossible relies on a 20000 width layout. I guess .

    Chipmunk physics may not have this limit, so it may be gone in future.

  • Is it just me or does the character go invisible when pressing left? (Presumably due to lack of left animation).

    Otherwise it's great.