Search Issue Tracker
Duplicate
Votes
0
Found in
2018.4.4f1
Issue ID
1209064
Regression
No
When exiting and returning to Holographic Remoting Player on HL2, Unity 2018 LTS crashed
DESCRIPTION
When exiting and returning to Holographic Remoting Player on HL2, Unity 2018 LTS crashed.
NOTES
Bug I was expecting was to be still connected, but not see app.
https://docs.microsoft.com/en-us/windows/mixed-reality/holograms-100
Did not see this 1912 B week.
WORKAROUND
N/A
IMPACT
Low – This is not an expected workflow
MACHINE NAME
900066791656
REPRO STEPS
1. Flash a HL2 to latest build, complete OOBE, download Holographic Remoting Player
2. Use a previously created app in 2018 LTS for a generic cube. (or new one via guide above)
3. When you reach the Holographic window, change to HL2, type in your IP
4. On device launch Remoting Player.
5. In Unity hit Connect
6. On device, go to start, go to Mixed reality home.
7. Return to the app.
8. Observe on PC Unity crashes
ACTUAL RESEULTS
Unity crashes
EXPECTED RESULTS
HL2 returns to default app screen, and Unity is still running
REPRO RATE
3/3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
Add comment