Android and IOS wrong MouseEvent3D Z order

[SharpEdgeMarshall]

Only on Android and IOS if you have for example a box on a plane and click on the box, the mouseevent3D will always target the plane.

So the issue is concerning MouseEvent3D with overlapping object.

[SharpEdgeMarshall]

After 1 hour of debugging there are some news:
the problem it's due to this call context.drawToBitmapData(pixel); at line 806 of View.as, on the PC it draw some colours on Android it's setting all the pixels to 0 and then from what i've understood the code it's not able to generate Depth so the plane comes in front of the box in the mouseEventProcessing.

Ok and now i don't know how to solve this...

P.S. sorry for bad english

[Yaski]

Ok. Thanks for clarification. We will check how drawToBitmapData works on mobile devices.

[SharpEdgeMarshall]

Thank you, i think alternativa is a powerfull engine, it's working very well on mobile except this bug.

[kojot1234]

I'm still debugging it to get to the bottom of this bug. That's also as far as I got.

Line 835: var color:int = pixel.getPixel(k, 0);

Always returns 0.

[SharpEdgeMarshall]

no news about this issue?

[makc]

if you have simple geometry (you probably do, on mobile) you could try casting ray instead of listening to mouse events.

[kojot1234]

It's a very common issue in the forums, how can this issue be resolved is Alternativa3D problem or Adobe's?

[SharpEdgeMarshall]

var color:int = pixel.getPixel(k, 0);
returns zero because the var pixel is black,
this is due to the call to context.drawToBitmapData(pixel); at line 806 as i said.
adobe or alternativa problem? i don't know
if yaski could tell us what influence drawToBitmapData i could investagate furter...

[cervantez]

Any status updates on this one? Tested it in away3d and they don´t have that problem. Different approach? Probably.

[Yaski]

Please answer a question in facebook
https://www.facebook.com/questions/466603040039559/

[SharpEdgeMarshall]

any news?
The survey result seems clear we need Alternativa3D on mobile!! :)

[Yaski]

Yes, i agree with you. We will work in this direction.

[makc]

9 months ago

it's time )

[kojot1234]

There haven't been any commits lately, I just have a feeling that Alternativa3D will be abandoned. I just hope not.

[62316e]

There haven't been any commits lately, I just have a feeling that Alternativa3D will be abandoned. I just hope not.
Looks like Away3D has better support so its time to move forward...

[ChrisDenham]

Yeah, it's all looking a bit unloved in here. :-(
It's a shame, as this "MouseEvent3D on mobile platforms" problem seems to be our biggest outstanding issue with Alternativa3D. My current workaround is to use ray geometry intersection but it's way to slow unless you drastically simplify the geometries and/or perform intersections with low detail LOD nodes, which from a user perspective is a bit crap because they sometimes get unexpected intersection results because of the mismatch between visible and intersecting geometry.

[makc]

My current workaround is to use ray geometry intersection but it's way to slow

There is #59 that should solve this part.

[ChrisDenham]

Thanks makc, I will take a look at #59
It hadn't occurred to me that this pull request might help speed up ray intersection.

[62316e]

Any results?

[gonchar]

in process...

[62316e]

Still in process?

On Thu, May 23, 2013 at 3:33 PM, Sergey Gonchar [email protected]:

in process...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-18340170
.

Sent from my gmail.

[Heterfire]

Any results?Is it abandoned?

[makc]

Is it abandoned?

Do you mean the engine?

[Heterfire]

Yes, I've been waiting for version fixes the IOS system has been bothering me.

[makc]

The thing is noone really knows what causes the bug. It takes quite a time to research and find the cause, so if someone could give a clear picture of the problem (and not just "there are wrong colors in the bitmap"), fix will be done quickly. Otherwise, you need to wait for someone, who wants to use the engine on device and willing to spend time in debugger, to appear.