krbo

Supporting this! Would be a very useful option.

Bring us checkmarks back! Bring us checkmarks back! Bring us checkmarks back!

in addition: just tried to change square brackets shortcut with something else also using AltGr - nothing, no reaction on AltGr chars as shortcuts but everything is OK during text input, all AltGr chars are recognized in a text tool - []@{}\|€ as this is an input device malfunction I think it requires immediate action and fix, as markingram wrotes in "why msix" post it should be easy to patch whole suite now? tnx for reading!

hi, it's not a question of changing a shortcut, it's a question where they were last 6 years and where they still should be - after that period it's a muscle memory something is wrong with keyboard interpreting tnx for info!

Square brackets are not recognized - it's suite wide bug. Latin2 keyboard (Croatian language) where square brackets are AltGr+F (left) or AltGr+G (right), AltGr where is not marked as such is right ALT key Tested on Photo (paint brush, clone brush) size and Publisher (Pen weight)

just tested samples I have, (don't have the camera) and GH5 are GH5Mk2 RAWs are shown in V2:

Latest Topaz Denoise AI 3.7.0 surelly works on V2 as it works for me, just entered path to long ago installed Denoise, as you can see Sharpen AI and Photo AI also works:

Your Nik Collection path is wrong one - don't link that folder but the acutal one where they are installed, usually in "Program Files":

I will try to answer this. Just extracting will work individualy for each app but we don't know are there any interdependencies between each app and windows (dll registration etc) What is sure is that no other Serif app will be aware of others (as they are just unpacked to a location you randomly choose) so things like "Studio Link" will not work. Some "windows like" updates may not work as apps are not where they should be. It's just a hack to give you more comfortable work with your 3rd party software before system solution is done, if any (I strongly beleive Serif will do something) Biggest problem is that Serif didn't perform wide customer public beta of version 2, all of this problems will be presented to them during that process. There's nothing catastrophic happening, everyone can stil work with v1.

There's a little workaround in installing V2 anyone can try. You'll need a msix file and a free packer/unpacker like 7ZIP Install 7ZIP and download msix anywhere, right clik on it and instruct 7ZIP from a dropped menu to unpack it in a folder (it can be the deafult name as the msix file) After unpacking rename new map as you wish (Photo2) and move it wherever you wont, lets say to a previously prepared "C:\Program Files\Affinity"\ map Open "C:\Program Files\Affinity\Photo2\App" map - there is Photo.exe , start it, register it, make shortcut, connect with your 3rd party app... that's all - it works but can't be sure is everything ok, something missing or not , but it's easy to try and easy to delete

There were lovely check marks in a Layers panel, I can saw from a Moon which layer is active, which not Now they are replaced with awful dark grey and not-so-dark grey dots on which I waste time clicking to detect what is active what not active. (can't give sample right now as Win7 support is dropped off) Horrible UI previously:

I've had today twice small install glitch - update starts and fail during prepare phase (very soon) It was too low free space on my Windows drive - 2Gb were not enough. I would prefer, if you can modify installer, some message with more sense like "not enough space on your target drive" instead of non descriptive "setup failed". thanks!

opened all your samples simultaneously on Win7 x64 (so no OpenCL) played with RAW, developed, played more in photo persona - not a single hickup!

and then if I reopen RAW as a new work it sees haze from the start as there were no other reports of this, let's call it a glitch and forget it for now

Thanks Ron! It was very late so I've tried to find out what happened and went straight to bed Just tested with few other RAWs and yes, it works! Again with original picture I've mentioned and it works!!! But I can still provoke it on afphoto, will try to attach it (300Mb) so switch off all layers except background one and try Dehaze - still doesn't work at me but pixel layer above is OK. maybe you can dig out something (cheap Nvidia 1030 here and latest drivers) 399023403_amci1.afphoto

Just wanted to remove some haze and found filter is completely dead - no slider makes any change no matter Open CL on or off Screenshot illustration with all sliders maxed:

Hi, today I tried to compare some RAW shoots from a new Panasonic Leica DG Vario-Summilux 25-50mm F1.7 ASPH M43 lens and couldn't do it as samples from DPRview article were made with Lumix GH5 Mk2 camera Latest AP Win beta says "file type is not supported" just an info - something for a ToDo list, not critical for me as I'll never have GH5 Mk2

May I suggest you to go back to a previous drivers release? Intel HD 620 drivers download It's a 27.20.100.9168 version - just install it over one you have. I'm suggesting this as I'm using HD 630 and latest drivers (9316) are terrible on Win10 20H2 (19042.867) - constantly after each restart repeats partial install and more importantly crashed Topaz AI plugins (some nasty OpenGL2.0 crash) Reverting helped (I've tested that twice to be sure), maybe will do something for you also

This new "change" passed pretty much under a radar. I've just tested it by adding one lens profile from Adobe product and it worked great - now have two lens correction profiles to choose from. NIce one, liked it a lot!

precisely I will even suggest to concentrate on epub 2.0 leaving version 3 for some future goal as almost all e-readers are 2.0 (millions of Kindle/Kobo devices) Hiring authors of free epub software like Sigil editor or Calibre library/converter/editor will certainly speed up process of exporting HTML/CSS from simple text (epub 2 can't be complicated)

yes! problem solved!

exactly the same behavior as with HD 630

hi, my second PC with old Radeon HD5760 - Win7 780 starts and dissapears after a "loading fonts" on a logo - crash not reported Win event says it's a .Net runtime error: Application: Photo.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Management.ManagementException at System.Management.ManagementException.ThrowWithExtendedInfo(System.Management.ManagementStatus) at System.Management.ManagementObject.Initialize(Boolean) at System.Management.ManagementBaseObject.get_ClassName() at System.Management.ManagementClass.GetInstances(System.Management.EnumerationOptions) at Serif.Affinity.Application.LoadSystemInfoFromWmi() at Serif.Affinity.Application+<>c__DisplayClass64_0.<OnServicesInitialised>b__1() at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart() Dump file included 767 works OK a3c7724f-5215-4c39-ab7a-89da93462f4e.dmp

latest beta 780 latest Intel drivers (27.20.100.8783 few days ago) nothing changed in HD 630 and OpenCL - still hardware deceleration in use

OK, new beta - 1.9.0.767, let's see are there any difference: - still opens RAW slower with OpenCL (4 to 6sec compared to little more then 1sec) and first RAW after beta start opens like without tone curve, then sits for two seconds more and shows correct picture - this does not repeat until AP is closed and reopened - added two screen grabs of flower to show this - fast zooming with mouse wheel is fixed - rendering is faster then witout OpenCL - my test aphoto (3 adjustments and 2 filters) exports to jpg slower then without OpenCL (46sec to 37sec) - tried to make a focus stack (example attached) - horrible, looong loading and "thinking" times during stack phases, crazy color stripe flasher during final render - bottom fifth of a picture missing (that black bar), strange color bleeding (red is non existent in object)