nightofgrim's Forum Posts

  • The canvas objects hotspot isn't adjustable and it doesn't update when the object is scaled.

    If it's scaled down to 50% of it's size it will rotate around a hotspot that would exist if it were still 100%.

    I know there is a way around this.

    example: http://dl.dropbox.com/u/1727838/rotate.cap

    The linked cap is also a simple example on how to create movable scalable rotatable dynamic display boxes.

    I'm going to use this on a 45" table with a rear projection (like the Microsoft surface table)

    Sense the players can be on either side of the table this will allow them to move their personal boxes to a comfortable viewing position.

  • Since I'm more skilled with C++ now I'll look into it again. It might not be too tough to do what you need. No promises, though.

    The minimum would just be the ability to get the messages in a format that can then be parsed in construct.

  • I hope you can. Thanks for looking into it again.

  • bump

  • Something is wrong for sure, but I fixed it pretty easily. I just deleted all the points and re-drew them and it worked fine.

    Still, it shouldn't mess up in the first place so, yeah... bug.

    I think at a certain number of points it will break. The game I'm working on has some large objects that need a bunch of points, so right now I have to break them up.

  • I will file a bug report too but thought I should mention it here too.

    I found a new runtime bug with the physics custom collision.

    CAP can be dowloaded here: http://dl.dropbox.com/u/1727838/collision%20bug%202.cap

    Screenshot showing what happens:

  • THANK YOU for the Physics FIX!!!!!!!

  • sweet

  • Once again, thanks for all the kind comments, guys. I greatly appreciate the feedback.

    > I found a new one

    >

    > When zoomed in the camera wont scroll all the way to the edge of the layout.

    >

    > Cap file if needed:

    > http://dl.dropbox.com/u/1727838/camera%20bug%202.cap

    >

    This is actually a problem with Construct. When unbounded scrolling is left unchecked, Construct doesn't seem to be taking into account the display zoom level when determining the edge of the layout relative to the edge of the screen. If you check "Center view on me" in the sprite's properties in that CAP and then set the zoom level yourself, you'll notice that it does the same thing.

    I'd suggest reporting it as a bug, although maybe one of the devs could pop in and explain whether it's supposed to be this way or not.

    May I suggest a work around?

    How about an option to simulate bounded scrolling. So we would check "unbounded scrolling" and your camera plugin would compensate and only scroll to the edge.

  • I found a new one

    When zoomed in the camera wont scroll all the way to the edge of the layout.

    Cap file if needed:

    http://dl.dropbox.com/u/1727838/camera%20bug%202.cap

  • Any chance on a Physics custom collision fix soon?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • That was a fast fix. Awesome.

  • When using your plugin I can no longer click on objects during runtime.

  • No idea how you made all the hinges and physics work like that, is something I'd love to learn.

    By hinges are you referring to the swinging elevator?

    [quote:et7ytuxp]Wow that's really quite impressive. Nice work mate

    I'd love to see how you made the player work... a physics platformer has been on the back of my mind for a while now, but I had trouble getting anything to work convincingly.

    ~Sol

    I was thinking about making a tutorial but with some new physics collision bugs I can't. Maybe when they get fixed I will share.

  • Nevermind, there is an entirely new issue now.

    If the hotspot isn't centered with the sprite, then the collision data for some reason is shifted (even with bounding box). But if the hotspot is centered it makes it impossible to create custom collision.

    Look here. The red dots are where the hotspots are. The little boxes are resting on where the actual collision box is. All of these are using "bounding box"

    <img src="http://imgur.com/D0Znr.png">

    Here is a link to the cap file: http://dl.dropbox.com/u/1727838/physicsBug.cap

    Please fix the collision bugs