Instancing: 'unity_RenderingLayer' shares the same constant buffer offset with 'unity_LODFade

hello any one have a idea what this one is
Unity 2021.2.3 URP api 12.1.1

Code (CSharp):

1. Instancing: Property 'unity_RenderingLayer' shares the same constant buffer offset with 'unity_LODFade'. Ignoring.
2. UnityEngine.Experimental.Rendering.ScriptableRuntimeReflectionSystemWrapper:Internal_ScriptableRuntimeReflectionSystemWrapper_TickRealtimeProbes (bool&)

looking at cross fade "multi_compile _ LOD_FADE_CROSSFADE" is the same as api 10x and 12x added "multi_compile_vertex LOD_FADE_PERCENTAGE"

what did i miss as i did not have this error in 2021.2.2

 

not certain yet about the path to replicate this yet

 

@aleksandrk
(Case 1385456) Instancing: Property 'unity_RenderingLayer' shares the same constant buffer offset with 'unity_LODFade'

Unity 2021.2.4 URP api 12.1.1

finally narrowed this down a little

seams to be related to the combination of:
instancing_options renderinglayer
multi_compile_vertex LOD_FADE_PERCENTAGE

 

the fix could be found in updating Visual studio 2022 and recompile

 

follow up

had some time to look at this again
i found this was due to a change in #pragma

#pragma instancing_options renderinglayer

change
#pragma instancing_options assumeuniformscaling nomatrices nolightprobe nolightmap

use of the correct #pragma should fix if any one reads this thread later

cheers

 

bug reproduced in urp 13 and hdrp 13. so it not fixed yet

 

i suggest you file a new bug report so Unity QA can follow up
perhaps you can reference case number (Case 1385456) for QA to find the detail history when you submit the new report

case Number from before has already been closed

 

changed from "pragma multi_compile _ LOD_FADE_CROSSFADE" to "pragma multi_compile_fragment _ LOD_FADE_CROSSFADE"

pragma multi_compile_fragment _ LOD_FADE_CROSSFADE that is now found in api 14x also has the same problems about sharing the same command buffer

compile was found using VS 2022_17.2.1

note URP 12x terrain used in forward pass and Gbuffer
#pragma instancing_options norenderinglayer assumeuniformscaling nomatrices nolightprobe nolightmap

however it may need to be ?
#pragma instancing_options assumeuniformscaling nomatrices nolightprobe nolightmap

the section for norenderinglayer seems to be part of the problem

 

Still seems to be a problem with Unity 2021.3.7f1 (and Visual Studio 2019)...effectively makes light layers unusable...

 

QA recommended update VS

with URP just keep using pragma multi_compile _ LOD_FADE_CROSSFADE
when you get to api 14.0.3 and higher it can change to the fragment ok

in 15x i think they will add
#include "Packages/com.unity.render-pipelines.universal/ShaderLibrary/LODCrossFade.hlsl

 

Thanks DDE...just to clarify, do you know if Visual Studio 2022 is "officially" supported for use with Unity (and if so for which Unity versions)? I tried doing a general search for this but couldn't find anything definite...

 

works for me ok
Code Editor Package for Visual Studio | Visual Studio Editor | 2.0.16 (unity3d.com)



other reported some problems but it seems only a few had issues hit and miss
Visual Studio 2022 and Unity - Unity Forum

 

Thank you!

 

Same message suddenly appeared in my project 2021.3.24 & .25
Any solution for this? Or pointers where to look?

My message says:
Instancing: Property 'unity_RenderingLayer' shares the same constant buffer offset with 'unity_LODFade'. Ignoring.
UnityEngine.GUIUtilityrocessEvent (int,intptr,bool&)

Have tried recompiling, using VS 2019 & VS 2022, rebuild library etc. But still I get the message in the editor. Sometimes 4500 times in a few seconds, than it keeps on that number. Unless you do play, then it always reappears.

 

I'm getting this error after updating from Unity 2021 to Unity 2022. I have the latest package and updated VS and tried pragma multi_compile_fragment _ LOD_FADE_CROSSFADE.

Any other advice to get this to stop? Thanks!