ShinobiSlash's Forum Posts

  • Are you doing one of the following:

    - adding joints to an object in the same tick that it's declared to the physics plugin / created

    - destroying joints after an object has been destroyed

    - destroying an object that has just had joints attached

    - using a complex collision polygon with more than 8 verteces

    ?

    Also, does it do this in asm.js and box2d physics?

    Eh, for the stuff in BOLD, nah, not really that advanced in C2 yet,

    And I'm using box2d physics. And as stated in the above post, the problem has been solved as of now.

  • Asking if you should switch to Platform from Physics is a loaded question. If you can do what you need in Platform, you should have avoided Physics.

    However, it shouldn't be too much work to quickly experiment. Can you just turn off animations for the moment and play the game? That will go a long way to deciding what to do.

    Yea, I just removed the physics behavior from a few animated sprites (didn't really need them anyway for the most part)...and the game ran fine (in the runtime and html) w/o any crashes, freezes or bugs. Thanks for your help, hope you get the rep points,

  • Are your physics sprites animated? I found this:

    Also someone else reported an issue with animated sprites. You could try using an invisible sprite with physics on it and set your animated sprite to that sprite's position. (I'm hesitant to suggest pinning, as pinning to physics also has it's problems).

    Yes they are...so that's the problem? Well, that would be kinda complicated since they also move and whatnot. So do I give the same behaviors to the sprites (sine, bullet, etc) movements to the invisible ones as well?

    Do you think I should just switch to platform behavior instead? Again, I done all the layouts for this game already, and readying it for release soon (I'm actually doing it for a client). So please, I really need things to work properly, or else it would be a wasted project and 80-100 bucks for the Pro License if I have to go to another program.

  • Ok, just ran the HTML, and midway through the game it froze up...completely stop playing.

    So again, I really don't know the issue; could it be the new NW.js I'm having a problem with? I will try re-installing it.

    And if anyone can tell what the hell all that means (the lines that start with 'at'), it would be really helpful.

  • Even if it's due to physics behavior,can you reproduce with Chrome or firefox?

    Well, it did the same in Chrome before...

    But now, I dunno what (maybe I switched computers) I've just ran it again with no problems. I'm gonna try to see if the HTML will go along w/o a hitch as well.

  • Bump...any help?

  • Sorry if this not the right forum for this question, but ran into this problem:

    Now, I read the Bug Report Forum guidelines, but I'm not sure if this fits the requirements. Because this happens after playing thru a few stages (or probably after a certain time period, about 20-30mins of playing), so I can't just simply upload a simplified capx.

    And I'm using ver.2.22,

    So any help would be appreciated.

  • It would be hard for me to give a specific answer without seeing your situation. The answer would be use the one that best fits your needs!

    You said you were already using force for your normal movements. I assume you would apply them on the ball. Either apply more in the same direction you already are applying for when you're going uphill, or maybe apply at an angle depending on the slope of your hill to be more efficient.

    Ok, been busy, but I will try to post a demo soon...

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I see it stuck on my system as well. Have you confirmed when you load the same project with 216 it works fine? Try downgrading and exporting again. Maybe it is a bug you found, try on the bug forum.

    No, I didn't, but I already updated the javascript (NWs?) file for beta 222. I really don't feel like rolling back.

    But I might have to do so.

    And here's how it's supposed to look (this was made using 216 and Free version/before I upgraded):

    http://gambler-snake-26122.bitballoon.com

  • http://cameraman-shipping-10615.bitballoon.com/

    Here's a link to the html file...when I run it, it works fine sometimes, but whenever I export to html, it just stays on the main splash w/o moving on to the next layouts?

    I;m using the new 222 beta; it was working fine with ver216. Is there some kinda bug I should know about?

  • Layout scale is a system action.

    Set up a condition for when you want to zoom, such as On Start Of Layout. (Or on key press, or touch, ect.)

    Then use the action System - Set Layout Scale.

    Thanks, I will try that tomorrow (a little burnt out ATM, )

    No rep/thank buttons here?

  • If you want it to go uphill, you'll need to either add force or impulse.

    https://www.scirra.com/manual/98/physics

    [quote:2s8wbbne]Apply force

    Apply force at angle

    Apply force towards position

    Apply a force on the object, either at an angle, towards a position, or with custom X and Y axis forces. Applying a force causes the object to accelerate in the direction of the force. Forces can be applied from an image point or the object's origin.

    Apply impulse

    Apply impulse at angle

    Apply impulse towards position

    Apply an impulse on the object, either at an angle, towards a position, or with custom X and Y axis impulses. Applying an impulse simulates the object being struck, e.g. hit by a bat. Impulses can be applied from an image point or the object's origin.

    Thanks...any one in particular? I use 'Force' action for my normal movements. And where would you apply said forces? on the Ball or on the Tile surface?

  • Not sure if this is allowed here, but here's my event Pause code blocks.

  • Thanks, I will check that out, but still a bit confused...

    Is there any video/tutorials on how to do it? I'm assuming you would put this (layer scaling) into the event sheet of the actual stage, rite?

  • For example, if the Window size is 640x480 normally, but for certain stages/levels, I want it to zoom out a bit (like to 800x600). Is there a way to go back and forth without changing the window size for the entire project?