test: reuse UnityChan assets in our sample folder for HdrpGraphicsTest-2022.3 and HdrpGraphicsTest-6000.0

[sindharta]

No description provided.

[karasusan]

I got the shader error when opening the ToonShader scene in the HdrpGraphicsTest-6000.0 project on Unity Editor 6000.0.50f1.
No error when opening the HdrpGraphicsTest-2022.3 project.

Shader error in 'Toon': undeclared identifier 'unity_MipmapStreaming_DebugTex_ST' at /com.unity.toonshader/TestProjects/HdrpGraphicsTest-6000.0/Library/PackageCache/com.unity.render-pipelines.high-definition@4a7a2c416b77/Runtime/Material/Lit/LitData.hlsl(299) (on d3d11)

Compiling Subshader: 0, Pass: GBuffer, Vertex program with DEBUG_DISPLAY DECALS_3RT
Platform defines: SHADER_API_DESKTOP UNITY_ENABLE_DETAIL_NORMALMAP UNITY_ENABLE_REFLECTION_BUFFERS UNITY_LIGHTMAP_FULL_HDR UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_PBS_USE_BRDF1 UNITY_PLATFORM_SUPPORTS_DEPTH_FETCH UNITY_SPECCUBE_BLENDING UNITY_SPECCUBE_BOX_PROJECTION UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS
Disabled keywords: DECALS_4RT DECALS_OFF DIRLIGHTMAP_COMBINED DOTS_INSTANCING_ON DYNAMICLIGHTMAP_ON LIGHTMAP_ON LIGHT_LAYERS SHADER_API_GLES30 SHADOWS_SHADOWMASK UNITY_ASTC_NORMALMAP_ENCODING UNITY_COLORSPACE_GAMMA UNITY_FRAMEBUFFER_FETCH_AVAILABLE UNITY_HARDWARE_TIER1 UNITY_HARDWARE_TIER2 UNITY_HARDWARE_TIER3 UNITY_LIGHTMAP_DLDR_ENCODING UNITY_LIGHTMAP_RGBM_ENCODING UNITY_METAL_SHADOWS_USE_POINT_FILTERING UNITY_NO_DXT5nm UNITY_NO_SCREENSPACE_SHADOWS UNITY_PBS_USE_BRDF2 UNITY_PBS_USE_BRDF3 UNITY_PRETRANSFORM_TO_DISPLAY_ORIENTATION UNITY_UNIFIED_SHADER_PRECISION_MODEL UNITY_VIRTUAL_TEXTURING

[H3idi-X]

I checked HdrpGraphicsTest-6000.0 with 6000.0.48f1 and haven't seen that kind of error on my site yet. I think that error should be fixed in other PR for 6000.0.50f1.

[H3idi-X]

I tried to reproduce the error using 6000.0.050f1. But I haven't succeeded to reproduced issue.

[sindharta]

@karasusan

I am in favor of H3idi-X's opinion.
Can you try opening with 6000.0.48f1 and see if you still have errors ?

[karasusan]

I wish the cause of the issue were my environment, but it reproduced with 6000.0.48f1.
I'll try to remove the library folder and reimport it.

It doesn’t reproduce on macOS.

[karasusan]

We can also reproduce this issue with "development/v1" branch. So, there's no need to fix this issue in this PR.
I'll make a bug ticket for the issue.