Hi, that issue was fixed for 3.2.2 version, I marked the ticket as resolved.

Also when running this: https://www.noesisengine.com/xamltoy/8b ... aee192e2bd, the font disappears when DropShadow effect is present.

And this is related to the same issue I explained before. With the new algorithm the result is ok:
.

Hi Otter, The problem with WorldUI in combination with Effects was a known issue we've been working to solve for the next release. It has nothing to do with PPAA, the problem was that 3D transformations were not taken into account when generating the offscreen textures, so could be using smaller siz...

Do you know when you might be able to provide this? Not for the upcoming version, probably next one. by making the "Resources" property public I think there is no problem on making that property public in the extension as it is only for Blend, so I generated a new Noesis.GUI.Extenssion Nu...

Hi Sam, We've been looking at our current implementation of the Loc extension and as you noticed there is something we have missing. The extension should be able to detect changes in the localization dictionary, and update the target properties automatically. This mechanism is similar to what Dynami...

Hello, I just installed NoesisGUI 3.2.1 in a empty Unity project, imported the World Space UI sample, opened the WorldSpaceUI-blend solution in Blend, build the project in Blend (Build > Build Solution (F7)), and everything appears to be correct. I got no errors in the designer and I can hit Debug >...

It is strange, I was able to reproduce the problem and the patch fixed it.
Could you please attach some example in the ticket that reproduces it for you? I might have something different in my test project.

for more explain, when i create a UserControl from Tools/NoesisGuI/Create , and reference that in mainwindow.xaml , blend gives error that the UserControl does not exist If you work with a Blend project, it is better if you create all the controls directly in Blend (right-click project > Add > User...

Please let us know if you find any issues.
Glad to help.

In my case I don't want to do this as I would need to create about 30 Dependency properties if I want to do it this way. That's a bit too many for my liking. In my example the Name property was not intended to be a DependencyProperty, just a CLR property of the PlayerData instance. But if those pro...