Search Issue Tracker
Won't Fix
Won't Fix in 4.4.X
Votes
0
Found in [Package]
4.4.0
Issue ID
XRMB-80
Regression
Yes
Latest xrmanagement breaks performance testing project on Hololens2
Hi team, I am running a performance testing project on Hololens2 with the latest 2022.3.18f1, and it looks like some update from the {{xr.management}} package breaks the project. In UnityPlayer.log I got:
{code:java}
Initialize engine version: 2022.3.18f1 (d29bea25151d)
The referenced script (Unknown) on this Behaviour is missing!
The referenced script on this Behaviour (Game Object '<null>') is missing!
A scripted object (probably ?) has a different serialization layout when loading. (Read 48 bytes but expected 76 bytes)
Did you #ifdef UNITY_EDITOR a section of your serialized properties in any of your scripts?
The referenced script (Unknown) on this Behaviour is missing!
The referenced script on this Behaviour (Game Object '<null>') is missing!
XRGeneral Settings awakening...
UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:Log(Object)
UnityEngine.XR.Management.XRGeneralSettings:Awake(){code}
The project is a private repository provided by Microsoft to collect performance matrices for Hololens2, please direct message me for the entire project; the attachment is the full player log.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
- Resize to Fit option for Import Activity window's Columns does nothing
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (4.4.X):
There are no fixes planned for this Bug