Search Issue Tracker
Fixed
Fixed in 3.1.0-exp.4
Votes
0
Found in [Package]
3.1.0-exp.3
Issue ID
URS-440
Regression
Yes
[Render Streaming] Unable to intercept Vulkan initialization in a custom graphics plugin when using IUnityGraphicsVulkan
How to reproduce:
1. Open the user's attached "NativeGFXPlugins" project
2. Observe the contents of the "plugin1.log" file with any text editor application
Expected result: The second line in the "plugin1.log" file states "intercepted Vulkan initialization" and the plugin successfully intercepted Vulkan initialization
Actual result: There is no second line in the "plugin1.log" file that states "intercepted Vulkan initialization" or the second line states "Unable to intercept Vulkan initialization" and the plugin has failed to intercept Vulkan initialization
Reproducible with: 2.2.0-preview, 3.1.0-exp.3 (2019.4.38f1, 2020.3.34f1, 2021.3.1f1, 2022.1.0f1), 3.1.0-exp.3 (2022.2.0a11)
Not reproducible with: 2.1.1-preview (2019.4.38f1, 2020.3.34f1, 2021.3.1f1, 2022.1.0f1)
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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Resolution Note (fix version 3.1.0-exp.4):
Fixed in 3.1.0-exp.4