alastair's Recent Forum Activity

  • I'm looking forward to the black bar fullscreen scale too.

  • "Blank" events, effectively have the "System: Every tick" condition in them -- their actions will always run.

  • If you don't understand the question asked earlier (since you didn't respond to it):

    (Does task manager show it using way too much memory?)

    Pres Control + Shift + Escape, then look for Construct's name and check what memory usage number it says.

  • I haven't used the canvas before, but have you tried doing the "clear canvas" action before you do your drawing actions?

  • I've just tried using "simulate controls" to do movement and it works well, I'm still occasionally getting an issue with the condition but I'm not sure if its still the gap issue or not. Hopefully that 2 pixel gap detection for "is by wall" change will help though!

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Yeah I'm using even numbers and bottom-middle alligned hotspot for detection.

    I didn't realize it was bad to do it "manually". I initially preferred to just use the vector as it feels more "in control" and simpler to just do -400 to move left and say -800 when dashing left, however I guess I may as well try and use the "simulate control" thing and just adjust maximum speeds and see how that goes. It also didn't feel as "snappy" when using "default controls", but that was probably just because I didn't have a very large acceleration value. The main reasons I don't use default controls because in the future I'm going to be adding customizable controls options, and in-case more input options are available later (such as gamepads).

    Also, thanks for the increased size. :)

  • I've been trying to figure out why my events with the "is by wall" condition haven't been working 100%, but then when I made my detectors visible I noticed that the detectors with the platform behaviour weren't always touching the wall -- even when you are trying to slam against it! There is sometimes a gap of 1 or 2 pixels, when it is a 2 pixel wide gap that's when I notice the "is by wall" condition not working.

    I'm wondering if it is possible to remove this gap, or if possible to increase the detection size of the wall by another pixel (or have it variable)?

    I accidently closed the first example I made which revealed the "bug" more frequently, but this new one I made only does a gap of 1 pixel on the left (the gap usually varies between 0/1/2 wide). But at least you can see it has a gap between player and wall:

    http://dl.dropbox.com/u/1024727/c2/gap.capx

  • Does that mean that any "On trigger" condition are effectively placed at the top of the event sheet, since you said their location doesn't matter in the event sheet?

  • I saw some videos about a year ago, I think my thoughts where: the combat system looked dull, the dialogue boring, the characters ugly, the graphics a generation behind, and the environments lifeless.

    I wonder if it has now improved to a quality similar to those early trailers (called Hope and Deceived), but if it has grinding then I won't be interested regardless.

  • That plugin seems redundant to me? Subevents can already do all that? Maybe if there was a better example I'd understand its use.

    To do an "if" all it takes me is to add a "local variable":

    <img src="http://i43.tinypic.com/2mwv9c7.png" border="0" />

  • It can be a good idea to turn off the default controls in the behaviour, and to do input commands with events. For behaviours, I think there are actions that "simulate" input commands, so you could have an event with the condition "Left button is down" and then have an additional negated condition which is "down button is not down" (so you don't move while crouching), then have the action say "simulate control left".

    Or maybe another way you could try would be to, while crouching, have an action that sets the sprite's platform vextor X to 0.

  • Oh wow that's interesting, thanks Rojo! So to make it easier for me to understand, I'm going to presume that the "for each" condition is always there after an overlap but just invisible.

    Now that I understand that, it was a simple fix in this case. I replaced the "pick random" condition with a check to see if 'pickingup' variable equaled 0, so that the event was only occurring once.

    Fantastic, thanks for you help.

alastair's avatar

alastair

Early Adopter

Member since 14 Jul, 2007

Twitter
alastair has 8 followers

Connect with alastair

alastair.games

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • Enduring Visitor Visited Construct.net 90 days in a row
  • RTFM Read the fabulous manual
  • x3
    Quick Draw First 5 people to up-vote a new Construct 3 release
  • x9
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

27/44
How to earn trophies