Colludium's Recent Forum Activity

  • repkino - this might be possible - thank you for your idea! I'll take a look at it this weekend and see if I can make it work....

  • v2.06 submitted to the store for approval.

    Bugfix: Minify export was broken and is now fixed (closure compiler didn't like the use of a cr.ObjectSet forEach method).

  • just to add to this list:

    Don't use cr.ObjectSet.s.forEach(foo) because the c2 closure compiler is not compatible...

  • Colludium I hope they do it asap. btw Platform2 is really great behaviour, thanks

    p.s. are you planning to add some more features to the behaviour?

    Thanks! What sort of extra features would you like - I'm open to suggestions and will include them if the coding won't kill me .

  • Drago_18 - thanks for the interest! I can only provide support to the new c3 runtime if the sdk is completed and explains the runtime access methods that the Platform2 behavior uses (for collision filtering etc). As it stands all standard plugins are obfuscated so there is no way for me to figure this out (the SDK template says to look at standard plugin examples... ), and I don't have the time to try to guess how they work. No SDK explanation = no port to c3. I've explained my position to scirra and have been told that the SDK documentation will be completed soon. Until that happens then I can't do anything.

  • v2.05 submitted for approval in the store. Thanks RattyRat for the spot on this one.

    Bugfix: added missing reference angle to prismatic joints. Now the two bodies maintain their relative angles when the joint is formed.

  • matriax - thanks - and yes, I am working on adding an optional penumbra effect (from light width). Hopefully I'll have some progress to report soon.

    — Fawk - thanks and I hope so. I have not yet experimented with this in c3 but I have my fingers crossed that the runtime obfuscation isn't going to stop me...

  • I created a bunnymark behavior just to compare the performance of plugins to event sheets - and the plugin was 3x as as fast as using events. So... There is an overhead to the event system. The trade-off, of course, is event sheet convenience - if no one notices the overhead then it doesn't matter....

    Edit - this plugin was for c2 although it's likely the same for c3; I didn't check the forum title..!

  • Does the minifier work if you export for html5? And are you using any 3rd party plugins...? They may not support minify....

  • RattyRat,

    I'm not sure if that's a bug with the library or with the implementation in my behavior; I should have a better idea by the end of the weekend. I'll see if I can make the joint recreation algorithm more robust - in the meantime, as you suggest, the best course of action is to avoid animations on physics objects because the bodies and, therefore, the joints all need to be destroyed and then recreated each time an animation frame changes.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Dammit, it's hard to post replies at the moment...!

  • Hello,

    Afraid I have spotted another one - here is the link : https://1drv.ms/u/s!Aup_NDH7UAIvgrZAt6XHUt-KeMcHqA

    Pressing LMB spawns a new object based on the position and angle of the previous one. Every few sprites you should get one that seems to be fixed in position (although the debug panel shows considerable downward velocity).

    This does not occur if A) the angle is always zero or B) the object has Box2D+ disabled initially.

    So.... Lots of things to keep you busy.

    RR.

    Hi. Thanks for this bug report - it's a good one, but not really a bug and more of a limitation...

    It is a limitation of the Box2D library I used and I am not sure that it will be a simple problem to work-around within the plugin - it's something you'll have to be aware of when using it in c2. The problem occurs when you set the object angle after the body is created and before the box2d+ library has had a chance to run the box2d world. Thus the object's body hasn't interacted with the world when you change its angle, and that causes the problem - and that is why it works ok if the behavior is disabled before the angle is set.

    To avoid this issue, if you're going to create objects and change their angles upon spawn, it's best to set the behavior disabled and only enable it after the object has been rotated.

Colludium's avatar

Colludium

Member since 26 Aug, 2013

Twitter
Colludium has 11 followers

Connect with Colludium

Trophy Case

  • 11-Year Club
  • 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
  • x3
    Coach One of your tutorials has over 1,000 readers
  • Educator One of your tutorials has over 10,000 readers
  • RTFM Read the fabulous manual
  • Email Verified

Progress

18/44
How to earn trophies