[NC V2.2] iOS Deserialization errors on Graph Awake

This topic has 0 replies, 3 voices, and was last updated 11 years, 1 month ago by pjohalloran.

Viewing 10 posts - 1 through 10 (of 10 total)

Author

Posts
April 15, 2015 at 10:48 am #19120
pjohalloran
Participant
Hi,

Just trying out v2.2 on iOS this morning and i am experiencing some exceptions related to deserialization when the BT starts up. Please see stack traces below.

https://gist.github.com/pjohalloran/b3985419f81ba5485237

Maybe related to my other post http://nodecanvas.com/forums/topic/crash-on-wp8/
April 15, 2015 at 12:19 pm #19129
pjohalloran
Participant
I have tried both solutions suggested in http://nodecanvas.com/forums/topic/nc2-aot-error-on-startup/

The AOTDummy class suggested by Gavalakis and the AddAotCompilations suggested by FullSerializer author jacobdufault.

Neither worked but i think its a deserialization error rather than a AOT error.
April 17, 2015 at 11:23 am #19128
Gavalakis
Keymaster
Hello,

The Script Control tasks and Generic Tasks (the ones showing (T) suffix ) are not supported in iOS right now.
The next version will support Script Control tasks in iOS as well.

Please let me know if you encounter any further issues in iOS when using NC without these kind of tasks.

Thanks.
April 30, 2015 at 4:33 pm #19127
tom
Participant
Hi,

Gavalakis, do you perhaps have an update for us on the upcoming update?
An estimated release date for the next version would be great. We’re trying to figure out if we can count on NC working with Script Control tasks on JIT-less systems sometime early in May or if should start planning for a less optimistic scenario.

Our development plans depend on that so a short update would mean the world to us.

Cheers,
Tom Kaczmarczyk
April 30, 2015 at 4:44 pm #19126
Gavalakis
Keymaster
Hello Tom,

In the next release a new set of Script Control tasks will be included that can work on any platform. So if you are targeting multiple platforms that include JIT-less ones, you will be able to use these new ones, else you can still use the old ones as they are quite faster due to how they work, which is not possible in all platforms.

Also, further issues with iOS has been fixed (eg bound variables, fsm callbacks).

I expect to submit the new update within the weekend.

Do you have any other issues with iOS that maybe you’d like to let me know?

Thanks and best regards,
Gavalakis Vaggelis
April 30, 2015 at 6:58 pm #19125
tom
Participant
Excellent, that’s great to know. Thanks for your answer.

We’re targeting XBox One not iOS but the JIT-lessness conundrum seems to be the same for both platforms. Apart from the serialization issues we haven’t found any other problems, but I suppose that might change once we get the game to start after your update. 🙂

I’ll keep you updated and let you know if anything explodes.

Cheers!
Tom
May 6, 2015 at 7:55 pm #19124
tom
Participant
Hi again Gavalakis,

Any news on the 2.3 update?

If you’ve got a release candidate that you’re testing or tweaking for performance, then maybe I could bother you for a pre-release package so that we can get started on our end? We’re under a bit of a time pressure here – we don’t need a production-ready version just yet, but we do need to start testing to check if anything else explodes. 🙂

Cheers!
Tom
May 7, 2015 at 10:05 pm #19123
Gavalakis
Keymaster
Hello Tom,
Sure 🙂 Let me know of an email and I will send it to you earlier.
Thanks!
May 8, 2015 at 11:34 am #19122
tom
Participant
Great! I’m sending you my email address via email to info_at_nodecanvas.com.

Thanks again!
Tom
May 12, 2015 at 7:50 am #19121
Gavalakis
Keymaster
Hello Tom,
I’ve send you the latest version to your email.

Cheers!
Author

Posts

Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.