Mikal's Recent Forum Activity

  • This worked very well, thanks for the nice interface / feature.

    Sped up perf by around 30X versus calling a C3 Event function from C3 JS scripting to access the plugin ACEs.

  • Ah, I think I am beginning to understand... I need to extend IWorldInstance w/ weakmap of functions I want to expose to scripting and register with:

    GetScriptInterfaceClass() {

    return self.IMyPluginInstance

    }

  • How can we call or (expose to call) 3rd party plugin methods from Scripting, similar to how we can call methods for plugins like Sprite, Text, etc. from scripts.

    I have used methods to work around this like call C3 event functions from script, but I benchmarked this and calling a C3 event function from Script has a higher performance cost for my project which drop performance below 10fps. I also benchmarked calling a function with no events and the action of just calling the empty function was also fairly heavy.

  • Diego

    The scene graph features are great, the additional ACEs and the new editor support.

    How do you suggest to 'clone' a Scene Graph at runtime. For example if I have the Skeleton model setup in the editor once, with parent child relationship and placement, during runtime, how would I create another version and place it somewhere else? I would hope that I could create a new Scene Graph based on the particular root instance (perhaps through UID, or some other picking, like an instance var, etc.)

    Since scene graphs can have multiple instances of the same object, it does not seem like Containers work for this (we have tried and I have not yet seen a successful implementation using containers, especially with multiple instances of the same object in the Scene Graph.)

    Any suggestions or ideas, or is this a new feature request?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Ashley Here's another usage of the new Mesh Points w/ the C3 Spine plugin.

    I added a SpineBBoxGetPoly expression which returns poly points in JSON format of named slot/bounding box attachment. Using with C3 Sprite Mesh to creates a very accurate Collision Bounding Box in C3.

    SpineBBoxGetPoly expression returns poly points in JSON format array of named slot/bounding box attachment. Use C3 JSON object to parse and use points. The points are returned in top level JSON array [x0,y0, x1, y1,…]

    This is just a simple bbox with angles and stretches, but we could make a bounding box which actually followed the spikes on the sword, nice feature Scirra!

    The yellow / pink / blue box is a C3 Sprite w/ mesh points.

  • Add SpineBBoxGetPoly expression returns poly points in JSON format of named slot/bounding box attachment. Use with C3 Spine Mesh to create a very accurate Bounding Box in C3.

    SpineBBoxGetPoly expression returns poly points in JSON format array of named slot/bounding box attachment. Use C3 JSON object to parse and use points. The points are returned in top level JSON array [x0,y0, x1, y1,…]

  • Release 1.17.0 Add debug property, SpineBBoxCenterX,Y expressions. UpdateBBoxes action.

    Bounding Box Attachment

    - SpineBBoxCenterX, SpineBBoxCenterY espressions give the average of the named slot/bbox polygon points. Useful for attaching C3 Sprite object / collision box to the center of the Bounding Box.

    - The UpdateBBoxes updates the bounding box to the current point in the animation. It should be done just once per tick per instance, before the SpineBBoxCenterX/Y expressions are used.

  • I have been working with colyseus.io/, websocket based. So far it's been good. I am making an authoritative server using it.

    There is a C3 client plugin for it.

  • FYI for any following this, Ashley has fixed this and the fix will be in the beta release (after r219-2.)

  • Ashley

    I did an experiment, it looks like the physics behavior collision box is not getting updated as a collision poly changes with updates to mesh points. I created an issue below w/ example project.

    github.com/Scirra/Construct-3-bugs/issues/4269

    For other collisions like between 8-dir behavior and solid, the collision box is updated.

  • Thanks Ashley for the info. I’ll keep testing and if it’s still not working for me, I will post to the github issue site with a sample project.

  • First, thanks for the new Mesh ACEs for Sprite, it will definitely prove useful for new visual effects!

    In experimenting with setting absolute x and y mesh points, it appears that the collision polygon does not expand outside of the original bbox in the editor. I am hoping that this will be changed in the future. I do see the 'new' bbox is changed in the debug preview (to be larger than the original bbox), but the collision poly does not seem to also grow beyond the original bbox size.

    Looking for feedback on the design intent (and if need I can file a bug report.)

    Large bbox is setting mesh points outside original bbox, but collision poly remains around the size of the original bbox (small box picture.)

Mikal's avatar

Mikal

Early Adopter

Member since 22 Apr, 2016

Twitter
Mikal has 112 followers

Trophy Case

  • 9-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
  • 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
  • RTFM Read the fabulous manual
  • x10
    Great Comment One of your comments gets 3 upvotes
  • Delicious Comment One of your comments gets 10 upvotes
  • Email Verified

Progress

21/44
How to earn trophies