WebGL - Buffer limit exceeded.

[CabbageWarrior]

Hi everyone!
I'm using Nova UI for a cross-platform project (Android/Quest - WebGL) and I found an error when I have complex interfaces in my scene that break the tool.
The problem happens only in WebGL builds.

Problem is in "ShaderBuffer" class at line 47.
texture = new Texture2D(textureWidth, 1, TextureFormat.RGBAFloat, false, true);

The error is "Buffer limit exceeded" and that's because the calculated texture width is over 18k while the buffer limit is near to 16-17k.
It seems to depend on how many blocks are rendering. Problem is: I've not finished to implement all the UI I need yet, so I can't try to find a temporary workaround.

Now I'm in the situation that I have few days before the delivery of my project and this bug exploded in front of my face yesterday. That was a fantastic discovery! 😂

I sent a mail to your contact address with a sample project.

Unity version: 2022.3.1f1

Hope to hearing some news!

Thank you for your support!

[adgray1]

Hi!

We'll do our best to investigate this promptly, but it sounds like you're on a tight deadline, and we cannot guarantee we'll be able to provide a fix within your preferred timeframe - as the fix is currently unknown and could be more involved than changing only a couple lines of code.

For that reason, your best bet in the short term is to find ways to simplify your UI. A few tips that could be useful:

1. Replace all UIBlock2Ds which don't render anything to regular UIBlocks (this will reduce the amount of data passed to the shaders)
2. Remove any unnecessary nested UIBlock2D "container" elements (e.g. nested containers in the hierarchy there purely for organization)
3. Reduce the number of simultaneously enabled UIBlocks (of all types). In the project you shared with us, it looks like you have multiple "panels" rendering over each other (e.g. UIEvent-Root and TabletPanelAssets-WebGL). If the background panel can be disabled while the foreground panel is visible (and vice versa), that's worth doing.

Thank you for bringing this issue to our attention. We'll be sure to follow up once we have more information/guidance to offer!

[adgray1]

One follow up question I left out:

In the project you shared, what's the difference between the "working" and "not working" builds? Does the "not working" build have a few extra UIBlocks or is it something else?

Edit:
Apologies, I believe you do say in your email that the "not working" build has the "PopUp" object enabled in the scene. My mistake!

[CabbageWarrior]

No problem at all! Thank you for your time and your suggestions!

My team and I will try to simplify our stuff, hoping to hear some good news about this issue. We are rooting for you!

[dkonik]

We believe we have a fix and emailed you a patch. We are still validating the fix ourselves, but we wanted to unblock you as soon as possible. We'd really appreciate if you would help us stress test, so be sure to let us know if you hit any issues!

[CabbageWarrior]

Thank you very much! The team tested the fix and it "seems" to work. Now we will make more tests with more UI elements (the one we need, basically) and will come back with news during the next days (or, if something doesn't work, in the moment we notice it 👍🏻 ).

Thanks again, you've been so fast! ❤️

[adgray1]

The fix for this has just been published in Nova v2.1.1!

[CabbageWarrior]

That's fantastic news! Thank you!