Thanks for the report, I continued the conversation there, with a proposal to solve your issue.

View instances are resource-intensive, so we always recommend creating as few as possible. In your case, a single View is sufficient, and you can dynamically update the root content using code. To load each screen, you can use Noesis::GUI::LoadXaml(PATH_TO_XAML). Please refer to our C++ examples for...

Could you please create a ticket for this (make it private if necessary) and attach a link to the capture? If the file exceeds the attachment limits in the tracker, you'll need to upload it elsewhere and share the link

This is not implemented/supported. Could you please file a ticket?

Add this line to the root of your XAML:
And your binding will start to work.

Great! Marking this as solved

Hello, regarding the clipping issue, could you clarify whether this is a render to texture or a render directly to the camera? It seems that the stencil bits may be missing on the surface.

Could you also attach a RenderDoc capture of the frame so we can investigate further?

The challenge is that multiple input devices (keyboard, mouse, touch, gamepad) can be used simultaneously in Noesis, making it difficult to provide a single listener that handles all possible corner cases in your game. I believe this issue should be addressed on the integration side of Noesis. Since...

Let's assume that I have a list of images that I would like to use when needed as Binding with image path value .

If these images are not directly referenced in any XAML (as appears to be the case here), you'll need to manually inject their dependencies (as described above) for each one.

1 - The proposed code seems to solve the first problem https://www.noesisengine.com/bugs/view.php?id=3476#c9787 Will this code be included in any future updates or do I have to do this myself in every update? Please, file a ticket about this and we will think about it. 2 - I still don't understand ...