DYNAMIC_VB_SIZE in RenderDevice.h is not enough for some complex situation.

10 Apr 2025, 03:51

Hi

We using NoesisGUI to edit floor plan, when there are too many drawings in the floor plan, the App will crashed. After some debug, we double the DYNAMIC_VB_SIZE and compile the SDK ourself fixed the bug. Is there a way that we can fix the issue but do not compile the SDK when update to a new version?

Thanks.

10 Apr 2025, 20:18

Modifying DYNAMIC_VB_SIZE is delicate, as it's tied to many dependencies and optimizations across all renderers.

Could you please create a ticket and share the crashing XAML? I'd be happy to take a look.

bemedom277 · 19 Apr 2025, 06:05

Hi

We using NoesisGUI to edit floor plan, when there are too many drawings in the floor plan, the App will crashed. After some debug, we double the DYNAMIC_VB_SIZE and compile the SDK ourself fixed the bug. Is there a way that we can fix the issue but do not compile the SDK when update to a new version?
mapquest directions
Thanks.

We encountered the same issue with large floor plans and resolved it by doubling DYNAMIC_VB_SIZE, but would love to know if there's a supported way to configure this without modifying and recompiling the SDK every time.

21 Apr 2025, 12:56

Could you please share a XAML sample that reproduces the issue? It will help us better understand what's going on before we suggest a solution.

Also, please create a ticket for it so we can track it properly.

DYNAMIC_VB_SIZE in RenderDevice.h is not enough for some complex situation.

DYNAMIC_VB_SIZE in RenderDevice.h is not enough for some complex situation.

Re: DYNAMIC_VB_SIZE in RenderDevice.h is not enough for some complex situation.

Re: DYNAMIC_VB_SIZE in RenderDevice.h is not enough for some complex situation.

Re: DYNAMIC_VB_SIZE in RenderDevice.h is not enough for some complex situation.

Who is online