Give us as much detail as possible regarding the issue you're experiencing:
Unity Editor version:2022.3.12f1 ML2 OS version:1.7.0 Unity SDK version:1.12.1 Host OS: Windows
Error messages from logs (syntax-highlighting is supported via Markdown): None
Hello,
I'm having trouble rendering the unity scene onto my ML2 headset while using App Simulator on the MLHub. If I open up scene view and enable gizmos, I'm able to observe the camera frustum and controller position+ray moving around as I move my head and the controller, but no elements from the scene appear on the headset.
When I build and run the unity app onto my ML2 headset, the scene works as normal. I would, however, prefer to use App Simulator for faster iteration.
Has anybody run into a similar problem before? Could it be a hardware related issue?
In isolation, everything appears to be working.
The virtual simulator appears to launch just fine with the 1.7.0 sdk, the magic leap 2 appears to connect to the PC via MLHub just fine and app simulator is able to launch.
The unity scene also appears to run just fine with no errors. I was testing it out with the simple scene tutorial with the single cube so there really shouldn't be any issues with the way the unity scene was set up.
The issue lies in the fact that everything seems to be working correctly yet the magic leap 2 is unable to render the unity scene or have the headset movement be reflected in the camera view (in the game view window in the unity editor). This would be my second time setting up a magic leap 2 workflow from the initial tutorial, but I never ran into this particular problem with the other magic leap 2.
If you are using the App Simulator Unity package, do you mind capturing the logs after reproducing the issue? The Logs can be captured by selecting Magic Leap > Save Diagnostics Logs
Hi,
I'm using the app simulator through the magic leap hub. I never ran into any errors while using it aside from the ADB errors I get when closing the unity project and leaving the app simulator instance running. I've attached the diagnostic logs to this reply: NoSceneRenderingOutputLog.zip (637.1 KB)
Update: I had someone else try out the same scene on a different computer and they had the exact same issue with the unity scene view accurately reflecting what is happening in the scene during runtime but the display in the ML2 stuck on the "App simulator is running. Launch a Unity scene..." window.
I tried using the app simulator unity package and it seems to work the first time I run the scene upon starting Unity. If I try to stop and start the scene again, I run into the same issue I had with the MLHub based app simulator. One error message I am running into on subsequent scene runs is:
Do you mind clearing your Library package cache folder and making sure that the Magic Leap App Simulator is the only XR Devices selecting in the Project Settings > XR Plug-in Management , under the standalone tab?
Additionally, please note that the App Simulator is deprecated and is no longer supported. We strongly recommend using other methods such as Unity’s XRI simulator since we are no longer developing or updating the MLSDK App Simulator.
