It *should* default to using the discrete GPU (dedicated NVidia) and that's for sure the GPU you want, but that's left up to NVidia's Optimus logic so not sure what version you have installed etc.
Typically 'Run with graphics processor' context menu has to be enabled in NVidia Control Panel.
But what I would do is go into NVidia's control panel and where you see the list of apps, just "Add" XD there, and try forcing to the 960.
Actually I stand corrected - so since our app is a UWP app, I believe XD in this case would default to whatever GPU the desktop windowing system (desktop compositor) is using, in this case it would be Intel.
So I believe if you are successful forcing the NVidia GPU in this case it would potentially mean lower (worse off) performance for you given that there will be an extra resource copy to the compositor's GPU in the end.
Can you give it a whirl and report back what you observe?
I was able to give myself permission to access the WindowsApps folder, and I forced Adobe.XD.exe to use the dedicated GPU. Performance, like you said, was worse.
Is there any the XD dev team could release an update in future where it uses the dedicated GPU instead of Intel? I mean it couldn't be that the GPU is weaker than the Intel onboard graphics? Or it's not that simple?
It's definitely complicated - and there are some UWP (Universal Windows Platform) specific caveats.
I've put an inquiry out to the Microsoft platform team and will answer here if I hear back on any specifics. It's unfortunately not up to our app which GPU we have an affinity for.
But the slowness comes into play because ultimately after we render with the NVidia GPU the OS has to then copy the results over to the other GPU for compositing.
Thanks for taking the time to review this Corey. Appreciate your insights into this matter. Hopefully we'll get to see the day when Adobe XD uses all the power the GPU has to offer like other Adobe apps.
I understand where you're coming from with the current UWP architecture. Rather a big bummer. Cuz as of now, when dealing with large amount of artboards, moving artboards around can bog down the entire app drastically. I was hoping that using the GPU could allow us to gain some boost in performance, but seems like we're out of luck for now.