Search Issue Tracker
Fixed
Votes
0
Found in [Package]
6.9.1
Issue ID
1179662
Regression
No
Editor crashes when assigning Universal's RP Forward Renderer Data to Custom Render Pipeline
Steps to reproduce:
1. Create a new project
2. Install Universal RP from package manager
3. Create Project View -> Create -> Rendering -> Universal Render Pipeline -> Forward Renderer
4. Assign the generated asset to the 'Custom Render Pipeline' field in the Quality Settings
Expected result: you cannot add Forward Renderer Data to Custom Render Pipeline
Actual result: you can add Forward Renderer Data to Custom Render Pipeline, Editor crashes
Reproduced with: 2019.3.0a10, 2019.3.0a12, 2019.3.0b2, 2020.1.0a1
Not reproduced with: 2019.3.0a9 - can't add Forward Renderer Data to Custom Render Pipeline
Notes:
- Also reproducible with Universal RP 7.0.1 and HDRP Diffusion Profile 6.9.1, 7.0.
========== OUTPUTTING STACK TRACE ==================
0x00000198006372C5 (Mono JIT Code) [C:\buildslave\unity\build\Runtime\Export\RenderPipeline\RenderPipelineAsset.cs:9] UnityEngine.Rendering.RenderPipelineAsset:InternalCreatePipeline ()
0x000001980063717B (Mono JIT Code) [C:\buildslave\unity\build\Runtime\Export\RenderPipeline\RenderPipelineManager.cs:84] UnityEngine.Rendering.RenderPipelineManager:PrepareRenderPipeline (UnityEngine.Rendering.RenderPipelineAsset)
0x00000198006367A3 (Mono JIT Code) [C:\buildslave\unity\build\Runtime\Export\RenderPipeline\RenderPipelineManager.cs:58] UnityEngine.Rendering.RenderPipelineManager:DoRenderLoop_Internal (UnityEngine.Rendering.RenderPipelineAsset,UnityEngine.Camera[],intptr,Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle)
0x0000019800636BF4 (Mono JIT Code) (wrapper runtime-invoke) <Module>:runtime_invoke_void_object_object_intptr_AtomicSafetyHandle (object,intptr,intptr,intptr)
0x00007FF9DA4DC11B (mono-2.0-bdwgc) [c:\users\builduser\builds\tsuywz8z\0\vm\mono\mono\mini\mini-runtime.c:2809] mono_jit_runtime_invoke
<...>
========== END OF STACKTRACE ===========
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Add comment