Search Issue Tracker
Won't Fix
Won't Fix in 1.4.X
Votes
0
Found in [Package]
1.4.2
Issue ID
OXRB-87
Regression
No
Crash on SetDebugLogWrapperPointer when using SteamVR with Zibra Liquid Asset
Reproduction steps:
- Open the user's attached project
- Enter Play mode
Expected result: Play mode is entered
Actual result: Crash
Reproduced with: 1.4.2 (2020.3.41f1, 2021.3.12f1, 2022.1.20f1, 2022.2.0b12, 2023.1.0a15)
Reproducible on: Windows 11
First few stack frames:
0x00007FF86B58D3F6 (ZibraFluidNative_Win_Editor) SetDebugLogWrapperPointer
0x00007FF86B589C87 (ZibraFluidNative_Win_Editor) SetDebugLogWrapperPointer
0x00007FF86B589DE5 (ZibraFluidNative_Win_Editor) SetDebugLogWrapperPointer
0x00007FF86DEF8719 (Unity) GfxDevice::InsertCustomMarkerCallbackAndDataWithFlags
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
The callstack indicates this issue is coming from Zibra. Please reach out to the creator of that asset to get support for this issue.
Resolution Note (1.4.X):
The callstack indicates this issue is coming from Zibra. Please reach out to the creator of that asset to get support for this issue.