SpacemanJupiter

I'm new to Affinity Designer and was trying to find a way to crop canvas. I applied the artboard as a method and totally freaked out because I couldn't undo it, and it had shifted things around. It wasn't much work to simply shut down without saving and recreate a few steps of work but I'm really glad this is being worked on.

I've actually done that several times over the past week. I'll go into Nvidia control panel and change it, and also change it in the performance options of Designer. It still happens, but I couldn't get it to happen when I completely uninstalled Intel graphics drivers and just let windows use the windows basic driver. This is one HUGE gripe that I have about the MSP. The two graphics drivers seem to somehow be dependent on each other which is really odd, or at least, the Nvidia drivers are hardware is somehow dependent on the Intel being enabled. When I disable the intel chip, it also disables the Nvidia control panel and I just get the msg that 'there is no nvidia chip on this system' when I try to open the control panel. This is after complete format and reinstalls of windows, not just resets. Beyond frustrating. I'm just wondering now if this hardware was just horribly designed.

My whole screen is going black for a split second. It is most easily reproducible if I'm dragging around an imported jpg or image file. It can be random as to how often, but sometimes it happens every few seconds and even twice within 1 second. The whole screen is basically blinking off and on. MobileStudio Pro 16, 16gb ram, Nvidia M1000M Quadro, Intel iris 550, Win10. The suspect is Intel drivers. I've tried various versions of the drivers but the only time I cannot reproduce this blinking problem is by completely uninstalling Intel graphics drivers. I can't leave them uninstalled though because this tablet won't simply change over to the Quadro for the desktop acceleration. It also makes my pen unusable. But, who is at fault here? I am not sure whether to come here or go to Intel. Affinity Designer is the only program where this problem surfaces. I can't reproduce it in Adobe stuff or 3D animation programs, or anything else. What seems clear is that the program and pretty much any intel drivers for the integrated chip are not playing nicely with each other. I'm just hoping someone else also has a MSP and has found an oddball version of Intel drivers that works with this software.