darkstar

Just wanted to query you on one thing, with your method, is there any improvement with your standard web based if you did manage to get accelerated physics to work?

darkstar

I think you figured it out by the looks of things, but just click on the cocoonjs object and once you have selected it, change the physics engine property to standard web based instead of accelerated physics to make sure that your exports will work.

Let me know if you are still stuck, I can always help you out

EyeHawk

Just one query regarding testing the in-app purchases.

How do you obtain the actual file that allows you to test the in app purchase? Must the status be "ready for sale" or "prepare for upload" where and how would I go about doing this?

EyeHawk

Thanks for the info, really appreciate it. I did eventually work that out after pulling all my hair out.

How do you set up your actual Products on Cocoonjs Database?

tumira

Construct R141 is a BETA release, maybe you should revert back to R139 Stable and try that out.

Squirrely1

You never quite solved it did you, because they want the accelerated physics to work and not get a black screen. The Standard web based physics seems to be pretty basic "Solution". Like cvp said, it's a workaround, not a fix. Accelerated physics will boost performance ALOT, thats why we are trying to find a REAL solution.

bump

cvp

I emailed Ludei about this situation we're having, and this was their reply to me

"After some investigations here, we've detected that Construct 2 plugin for physics performs some changes on our JavaScript exception code base.

We're speaking with Ashley from Scirra, because this change makes the physics on Construct 2 unusable, but it's a Construct 2 issue. And it's out of our control.

Thank you."

I have the Latest Cocoonjs Launcher 1.4.1 for IOS, and I have R139. When I change the physics engine to Accelerated I still get a black screen with the exact same error... Any news on this issue?

I just tested the Cocoon 1.4 on Android, and it seems that it loads layout by layout on their. I noticed an increase in performance, however on IOS there is def no increase in performance

When you check the Memory Log it should bring up some form of error surely? Also, I am not entirely convinced that this new 1.4 on IOS is actually Loading Layout by Layout. I notice that when I have a layout with very few sprites, I will still see a poor performance of 7-15fps. This has been a really big disappointment. In all honesty, I can see no noticeable improvement with regards to performance. Does anyone feel the same about this? Or am I just being cynical?