Visual corruption using bgfx-nanovg renderer about bgfx HOT 4 CLOSED

My guess is that with your change example is running out of transient buffers. Solution is to increase size of transient buffers. But that's for user to determine how big transient buffers need to be for their specific use case.

from bgfx.

Thanks for the suggestion, I tried playing with that, but I don't think its the reason.
Looking at getCaps() and getStats() after I submit my rendering, it shows:

caps->limits.transientVbSize is 6291456
caps->limits.transientIbSize is 2097152
stats->transientVbUsed is 1088800
stats->transientIbUsed is 24

So it seems the limits are not being hit even when the bug occurs.
I also tried bumping both transientVbSize and transientIbSize by 10x, but the bug still happens.

from bgfx.

Couple more data points on this bug;

• I tried overallocating all resources by 10x, to check its not a buffer overflow type bug (ie add "size*10" to the realloc calls in nanovg.cpp and nanovg_bgfx.cpp), but the bug still occurs
• I synced the original nanovg repo and build the native example, but did not repro there.

So I think the bug might be somewhere in nanovg_bgfx.cpp

from bgfx.

So I think the bug might be somewhere in nanovg_bgfx.cpp

Scope of NanoVG in bgfx is that example. If there is bug, you can submit fix, but example as is sufficient to demonstrate that bgfx could be used for 2D rendering.

from bgfx.