Problem Description

System Reset persisted objects action is duplicating persisted objects, recreating persist objects that should be destroyed after second or more restart of layout.

Attach a Capx

Yeah

[attachment=0:1jbbooec][/attachment:1jbbooec]

Description of Capx

Contains an object "PersistObject" with Persist behavior, Textbuttons to Reset persisted objects and to Restart layout, Text with description of other bugs in Reset persisted objects action on the margins, Double click somewhere in the project to create PersistObject, objects can be dragged with mouse, Text to show dragged items UID & IID.

Steps to Reproduce Bug

• Open project and preview it with debugger
• Look how much instances of "PersistObject" you have, should be 1 - #0
• Click Reset persisted objects, then Restart layout, then click Restart layout again

Observed Result

Look at the debugger, now we have 2 instances #0 and #1, if you move the object in preview before the restart, the object will go back to it's initial place after restart, but after second restart, another object appears on the place where the initial object was before first restart.

The #0 and #1 have identical UID.

Expected Result

After restarts, the objects staying at their initial state, the initially non existed objects still not exist, persisted objects are on their initial places and nothing is duplicated.

Affected Browsers

• Chrome: (YES)
• FireFox: (YES/NO)
• Internet Explorer: (YES/NO)

Operating System and Service Pack

Windows 7 64bit with latest updates and latest drivers.

Construct 2 Version ID

r191

Why not release it for iOS 8+? It's only a matter of time before it reaches the vast majority of users. It's already up to 60% on latest figures. If you choose to support iOS 7 you will have to deal with wrappers which have some pretty difficult compatibility issues.

Hello Ashley, if i choose iOS 8 export, what can you say about new webview+ from ludei? As i understand, it's a wkwebview, even phonegap will use it (later), is it good? Maybe this can resolve troubles with cocoonjs? I mean, the wkwebview is the only export option for heavy games, the other option is canvas+ (buggy and deprecated) or phonegap with wkwebview, but nobody knows when phonegap will switch to wkwebview. So, what you can say about it?

• iOS ARM64 support
• Enabled WV+ on 64 bit devices

Yeah, i wait so long for that moment.

Hello,

I am afraid it is not currently in our roadmap, and right now it is not one of our priorities as we are about publishing a new release. I am sorry for the bad news.

Regards.

A new release of a plugin or a new cloud compiler?

You don't need it to publish, you just need to be specific in your targeted device in the App description itself as well as the testing notes to Apple.

ie. Designed for iPhone 5s, iPhone 6/Plus and iPads with Retina Display.

They accept it if you are very clear about it.

Wow, i didn't know that, thanks for the info.

iOS8 adoption is coming along great.. let's hope the audio issue is resolved soon!

Since it was running so fast, I thought I'd up the ante a bit and add in more parallax layers, effects and proper trails:

Subscribe to Construct videos now

Still running crazy fast on iOS. It can take more! O_o

Very exciting times for C2 mobile devs, we can essentially make a full blown PC quality game without fear of it running like a slideshow.

What about iphone 4s? Have you tried it? It's not so fast as ipad mini 2, but i thought that you need to support it to publish your game to appstore.

Could I ask a question, I though that webview+, and canvas+ are actually working with the html5 export itself, is that so?

If so, official support from scirra of webview+ itself is actually not adding anything, and that would also mean that it would still work long term wise, as webviews are real browser engines (which scirra supports).

True, but sometimes i have troubles with construct2+cocoonjs compatibility and nobody cares, because it's not supported. I just want to say that webview+ is not a buggy technology, it's a system wkwebview, even phonegap will use this stuff (one day, i hope), and for now this is the only export option that can handle heavy games for ios, and even if phonegap will switch to wkwebview, cocoonjs webview+ will still be better for all my games because it supports the cocoonjs native physics. It's not fair that good technology is not supported only because Ludei using in, ludei doesn't create it, apple created the wkwebview and cocoonjs can build our projects with wkwebview. It's working now and it will work with html5 export for sure, because its just a webview, i just want the cocoonjs support back in case of compatibility problems. If you want to say that i shouldnt have any compatibility troubles because webview supports html5 export, i say it's not true, phonegap is a clear webview, but it has different export option to improve compatibility.

You had audio troubles? That implies its fixed now, what happen and how was it fixed?

It is indeed extremely awesome on iOS8+, feels like the JS engine on Apple is much faster than on PC for a low power mobile SOC to handle my game as well as my Intel i5 Ivy Bridge.

Nope, no fix for that, i just removed all sounds for now. And i don't think that this problems is caused by a bug above, because it's a safari bug. It looks like a bug in webview or cocoonjs, but there will be no fix for that i guess, because cocoonjs is not supported.

I had that audio troubles too, but that webview+ is AWESOME, my physics game has even better performance than with canvas+, why scirra still not officially support it? I heard that canvas+ is not good, but if i understand it right the webview+ is apple system's webview, phonegap using it too, but cocoonjs is even better (because cocoonjs using the WKWebView instead of UIWebView).

I thought it is set to Yes in the example, just a mistake there...

I can confirm on r184, i try it on 2 different pc's with latest drivers so i don't think the problem is in the drivers.

is the wkwebview method supported only on ios 8 ?

Yes, it's an iOS 8 API.