I have just created #2239 to track all issues and ideas for Hot-Reloading

In the past, XAML reloading was disabled and almost nobody was using it so we couldn't fix many things in real-world scenarios. We decided to change this in 3.1 as hot-reloading is going to be more and more important in future versions. We have the compromise to prioritize all kind of issues related...

Noesis::GUI::LoadXaml should invoke your LoadXaml implementation if the provider is correctly installed.

All our examples use custom XamlProviders, could you please have a look at them?

Thought ya'll might find this useful. I'm just using the GLRenderDevice provided without modifications; not sure what's going on with that last draw call. When we need to render masks, we only render to the stencil buffer. Color buffer is disabled. That explain why your clear was failing. In genera...

Back to my earlier question - can you provide some information about how we would compile to WebAssembly from a .NET Framework project? We do not mind writing post-processing scripts and makefiles if that is what it takes, we just don't know what the toolchain is, nor how to invoke it. I didn't hav...

Yes, definitely. I will do that. Thank you!

It is not only reloading, we also check for errors and more things.

Why do you want to disable it?

Everything is correct but the last point.

Rendering in the Unity screen space does not anti-alias. Non-bitmapped controls don't look good.

Just enabing PPAA in Noesis View should fix this. All our examples should render without AA artifacts. If you don't get that, something is wrong.

Probably you have Vulkan renderer enabled. Right now, it is not supported. You need to activate OpenGL ES. We are working on this, sorry for the inconvenience.

Yeah, sorry, an executable is not an option. We need one of this:

• A renderdoc capture showing the issue
• A xaml reproducing the issue in XamlPlayer
• A minor modification (patch) to one of our examples reproducing the issue.