Ashley's Forum Posts

  • Thanks for the report - you're right, it's a bug. Thanks for the clean repro. Should be fixed in the next build.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The physics basics tutorial strongly recommends you do not use 'set position' and 'set angle' on objects using the Physics behavior, because in order to keep up Construct 2 must tell the physics engine to teleport the object in the physics world. This is complicated and for technical reasons has to happen at the end of the tick, and must also override the velocity otherwise the object can start drifting around even when you use 'set position' every tick like you do.

    So what happens is you set the object position, Construct 2 marks the object to be teleported and reset at the end of the tick, then 'On touch end' fires, and sets the velocity. At the end of the tick Construct 2 tells the physics engine to teleport the object, and reset its velocity so it actually ends up in the position you asked for. So almost every time the object resets to 0 velocity and falls straight down.

    I've managed to find a workaround for this particular issue, so it should work in the next build. But I think there are other problems involved in using 'set position', so I would encourage you to find a different way of handling it if you can.

  • Thanks, should be fixed in next build.

  • ZhaoYun, that sounds like a different problem, can you make a separate bug report with steps to reproduce?

    bjp - dragging objects between projects is not actually supported yet, it's on the todo list - workaround is to copy and paste an instance from the layout.

  • This is because of the breaking change where created objects are not really created until the end of the next top level event. As a side effect the object count is not updated either until the end of the next top level event.

    I think this has been reported a couple of times now, which is reason enough to fix it, but unfortunately this will be another breaking change (since I am aware some projects already depend on the way it currently works).

  • This project appears to be working correctly. I'm not sure what you're expecting to happen instead? It is useful to provide .capxs which are as minimal as possible, so any events or objects not directly related to the problem are removed.

    By the way, if you spawn objects inside (overlapping) other objects, you should not expect the result to be realistic either, since this is an impossible physical phenomenon.

  • 'Set scale' was a shortcut for 'Set width to OriginalWidth * scale, set height to OriginalHeight * scale', so this did undo mirroring or flipping. I've changed it for the next build to preserve the mirror/flip state, so that should fix this.

  • .capx link is 404, did you make it public?

  • I can't reproduce any problem, it works perfectly in r103.2 here. Are you using the latest version of C2?

  • Works fine for me:

    http://www.scirra.com/labs/cjstext.zip

    Tested on a HTC Sensation running Android 4. I think this is a problem with CocoonJS running on Jellybean. Could you report it to ludei instead?

    • Post link icon

    Here at Scirra we're a very small team. We're lucky enough to have a popular product, but at the same time this means we receive a very high volume of bug reports. Unfortunately the amount of bug reports we get is beginning to become difficult to manage.

    A significant number of bug reports do not include sufficient information for us to do anything about the problem. For example, a bug report might consist solely of an error message. Alternatively a report might describe an issue, but not provide us with any way of reproducing the problem ourselves (such as steps to create the problem in a new project, or an attached .capx file demonstrating the problem). As described in how to report bugs, it is impossible for us to do anything about this kind of report.

    The large number of bug reports means the forum is beginning to fill up with this type of unresolvable report, which typically also goes unanswered by the original author when prompted for more information. As the number of bug reports made increases, it becomes more and more difficult to manage.

    In order to alleviate this we are introducing a new policy on closing bug reports:

    Bug reports which do not contain enough information will be immediately closed. We will ask for more information, and if it is provided, we will re-open the report. However if no more information is provided it will remain closed and your problem will not be investigated.

    As always, please read how to report bugs to ensure we can help you as quickly and efficiently as possible. Thank you for taking the time to report bugs but please make sure you provide enough information for us to actually help you!

  • Can you try with Chrome Canary (currently version 23) and let me know if there's still a problem there? Also, do you have any Chrome extensions/addons installed and if so does disabling them fix it?

  • Your .capx uses the Touch2 third party plugin. Please see how to report bugs - can you repost without a third party plugin?

  • I still cannot reproduce an issue. Have you tried Chrome Canary? I have noticed a couple of issues in rendering in the latest Chrome, which are fixed in Canary, so it might be a browser bug.

  • Can anyone provide a .capx not using third party plugins that reproduces this issue? Otherwise I will close the report.