You are right, DPI-Scaling is not yet implemented for the outer Direct3DUserControl. However, there is a callback method called DisplayProperties_LogicalDpiChanged. The name remains from deprecated DisplayProperties.LogicalDpi, but in fact it uses DisplayInformation.LogicalDpi. Feel free to rename the method and implement your solution in place. Creating a Pull request for your changes would let others participate in your enhancement. Even better would be looking for a solution not to scale the SwapChain in View, but to resize the render area. This reduces calculations and improves picture quality. So I did not implement it, because this might be to much for some users not prefering to have the render area resized by DPI-scaling.

I just offered a Pull-Request renaming the method an adding a

//TODO: handle other value affected by DPI change

Actually if I understand this correctly the solution I described above does exactly that. Currently the element is scalled up by WinRT logical scaling. But if you apply inversed scale on swapChain2.MatrixTransform it will be scalled back to hardware resolution so its effect is canceled out. I tested it on the device and I couldn't see any scaling artifacts.

Thanks for the Pull-Request. I will try to implement this in this method.

Cool :)

I also added a stub for CompositionScaleChanged event. I think you will need it also :)

This should be best visible not on downscaling, but on upscaling. Have you tried this with a scale factor of 2x or 3x. If pixels are still 1:1 crips then, it is perfect :) I think it is save to create a swapChain2 instead of swapChain1 initially. This would make your cast

        var swapChain2 = new SwapChain2(swapChain1.NativePointer);

unnecessary. Also you could try using double or different rounding strategy on the float-values to avoid 1px gap. But you probably know by yourself, and this is fine tuning I would do as a final step.

I have implemented these changes and created a pull request (I'm a GitHub noob, so let me know if this isn't the right way to do publish changes). I've added two sliders on MainPage so you can test with different transformations.

I didn't make it clear in the bug report but what I was originally looking for is implementing this in the Toolkit. It seems more complex to plug this into exisitng architecture so I appreciate if someone could point me in right direction.

I will look at it soon, at first it looks good. Are changes in "SharpDX.sln.DotSettings" really needed?
"XAML SwapChainPanel DirectX interop sample" demonstrates it at

"3. Scale DirectX content smoothly and precisely
This scenario shows how to scale DirectX content in a ScrollViewer control."

But I think even this sample is not completely DPI-Scale aware. Did you try it on your Surface Pro? Same steps should be done but completely in C#. Did you lookup the class where SwapChain1 was defined? You maybe can avoid the cast.