Skip to main content
May 10, 2019 6:48 PM UTC
Question

8.4.3.4381 bug, Preview not reading 3D clicks

It seems there is a bug in this latest release, the preview does not seem to register any "Click" actions on 3D object. So I have JS actions for click on 3D images and model items and i can't get any of them to work on the preview, they do work on device.

This is a massive problem for developing experiences. Can anyone else confirm this issue?

 

Looking at the debug window on preview. When i click on a model item all i see is "Tap on twx-dt-view element at pageX = 154, pageY = 123" (with the coords of the click) previously this would display the ID path of the model item you clicked on by default.

11 replies

jmikesellAuthor
May 10, 2019 7:02 PM UTC

So some of my 3D images are clickable in preview but only on part of the image. I can't find and patter to the part that is clickable. Some only work in 1/4 or corner of the image, other work everywhere but one corner.

 

Still nothing for modelItem

May 10, 2019 7:03 PM UTC

Hi @jmikesell 

 

I haven't been able to reproduce this locally - I tested a model, model item, 3D image, 3D label, and 3D gauge click event. All have invoked the JS functions I have tied to the event. 

 

What is your JS function doing? 

jmikesellAuthor
May 10, 2019 7:38 PM UTC

@tmccombie  The function displays a card and changes some visibility. But the first line of the function is a console.log and i don't even see that.

 

So it seems that i can click on modelItems until i play a sequence. My need is specifically showing spare parts info, so I run an explode sequence and then you can touch the parts to get details. I've been using this method for a year across a half dozen experiences without issue.

 

See if you can play a sequence and then click on the parts after the sequence plays but before you reset it. Historically you could click on parts while the sequence was running also.

May 10, 2019 7:59 PM UTC

@jmikesell I just tested this and I am able to click on the parts/modelitems during and after a sequence playback.  

 

Is this happening for all of your projects, or just this one in particular?