We are experiencing varius issues with virtual buttons.
The symptoms are one or more of the following:
Button not recognized
Button is automatically activated upon launch of the App
Buttons seem to toggle on and off
Buttons on multiple button builds, toggle between themselves randomly.
We have worked on our marker and made sure that the image areas of the button have plenty of detail. Should we try to make a marker of that that local area and test its readability? Or is the whole marker the key and the marker area is only a measured region of the whole and the image in that area is not that importnat.
Is there any issues related to the distance the camera is away from the marker in Unity? If so, is there any rules to apply here?
Is there dependancy on marker size? Scene size in Unity?
Does scaling the marker or the scene have any bearing on this in unity?
Is it better to use a set scale between Unity/Marker and Real World unit? Such as, use a 1 Unity unit to 1mm. If this is the case, what overall size does Vuforia like, in the Unity environment? Lets say our scene is 1000 units. Should our marker be 1000? Should the camera be 1000 units from the marker?
Does a printed marker real world measurement have any influence? Should it be realated to this scale? So if I continue with my example of a marker being 1000 units, should I pring the marker to be a meter wide? what hapens if our graphics go out of this area?
Does the number of pixels of the marker play any factor?
We would very much like to have the ability to have multiple virtual buttons, but we can not get a stable build.
Any advice would be extremely helpful as wel have client demos all this week.
Feel free to PM me.
Thanks
Eric
I have been working on this issue.
I have updated multiple videos with respective virtual buttons. But now the issue now is, everytime onVirtualButtonPress playing same video for multiple virtual buttons.
Any suggestions ?