calminthenight's Recent Forum Activity

  • I'm not sure if it's just my brain falling apart but I can't seem to reference object IID's inside expressions anymore.

    Using the expressions: object(0).X & object(1).X returns the same value (IID#0.X) for each.

    Also, after putting the IID in the editor will not suggest expressions after the full stop.

    Tagged:

  • Also, forcing objects into solids can cause problems. In my experience, glitching through solids, while annoying, is almost always a result of you telling an object that it should be in a position where a solid object is residing, and the solid object trying to tell the other object that it shouldn't be there. If it is not that, then it is edge cases where the object is moving so fast that by the time the collision event is registered, the object is already inside the solid. You have to design these edge cases out.

  • Changing the browser zoom messes C3 up, it should give you a warning dialogue when you do it. Only way to fix is to reload.

  • R0J0hound Thanks for having a look. Hopefully someone more learned in the ways of glsl will take an interest some day, or if not I'll eventually have a fiddle.

    alastair I wouldn't go as far as saying it is essential, but it is in my opinion one of the most authentic (and useable) arcade crt shaders around and would certainly be a great asset to pixel art developers.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Post a link to a version without 3rd party plugins (betteroutline) and I'll have a look

  • 1drv.ms/u/s!AkmrWgxeuxlKhItpN_TAMQLG0JgEYQ

    There is an example of both a global attack timer and individualised attack timers.

  • Ashley Thanks for that, I was curious to see why it would affect a whole number.

    That is exactly what I ended up doing, and it is good to know for future projects.

    As a follow up, does the engine, or do certain objects do some internal rounding when an angle is very close to whole number, as it is in this case? I noticed that the text object, when set to bullet.angleofmotion would still display 45 or negative 45 (not 44.9999999) in this case where I have seen it show the actual figure in other situations.

  • The other day I was making a bouncing DVD screensaver for someone on the forums for a bit of fun and I was frustrated by an error I hadn't seen before.

    I was using an event to set bullet angle of motion to 45° yet the angle would always end up at 44.99999999.

    Every other angle is fine except for 45° and -45°, meaning that I had to use extra events to check the angle later.

    I'm not sure why a floating point error would occur here as it is a whole number. Any ideas?

    Project here: 1drv.ms/u/s!AkmrWgxeuxlKhItoFF0OPkagZ00TLQ

  • Use the pathfinding behaviour.

    Var_ISawYou=True

    Var_IAsmSeeingYou=False

    then

    Every X seconds find path to player.X,player.Y

    On Path found - Move along path

  • All improvements to the audio system are very welcome :) It needs love.

  • It depends on your original and new resolutions and the size of each asset.

    Because you are not resizing to the same aspect ratio you will need to test and work out what looks best.

    If you were maintaining the same aspect ratio you could just apply the scale that you used to the assets.

    e.g.

    If you were resizing from 1260x720 to 630x360 you would scale all your assets to 50%

calminthenight's avatar

calminthenight

Member since 28 Jan, 2018

Twitter
calminthenight has 6 followers

Trophy Case

  • 6-Year Club
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

11/44
How to earn trophies