This is probably a silly thing but we locked 3.0.0, we will solve it in 3.0.1. Thanks for your feedback, as always!

I've been doing some tests and it looks like PPAA is not disabled when using effects. I created a xamltoy showing it: https://www.noesisengine.com/xamltoy/44de34a2f908121cca23d6d94885474c
I don't remember changing anything related in our latest releases, but could you please check again to confirm you are still having this issue?

It's broken for both PPAA and MSAA as I've just checked.
The screenshot above is without the drop shadow effect and the MSAA works fine there.

Screenshot at 19-32-15.png (31,361 bytes)   

Screenshot at 19-32-15.png (31,361 bytes)   

Screenshot at 19-31-59.png (38,955 bytes)   

Screenshot at 19-31-59.png (38,955 bytes)   

So those images are using MSAA only, PPAA is not enabled when Views are created, right?
I think it makes more sense to me now, what is happening is that offscreen textures are created without the correct MSAA samples.
Can you check if, before initializing the Renderer, you are calling RenderDevice.SetOffscreenSampleCount() to the appropriate number of samples?

Have you considered using PPAA only or do you need MSAA for anything else in your game?

Hi Sergio,
sorry for the late reply.

We utilize MSAA for a few other features in the game. I always prefer MSAA for NoesisGUI as it doesn't have any side effects (thicker lines). PPAA is fine when MSAA is not available or too expensive to use.

I got a chance to work on this. You're 100% right, the issue is with the OffscreenSampleCount.
The big problem here is that the game allows the player to change MSAA setting on the fly (off/2x/4x/8x). Currently, the Noesis View must be recreated in order to initialize it with new RenderDeviceD3D11 (that has new OffscreenSampleCount). Simply changing OffscreenSampleCount for the existing RenderDeviceD3D11 instance is not enough and I can guess why.

I wish we could change this on the fly as recreating a View object is a big no-no. It causes an issue with a multitude of other systems.
E.g. allowing the call to view.Renderer.Init(renderDeviceD3D11) again after it was already initialized would solve this problem (as I can change device's OffscreenSampleCount and call view.Renderer.Init). Currently, it's not supported as further access to the renderer object results in a memory access violation.

Regards!

I am going to close this, as this is not related to DropShadowEffect.

Let's move the discussion to 0001805