TerraSame
commented
4 years ago Update: Wouldn't you know it... Looks like I have this issue licked... I believe after many hours R&D-ing, This is probably my issue caused by lacking direction or maybe lack of my personal research as I Do now have a version of my project working with Unity 2019.2.17f1 and NuGet 2.0.0 and Maps SDK 1.4.2, completely with NO Control Pointer Raycast issue. Finally... Looks like I was not updating properly both NuGet and Maps SDK... Regardless of why, it is very good to see all combined software now playing nice together... Thanks and Happy Holidays to all !
Hello... Firstly, if this bug does not pertain to your Maps SDK but possibly the MRTK please "Point" me in the proper direction to find an answer to cure this issue. Thanks for your guidance...
I have been experimenting to great lengths to get your SDK working in the latest 2019.2.17f1 version. Yes it does work, and it works very well with one exception. But, I must admit that upgrading does not work although, starting a new project from scratch does. So, I have attempted starting from scratch on many 2019.2.... versions, all with the same glitch.
What I am doing is creating multiple scenes where I add interactable buttons in each scene to launch a different scene. The system I created does work perfectly in the 2019.1.4f1 (Approved in your Matrix") I do realize 2019.2..... is not yet approved but the quality of Unity visualization surpasses 2019.1.4f1 so I though I could possibly help you.
In any case, the problem is that upon clicking my scene switch button, the Control Pointer Ray changes and goes inactive until I bring up the UWP menu and then close it where the Pointed Ray is then fine until I click another Scene switch button upon the same pointer problem arises again.
Attached you will find a picture showing what happens to the Control Pointer Ray. The dotted line is the original raycast line and the curved raycast line gets added and I suppose it is a parabola ray cast, somehow added.
I am using the Samsung HMD for design and layout and I have not yet pushed my 2019.2.17f1 project to my HoloLens but I have done so with my 2019.1.4f1 version to the HoloLens where it works pretty good but not the quality of 2019.2.17f1. I have been experiencing crashes with all versions on the HMD and HoloLens where there are NO crashes in the Unity editor. Strange...….. I wonder why this is???
I have been fighting these Crashes and Control Pointed issues for about two weeks now, I don't know what is causing either issue. The Pointer Raycast issue does not occur in the 2019.14f1 version of unity but the crashes do after about 6 or seven scene launches.
If I need to get you any data or files I will do my best.
Any advice will be greatly appreciated... Thanks Paul