Closed DmitriyYukhanov closed 12 years ago
I'll take a proper look when I get home next week (And i'll have access to an ipad for ios testing on the 18th/19th).
Quickly looking at Hole.initObj(), can you tell if it's definately a PivotJoint issue on iOS, and not perhaps the bodiesUnderPoint returning an empty list, so bodies.at(0) is null (/error in debug swc)? (Just to track it down further before I can test on iOS and try to find a workaround)
Yeah, sure I'll look into it and post here if it will be something else!
Hi, how to progress?
I'm still trying to find time to look into this (I have upcoming exams) but it is still on my mind I've not forgotten about it :P
Hi, how to exams? =)
I've got 3 exams tomorrow, thursday and friday, then I should have time this weekend to try and look into this :)
Hi! What's new?
When I tried it out myself I couldn't find any problem with pivot joint not working on ad-hoc. I have my last 2 exams in next 3 days and then i'm FREE. So if you could maybe produce a small example I can compile (without dependencies) and see it broken I can try and find a work around to get aruond the adobe bug.
Closing unless a new report is made.
Hey, Luca! Here it is, report about broken PivotJoint in the ad-hoc packaged iOS app)
Please, feel free to compile this sources both for desktop and mobile (using ad-hoc packaging): http://codestage.ru/dump/nape/Nape_bug.zip
You should see one PivotJoint is broken and the bottom girder swings on one working PivotJoint left in ad-hoc build and how girder is fixed by two PivotJoints on desktop.
The broken PivotJoint is created at Hole.initObj();
Looks like it's another Adobe iOS packager issue, like it was with callbacks recently =(