Claudio60

Both the same 2 translation bugs Uwe367 reported, are also affecting the italian language.

Hi Mirjam, you can take a look at the little program firstdefence suggested and maybe this could be the easiest solution for you (I never tried the program); anyway my instructions are very simple (2 minutes' time) , I post some screenshots so you can check the procedure step by step.

Interesting, tks :)

To solve this problem you have to do this: go to regedit, then go to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > SideBySide, right click on SideBySide and select NEW > DWORD (32 bit) Value giving it the name PreferExternalManifest then Enter; double click on PreferExternalManifest and change the value from 0 to 1 and click OK, then exit the Registry editor. Now you have to create a text file with this content: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3"> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*"> </assemblyIdentity> </dependentAssembly> </dependency> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.VC90.CRT" version="9.0.21022.8" processorArchitecture="amd64" publicKeyToken="1fc8b3b9a1e18e3b"> </assemblyIdentity> </dependentAssembly> </dependency> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedPrivileges> <requestedExecutionLevel level="asInvoker" uiAccess="false"/> </requestedPrivileges> </security> </trustInfo> <asmv3:application> <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings"> <ms_windowsSettings:dpiAware xmlns:ms_windowsSettings="http://schemas.microsoft.com/SMI/2005/WindowsSettings">false</ms_windowsSettings:dpiAware> </asmv3:windowsSettings> </asmv3:application> </assembly> Now save the text file with this name/extention: Photo.exe.manifest (without .txt extention) and put it in the same Affinity photo.exe folder (C:\Program Files\Affinity\Affinity Photo) and you're done. Now Nik collection's ui is scaling properly as a plugin on high dpi monitors, hope it helps

Grazie mille Paolo e buon anno!!

I'm feeling so stupid… Thank you Gabe

I'm not sure if I'm doing something wrong or this could be a bug but I noticed this: - If I open an image and select b for brush tool, the brush size preview (the circle) is working correctly with the right colour using both the pen and the mouse (program ui is working fine); - if I create a new document file/new/b for brush tool (important: using the pen to give these commands) the brush tool preview (the circle) is visible both with the pen and the mouse but has no colour until I make the first stroke/draw with the pen or with the mouse (after that the colour appears inside the preview circle); program ui is freezed if I want to use the mouse to give a command (for example saving the file, close the program etc.) and is working only using the pen, the pointer of the mouse is moving but it's impossible to give commands (menu options not greyout but not active); but if I make something with the pen (browsing the menu is enough) the mouse starts working again and interact with the program. - if I create a new document file/new/b for brush tool (important: using the mouse to give these commands) the pen has only a pointer instead of the circle until I begin to draw with the pen or if the mouse pointer remains inside the image area (the preview circle is transparent), program ui is working both with the pen and the mouse; PS: I use my Surface Pro 4 with its signature type cover and when I talk about using the mouse I mean I'm using the trackpad ; "show brush size preview" and "enable pointer support" are both enabled under "preferences"; Affinity Photo is version 1.6.5.123 Any suggestion would be appreciated and sorry for my english.

I'd rather not uninstall and reinstall the pen's drivers because there is no updated .zip file to let me do this; the latest drivers/firmwares are present only in .msi file (both drivers and firmwares are installed) for win ver 1803 (I have 1809) and I think that if I try to install them (overwrite), my Surface will be messed up. I uninstalled all the entries related to surface pen in device manager but the problem persisted after the reboot; in the meantime I discovered a strange behaviour using the brush tool but I think it's better I'll describe it in the correct section inside the forum. Anyway I really appreciate your help!

Tks, I will surely look at all these informations, in the meantime I'm doing some procedures/experiments.

Hi, Tks for your answer but I don't use Wacom hardware but only the Surface pen together with My Surface Pro 4 and I don't have any drivers to update. Any other suggestions?

Same problem here with stable version 1.6.5.123 on a Surface Pro 4; using the Surface pen with the brush tool I have only a pointer visible on screen and if I want to see the brush size (the circle) I have to move the mouse on the active area first, after doing so the pointer turns into a circle and I can use the pen, as Omprakash Selvaraj described. PS: "show brush preview" enabled or disabled doesn't change anything.

Tks Dan, your fix has solved the issue, have a nice day!

It's not a Windows bug as if I associate the .aphoto file with Xnview MP the "open" contextual menu is in italian: "apri".

Hi Dan, I mean the right click in Windows Explorer, you can see it in my screenshot.