Revolute Joints not working in CocoonJS

Bugs will be moved here once resolved.

Post » Sat Jul 13, 2013 1:49 am

---UPDATE---
No need to read what's below the double line anymore... the error has gone with r138.2

Now I just have the same issue left like described here...
http://www.scirra.com/forum/cocoonjs-black-screen_topic63349_post435707.html#435707

Hope this will be gone soon with some CocoonJS update.
Or is there another solution?

BTW: how/where can I switch to the other physics-engine?

Cheers, Mig




------------
------------

Hi, I am posting this here just to let you know about an annoying bug that prevents me from getting my game working on mobile via CocoonJS.
It might be Ludei's responsibilty as the problem only appears when launching with CocoonJS, but who knows.

I basically just want to rotate an object around a hotspot using forces/impulses. Sounds simple and easy, and it works on the PC (Firefox) just as expected.


Link to .capx file (required!):
http://projects.migmarn.com/public/revolute_test.capx
http://projects.migmarn.com/public/revolute_test.zip (not minified)

Steps to reproduce:
1. Launch zip-file in Android CocoonJS launcher.

Observed result:
In the debug console it will show error messages indicating that something with revolute joints doesn't work. Then only black screen. As soon as the revolute action is removed/disabled error doesn't appear.

Expected result:
Gravity should affect the large rectangle and rotate it around hotspot 1 (on the right). It works as expected in firefox on the desktop (run capx to see yourself)


Browsers affected:
Android CocoonJS

Construct 2 version:
beta r136; but I've had this issue before with stable version r132 as well


Would be great if you could check it for yourself and give me feedback, or even help me to find some possible workaround.

Thanks for any help, MigMarsmanmig2013-07-13 02:21:05
B
9
S
2
Posts: 12
Reputation: 1,125

Post » Sat Jul 13, 2013 1:56 pm

In your update to r138 it states:
"CocoonJS: accelerated physics will now work with applying forces and torque when the next CocoonJS launcher comes out"

Since there were 6 months between cocoonjs 1.3 and 1.4 is it possible it might take another 6 months until this physics issue is fixed?

That would be very depressing. Am still hoping for some quicker solution. Marsmanmig2013-07-13 13:57:22
B
9
S
2
Posts: 12
Reputation: 1,125


Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 1 guest