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.
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.
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.
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?
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.
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. 🙂