newt's Recent Forum Activity

  • 1) C2 Construct 2

    2) C2

    3) C2

    4) Sprite animation (Load frames)

    5) Sprite animation (As in how do you do that with?)

    6) Vertex Object... and several new behaviors.

    7) Yeah pay to play, see 4)

    Zip's and appath& is your friend, probably have to see some big projects before thats done.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • + Sprite: On step

    -> Sprite: Push out of Sprite2 : Normal (use for slide)

    -> Sprite: Apply friction of 0.5 to speed

    + MouseKeyboard: Key Right arrow is down

    -> Sprite: Accelerate horizontal speed : 100

    (orientation 45 degrees)

    + MouseKeyboard: Key Left arrow is down

    -> Sprite: Accelerate horizontal speed : 100

    (orientation 140 degrees)

    Where Sprite is the player, and Sprite2 is the terrain.

    Note:

    You could make a Sonic type of game out of this by figuring out a way to adjust the orientation.

  • Platform:

    a raised flooring or other horizontal surface, such as, in a hall or meeting place, a stage for use by public speakers, performers, etc.

    a horizontal surface or structure with a horizontal surface raised above the level of the surrounding area.

    a flat, elevated piece of ground.

    Hmmm, perhaps something like a custom movement behavior for this would work.

    http://dl.dropbox.com/u/666516/cmslide.cap

  • The runtime stretches the texture like the layout editor shows. Canvases have always used as much VRAM as their overall size is (I wouldn't recommend canvases bigger than the size of the window), so this doesn't affect that.

    Well the reason I ask is because that even if you do resize at runtime it process's from the original size. That actually works well if your using an array, or distortmap. The strange thing is the amount of pixels will remain the same, but scaled. But updating the collision mask takes much longer once its scaled. Dunno it seems like its using the new size for that.

    Any way, some awesome work guys.

  • > Please - report bugs to the tracker, and include a clear explanation of the problem, what you expect to happen, what you see happening, and steps to reproduce. I just ran that .cap and it looks like everything is working fine. What's not working?

    >

    The canvas is set at a specific size and looks fine in the cap, but when run, it appears as a small square less than a third of the size it should be, like in the pic. It's already been mentioned in the tracker too as far as I'm aware, a few weeks back when I first mentioned it, someone else said it was a bug and then reported it.

    The example in the cap is an over the top one with it made much larger, to show the difference.

    Resize the canvas in the pic editor to your desired size, then check how much vram you use.

    Resizing needs to happen at runtime otherwise you'll eat up ram like milk duds, and god help you when you update the collision mask.

    OK, that one's fixed in next build.

    Is it just fixed for the editor display, or is it going to actually change the canvas dimensions for runtime?

    Edit:

    [quote:1gzdivmn]- [FIX] Canvas: cropping or invisible if not scrolled to 0,0 on start of layout

    Can I has no scroll always?

  • Hmmm, sooo..., how much would you be willing to pay for said objects?

  • Did you have multiple instances of the same object selected?

  • I'm not sure if it's a bug, or more like incomplete, any way yeah you can only use one named timer on the timer behavior. It is doable if you add an new behavior for each named timer you need.

    .... oh Rich... where are youuuu?

  • You can add components to your array, z for example, but that has a limitation at some point.

    You can also add multiple arrays, but again that may be limiting if it takes up a lot of memory.

    Probably your best bet is a private variable for the stat.

  • I tried lerp a bit, and it seems to be working much better, Im not sure If I have it set up exactly right but It does seem to be getting there.

    for x, and y loops

    set u and v to lerp(0, maxtilesize, loopindex(x, and y)*0.1

    That gives me a decent showing, but Im unsure of using loopindex, as the percentage.

  • You cant get per pixel on anything less than 2 pixels, so yeah point would be better.

    If your ship isn't terribly oblong you could try distance(x1,y1,x2,y2). Something like:

    system compare distance(bullet.x, bullet.y, ship.x, ship.y) is less than ship.width

    bullet destroy

    or what ever

    Distance works off of the image point, so as long as it comes within that circumference it should work.

    Other wise the only other thing you could try is instant hit with step, but that would be best with a percentage type of system... wouldn't really work with a bullet hell shump.

newt's avatar

newt

Member since 12 Nov, 2008

Twitter
newt has 26 followers

Connect with newt

pigmalien.github.io

Trophy Case

  • 16-Year Club
  • Entrepreneur Sold something in the asset store
  • 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
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Popular Game One of your games has over 1,000 players
  • 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
  • Unrelenting Visitor Visited Construct.net 180 days in a row
  • Continuous Visitor Visited Construct.net 365 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

31/44
How to earn trophies