bergmark's Forum Posts

  • Hi Ashley, thanks for the feedback. The rotation method was a gamble - I wanted to achieve a bobbing effect, and wondered if collision boxes of different shapes would react that way if their shapes were irregular. Guess it worked! Glad you liked it :)

    It may be hard to explain, though the "up and down" effect in 108 was smoother whereas in 111, the boat jittered more when its lower surface was touched by the rotating pixels. But following your suggestion, I turned on Point Sampling and there's no more jitter now :)

    Thanks a lot ;)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Hi, I read this scirra.com/forum/solved-manage-scroll-behavior-metal-slug-like_topic45395.html and found Kyatric's ingenious method for stopping the scrolling, similar to how games like Metal Slug do it. Currently I'm using the ScrollTo method at every tick (event, not the behavior applied to player) on a test project, but the example got me wondering - how many ways are there of stopping the scrolling and locking it to a specific area on a layout? I'm asking because I'm really curious and I'd like to keep the code as clean as possible.

  • Hi, I found something strange with platform collision in r111. I was making a small level in C2, testing out rotations. A quick explanation of the system: I have several rotating sprites. They operate in pairs - one rotates clockwise, the other counter, and there are several in a row - and their collision polygons are hexagonal. What this means is that any object on top of them (in my case a ship) will seem like it is swaying or bobbing over the sea.

    With version 108, the effect was smooth but with 111, the collisions seem to make the ship jitter a lot more, as if the polygons are pushing the ship a bit more forcefully. As per Ashley's request, here is the *.capx:

    mediafire.com

    Any ideas? I don't know why it moves smoother with 108. Also apologies since the level is kind of messy and incomplete otherwise.

    EDIT: Sorry, forgot to mention that you can move around with arrow keys or WASD.

  • What I'm getting from the *.capx is that each frame is of a different size. By this I mean that the wizard sprite has, for instance, a number of pixels that make up the eyes in one frame and a totally different amount the next, along with different positions, suggesting it's misaligned.

    Did you use some software to automate the sprite's frames?

  • So. This is what I did:

    Player : Y > Scroller.Y + 280
       Player: Set Y to Scroller.Y + 280

Player : Y < Blocker.Y
       Player : Set Y to Blocker.Y

    Aaaand... It works. This is interesting, because I've always been terrible at game editors, but I got this to work. Blocker, by the way, is simply an invisible sprite with the same shape and size of Scroller, along with its Bullet behavior and speed, placed a bit above Scroller.

    So I can sleep a bit easier tonight! My thanks to both of you once again :)

    Edit: I changed 300 to 280 because after changing the Y < Scroller.Y, the ship began going further down. 270 might be more adequate, though.

  • My thanks, Ashley. I did check out the Scroller, making it visible and changing values as well. I got a somewhat better idea of what to do with it now :)

    On the other hand, I'm almost ashamed to say how bad this is going on otherwise, though I'm the only one to blame really. I have followed your suggestion, and also went probing everywhere I could think of. Maybe I'm not giving the proper instructions, or maybe it's due to me using the free edition, can't tell.

    I'll poke this a bit harder for now then call it a day.

  • Thanks, I'll give it a quick try :) Also, my bad, I meant to say "make a ship be able to reach the top of the layout screen (but not go further than that)", instead of "now", meaning it should fly freely around the screen but never cross/go outside the layout.

  • Hi, as per the topic, I'm having problems understanding this command (and if I'm hitting a wall with this kind of simple command, I'm doomed). I'm messing around Scirra's Space Blaster template, and noticed the ship is "locked", unable to move beyond an area. In the code, this reads as:

    >Prevent the player flying ahead too far or going off the bottom of the screen.

Player : Y > Scroller.Y + 300
        Player : Set Y to Scroller.Y + 300

Player : Y < Scroller.Y
        Player : Set Y to Scroller.Y

    My understanding is that the 300 value is basically the area that "locks" the ship, preventing it from going further (any value above increases the area vertically, trapping the ship if moving down; any value below it narrows the area). While I'd like to know how I can make a ship be able to reach the top of the layout screen (but now go further than that), I'd also very much like to understand the the uses of Scroller.Y.

    I've also searched the forums and haven't found a concrete answer, though maybe it has to do with my search terms <img src="smileys/smiley26.gif" border="0" align="middle" />

  • Hi, I've been tinkering with Construct 2's free edition recently. I've noticed that the program lets me specify screen resolutions, but I'm missing the point of some things.

    I started messing with the possibility of making a vertical shmup. The plan, should I eventually finish the project, is to purchase a license that lets me export the game as a PC executable. In a slight oversight, I began working on the sprites first but then it ocurred to me that I'd like to do something similar to Jamestown insofar as screen resolutions, letting players choose between several of them, but also to provide screen modes that stretch pixels or maintain their ratio.

    So long story short, is it possible to simulate something like this in a browser for testing purposes without having to constantly change my monitor's own resolution? Also, is there some optimal window size for a pixel-based vertical shmup? Thanks in advance!