New warning about texture parameter support in 2021.3.10

I just updated from 2021.3.9 to .10, and was greeted with these:

A whole lot of shaders log this:
WindowsPlayer "Tijmen-Lenovo" Shader 'Hidden/TerrainEngine/Details/Vertexlit' uses 153 texture parameters, more than the 64 supported by the current graphics device.

I dont really understand whats going on, i highly doubt we are using 3000 textures in a single shader. Especially PostProcessing Uber which is the builtin PostFx v2. Using builtin pipeline.

1 Like

Tried deleting the library folder to reimport the project?

The update from .9 to .10 was quite quick, back as well. It didnt reimport everything, nor do i really want it to.

Hi. I have the same issue on iOS.
It started in 2021.3.10 and it results in incorrectly displayed assets loaded from asset bundles.

8470319--1125572--Screenshot 2022-09-27 at 21.25.20.png

Hi, can you file a bug on this with a repro project?

I too have the same issue.
I have updated Unity/HDRP from 2020.3.17 to 2022.1.16.
The warnings occur when assets are loaded from asset bundles which were built with the older version Unity.

1 Like

[quote=“Cherio4”, post:6, topic: 894776]
I too have the same issue.
I have updated Unity/HDRP from 2020.3.17 to 2022.1.16.
The warnings occur when assets are loaded from asset bundles which were built with the older version Unity.
[/quote]

I can confirm this. Additionally, assetbundles I built in 2021.3.8f1 seem to crash the application when I try to load them in 2021.3.11f1. Anyone else running into this as well?

Same problem loading assetbundles created with Unity 2022.1.10 into Unity 2022.1.12 / 13 / 14 / 15 / 16 / 17 / 18 / 19 and 2022.2.0.b10

Is a serious problem as many assets cannot be re-exported

Please submit a bug report and mention the bug number in this thread. We'll ask QA to prioritise it.

bug report submitted IN-19665

[quote=“aleksandrk”, post:9, topic: 894776]
Please submit a bug report and mention the bug number in this thread. We’ll ask QA to prioritise it.
[/quote]

3 Likes

Hello, Is there any update in this subject?
assetbundles I built in 2021.3.8f1 seem to crash the application when I try to load them in 2021.3.11f1

I have the same problem. Both old asset bundles and addressables are crashing iOS application

1 Like

Hello!
I have just found the culprit. A fix is on its way - hopefully it will be there in 2-3 weeks in 2021.3.

3 Likes

Hello, is fix available in https://unity3d.com/unity/whats-new/2021.3.13? I don't see anything related with bundles on the list of fixes

[quote=“aleksandrk”, post:12, topic: 894776]
Hello!
I have just found the culprit. A fix is on its way - hopefully it will be there in 2-3 weeks in 2021.3.
[/quote]

Happen also with WebGL using Unity 2021.3.13f. In the web browser console:

I've been on 2022.1.10f1 for a while because of this bug as well. I'm pretty sure 2022.1.11f1 and up was when I started seeing it.

Hi! A fix will be available in 2023.1.0a19; backports are in the queue.

[quote=“aleksandrk”, post:16, topic: 894776]
Hi! A fix will be available in 2023.1.0a19; backports are in the queue.
[/quote]
Hi, can you elaborate on “in the queue”? How long will it take? This is a pretty severe issue in a LTS, causing lots of trouble for users doing an update of a minor LTS version, which should be absolutely safe.

"In the queue" means PRs are prepared and are going through the PR landing process. It usually takes around 2-3 weeks before a public version is available after the PR lands.

If you rebuild your shaders/asset bundles (clear the Library/ShaderCache folder), the issue will go away.

[quote=“aleksandrk”, post:18, topic: 894776]
“In the queue” means PRs are prepared and are going through the PR landing process. It usually takes around 2-3 weeks before a public version is available after the PR lands.

If you rebuild your shaders/asset bundles (clear the Library/ShaderCache folder), the issue will go away.
[/quote]
we have hundreds of asset bundles, created from Prefabs. Rebuilding would take quite some time. Also, deleting Library folder would not trigger a rebuild of those, I guess?

Actually, you don't have to clear the shader cache, sorry for misinformation.
You just need to rebuild the bundles.

Alternatively, you can wait for the patch that has the fix.