SrPx

Yep, I believe is the stroke preview (that's why the show as list disabled works). I can't remember now, but I don't know if it was in the Windows Events viewer, the actual dump file (with a debugger) or the logs, where it indeed specified the brush preview as a problem (made me think of disabling that, indeed).

Recently another user had this problem. He solved it by using a different scaling. A lot of people think (maybe this is not the situation, but just in case) that you can only set Windows at 125% (yep, needed for a lot of laptops) and 100%. You can use "custom scaling" and set it at 115%, 111, 109, 120, 140 etc (btw, I tested all of these to work). Just, personal advice, don't use 102% or 110% . At those very specific (hopefully it's just those) scaling factors I discovered it crashes when double clicking the foreground/background color sample circles if I set at that DPI (don't know why). The ones (and surely any other number) I listed above work. Another users (actually, I believe 2 users) confirmed to solve the problem with 120%, and 115%, in their case. It's just clicking a blue link ('custom scaling/DPI' or 'advanced scaling', I think) below the place where you set your Windows scaling (in Windows Settings -> System -> Display, scrolling a bit). Screenshot below, sorry for the Spanish, but it is in the same location and items' order. Then you are carried to a new screen, where you type a custom scaling factor. Maybe 115% or 120% will suffice to show the button (and similar situations), but you might need to try several numbers until having one scaling factor that makes you most comfortable. It's often needed a Windows restart (reboot) after setting the scaling, to fully test it, though I have been able to test it without restarting. But to be sure it is taking it, it's best a restart. I'd try first 120 and 115, or anything in between, etc.

It seems it is having issues to load the Wintab driver. Is there a chance that the pen tablet service would be down? (in Windows Services). I would check that the very first. Secondly, if unable to solve anything by that path (specially after restarting Windows) , you would still have the option to use "Windows Ink" (typically in "projection tab", in the Wacom panel, surely similar with other brands) , for that app's profile in the tablet panel. Or in the generic options of the tablet panel, if you don't customize per app. And then, of course setting Windows Ink as input method, in Affinity's preferences/tools. Heck, might even work setting Windows Ink, and then back to "high precision" (what I am using right now, for other reasons, this is my new favorite). As it might "revive" the situation with wintab. But probably won't, if the tablet driver's service is down for some reason. A complete uninstall of the tablet driver, and re-install with a recent driver (for your specific tablet) could be a good way to address the situation. Now, how this could affect "edit in x Affinity app", no idea. Probably it doesn't, it just might be two separate problems (or not). Edit: Indeed, it appears that is not finding the paths... I don't know if this happens if you moved after installed the apps to a different disk/drive. I myself tend to address these issues by fully uninstalling the 3 apps and installing again.

I believe embedding fonts would anyway require the font(/s) license in the target system, specially for the product's commercial usage, but don't quote me on that... I would have to agree that the font embedding is ideal for certain cases. But I have found the situation (many times) where even before sending a first file, the print company would set the requirement of all fonts being converted to curves ("outlines"), despite being a PDF (specially, those print places of the hyper cheap kind). The best workflow for quality is "packaging" the print job (in InDesign, you can do that), where not only the font but other matters will get packed. Outlining the font (converting to curves) can make the text lose a bit of quality (it thickens a bit, kerning might change, etc), and you lose certain features that an actual font provides, even just as a product for display. Anyway, for editing in the target system, it's more usual in the industry to provide an AI or EPS, but because it's Adobe's format with Adobe's tools (fiercely protected walled garden, the file formats being the major guardians). For other companies, those formats are a bit of a nightmare, thus they need often to provide the files as editable PDFs.

I do that with Inkscape - Designer (but several of those features are now in Designer).

Yes, I think those settings are good for the case; I was going to suggest those to be confirmed that are the final ones. 100mp , if I am not mistaken, is about a 11.000 x 9.000 px canvas.Which is something my PC can handle well (in other matters, I don't do photography) but with 32GB RAM (which is the memory you also have, the CPU is quite older, and a laptop version, but hopefully that's not the bottleneck). But painting (what I mostly do) is a relatively low impact operation. I'm sure many filters and photography related operations can put the things to the limit. In the sense that some operations require a ton of processing while others are pretty light. Unless you were doing the exact same operations with same canvas sizes in v1 without lag. Then there'd be a problem. Also, it's a personal theory that I have never been able to confirm, but in other apps setting a too high number of undos, that eats memory (even more, in the past here having the history window open even would introduce slight lag, but that's probably a fixed bug now). Maybe is totally unrelated, but I set it to like 70 as maximum (also as rarely I will need more than even 30, saving different versions is a better workflow for me). Instead of the 1024 undos that come as default. One detail: For me, live filters and other special layers that require heavy processing, or the refining brush, etc, that was typically something that could make the entire app go slow in a large canvas size. When I need speed (ie, for painting), I tend to flatten (rasterize) all what I can and simplify the document.

Are those 5 seconds (seems tight to be able to do it) enough for you to set "hardware acceleration - open cl" as non checked, off, but actually exit normally the app? As a crash avoids saving any preference setting. People are reporting more crashes and issues with Open CL than with memory allocated (but it can be an issue in very low memory (ie, a 4gb RAM laptop) cases or misconfiguration). Also, showing preferences-> Performance, and preferences-> tools screenshots here could be very helpful. Specially as that's a system (unless you left some detail out) with no card, it's using the integrated CPU graphics. Also, how much RAM has got your system (to compare to what's set on preferences, etc). Windows tells you that in Windows Settings-> System-> About (it even tells you how much memory is really allocated and how much is reserved. Usually not a prob with intel). Another setting interesting to check (again, if fast enough to exit normally so that the setting is saved) is to set the renderer as WARP, instead of your integrated graphics. If it stops then crashing, that fact gives valuable info. If it's crashing, it's not saving the preference, so, another way to avoid the Open CL issues is to directly launch Affinity without Open CL, like recommended here:

@Manua Actually, yesterday I myself started to have a minor glitch with Windows Ink. Didn't know it was it, but the glitch was a flashing little square suspiciously similar to certain feedback label that pops when pen & ink features are on. I have that and the service always disabled, as is incredibly annoying while I paint or work on anything graphic (ie, "alt" label appearing on the middle (or the circles appearing everywhere you click, etc) of the screen every time I push alt key. We owe that to our dear MS). So, I suspected that it was triggering those labels for an instant every now and then (I'm constantly picking color while painting). Disabled Windows Ink in both Affinity and Wacom, and instead used "High Precision" in Affinity preferences (as "low" I know produces low quality selections among other things), and then the glitch of the black square disappeared. Turns out it works perfectly with "High Precision", now. In the past, but was several updates ago, I believe I saw an improvement of brush performance switching to Windows Ink, but as there have been several updates since then... And might be just my perception or placebo effect, but did seem to me that High Precision is slightly faster than Windows Ink. Thing is, the 4 things that drastically improved my brush performance, are now reduced to 3 : - Open CL off, the latest software updates to both Affinity 1.x and 2.x apps (they were definitely was slower years ago), and having a 3060 instead of the 1650 graphics card (and 12GB vs 4gb, though maybe that does not affect much) I used before with Affinity. I noticed the difference with each of this, but I assumed Windows Ink was still another positive factor. So, apologies. When you say, 'it makes all super slow' with Open CL off... you are only un-ticking that checkbox, right? You need to leave your Nvidia Quadro P2000 as the renderer, not Warp (but Warp is a good way to eliminate the factor of the graphics card as a problem, to realize if it's other problem. If I understood it well). As it's software rendering only (and really slow). The fact is that not only I did not notice an slow down in my usual stuff to do as a painter, when setting Open CL off, but I even noticed all snappier with it off. When you say, "makes everything super slow", what specifically gets slower ? The brushes, the menus, some filters? Also, for me it is always slow to paint with any live filter on, even if it is applied to another layer. I disable or rasterize those, and paint with very few layers. Still, allows me to paint with four to 10 layers (haven't tested more) in 7000x5000 px canvases (for print and stuff) with Adobe RGB color profile and images in 16bits color mode, brushes of 500 pixels very fluid. All that with Open CL off, very fluid. So, yep, there's some sort of conflict in your system with Affinity (or, some issue in the system itself, that only is detected by Affinity, as it's kindda more picky with a system or driver issue than other apps). I have not tested if I can change the flow with Windows Ink, as I leave the flow fixed value and specific flow response to pressure in all my brushes (indeed, I only change the brush size, and with the Wacom Intuos 4 XL's physical tablet disc/ring, as it's very fast and keeps me in the zone). So, imo just change it to 'High Precision' and sorry for the confusion. They will reach to your case, but it might take a while. But two things: They need to study one case per thread, that's the workflow, so, if you want to have more chances in being seen, I would advice to start a new thread with one small paragraph and your most recent crash report file. The other thing is that they are currently overbooked by fixing bugs and working at full throttle on the Affinity apps (and as you know, small staff, they can only attend stuff as they can humanly can). But yep, imo, make a new thread with the crash report file attached. And sorry about the confusion about Windows Ink, but I was wrong about my own setups, actually, you can and maybe should set up "high precision" instead. Also, sharing your Preferences/Performance, and Preferences/tools , Preference/Interface, Preference/general screenshots could be helpful for them to see if there's sth off or anything.

With PDF/X-4 (in Photo 2.0.3, but I guess is the same in Publisher) it also can't be set RGB, and if left blank exports as CMYK. Yep, at least this one definitely should allow setting RGB color space, and a color profile (ie, Adobe RGB). Amazon -important with the boom of book publishing- requires PDF for the KDP hard cover, but I never was able to find if it needs PDF/X or regular PDFs (for the ebook digital covers I believe it is yet Adobe RGB color profile and TIFF). Still, PDF/X often avoids issues in the printing job. PDF/X-4 using RGB (and letting the RIP deal with it) is even a requirement for a good number of places now, for whatever. I myself got used through so many years to just have to export PDF/X-1a (which since always meant a CMYK file or spot colors), but I started to be surprised years ago when certain print companies, even "big" ones, started requiring PDF/X-4 and in RGB, Adobe RGB profile.

Which settings do you have in Preferences/performance and preferences/tools, @Manua ? I had some app lag, and some serious issues with brush lag until I disabled Open CL, (but left my nvidia card, not warp) but also set Windows INK in input method in preferences/tools but as well at my Wacom's panel (through windows control panel), in the app's profile for Photo (or etc), -btw, how to do that, here - in the "projection" tab. Also, I had issues with .net (repaired), SFC and DISM found some corrupted system files (fixed by them), and did not get totally smooth brush work until used a tool to uninstall my nvidia drivers, and installed the most recent Studio ones. Left GeForce Experience to auto update the drivers, but being nvidia Studio drivers, that is not frequent, thankfully. Currently my brushes go as fast as in clip studio. Some eventual freeze (but it recovers after some seconds, no app swap needed) occur when I am editing the brushes settings, specifically in the brush's pressure curve setting, while handling those nodes, usually when I "fail", and click outside the actual node, in the dynamics tab of the brush configuration (that window which you get when double clicking on any brush on the list; the changes there get saved for ever in the brush, unlike when you change them in the toolbar) . But knowing that, I change the pressure curves with my mouse. It does not happen anywhere else in any affinity app any more. So, kind of all what I applied (above) works outstandingly for painting fluidly. I've told these settings and actions to some other people with brush/app lag and it has solved it. But who knows. Edit: Besides the needed (for fluid painting) open cl off and activating both windows ink in wacom panel and affinity, I'd really use certain tool to fully uninstall your nvidia drivers, and be sure to download the latest graphic driver for your specific Quadro graphic card. I'd restart the system before installing the new drivers. Nvidia drivers full uninstall tool : https://www.guru3d.com/files-details/display-driver-uninstaller-download.html Edit: Important, @Manua If my memory does not fail me, you do need to choose Studio drivers (also, supposedly more stable) with a quadro card, now that you are going to download them. The laptop vendor might have installed the game ready ones. I use the studio drivers with a 3060, both in a laptop and a desktop, it all goes pretty well for painting. The brushes surely won't go fully fluid until the open cl is off and the windows ink is set in wacom panel and affinity prefs, but I've seen the dump, and strongly suspect the driver (uninstalling with that tool) re-install is needed.

If it crashes in seconds and have never been able to exit normally, then the no-open cl setting is not saved; preferences seem to need a successful exit to be saved. There is a way to launch Affinity apps without open cl, for these cases (among others) :

Ouch... SORRY. I really need to sleep more. I have just realized I understood badly the issue, since the beginning.. It'd be bad to delete all my posts now, for the thread's coherence. You mentioned "pixelated", and not smooth enough, while for some strange process in my brain (prolly too fast reading and being sleep deprived) I was thinking of blurriness, the opposite. If things get too pixelated, my general rule is to export at very large pixel size from the vector app, and then resize on the raster app I think provides me with best pixel output. This typically provides me with best line and font quality for a client sample (the rare cases when I don't just use PDFs for that) That is, I often leave this to batch processing (often with lanczos) in irfanview, XnView, or even just Photo, as from a big image and treating it with raster filters, you have lot of control. But yep, apologies as I had not understood well the matter, thinking of "poor quality" as blurriness. I mean, I initially read pixelated and that, but seems my brain went to other posts that previously appeared here. Some of what I say (as tricks, never solutions) still applies, but using other filter, not unsharp mask.

Yep, while Windows Paint surely is showing a PNG (of course, never a JPG to evaluate sharpness, due to the compression. But I guess that's implied) without many tricks -and yet I'd only trust a view in 100% zoom, in any viewer... and even so, who knows, after all I have been able to realize in many apps, including Adobe's- I would warn people about browsers, though. In some cases they do "smart scaling", ie, whenever not showing an image 1:1 (100% zoom) because the web code is making it to show smaller or bigger. I tested back in the day (maybe browsers have improved now, but anything happening in real time tends to be lower quality, by nature) that those resamples are in lower quality than even bicubic and certainly lanczos 3 resample (and of course, that many browsers don't have color management, or not "ON" by default, but that's another issue, tho can affect contrast perception, and so, sharpness perception, which can be happening also here with different conversions in different apps from CMYK to the PNG's "forced" RGB). And I would not be surprised if in some browsers (there are many: Safari, Opera, Chrome, Firefox, Edge, etc) there's some resampling by default even if the web page code isn't telling it to show at a different size. Responsive design anyway (which is everything, today), is re-scaling everything constantly, and the browser, to my knowledge, never gets lanczos 3 resample quality. Anyway, I would go to the process I mentioned/listed earlier, as I myself believed what was being said here by two or three people in the forums (which could be true for some use cases if not knowing the following) about the image exports from Affinity (all apps, as the export engine I believe it to be the same), and proved (to me) the final situation not to be true (IF knowing what to do), when just setting Lanczos 3 "non-separated" -which in Affinity includes strong sharpen in the process- the export was super sharp... indeed, a bit too much. So I realized the best is Lanczos 3 "Separated". As while it outputs things a bit too smooth, it has enough detail and information to gain sharpness without losing info: While the smoothing happens later, I tested that if you add an unsharp mask filter previous to export (or live filter over everything, affecting all layers), the result is pretty good. btw, I am a professional graphic designer (decades, sigh), 3D artist and illustrator (many years, had to switch fields often). Well, I am also a hobbyist, too . I only say it so that the solution is taken in consideration, as going that path should end up with good exports. If one is trying to export a PNG direct from vector content... for this trick (and if willing to get a super sharp sample) it's needed to flatten/rasterize all first (and undo later, not saving the source file flat, obviously) , something I used to do in Adobe's apps, anyway. From Designer, best is to click "Edit in Photo" in File menu, apply in Photo an 'unsharp mask' filter, then export as PNG. Edit : But if for some reason (I wouldn't understand that in a professional environment) you did not get the 3 apps, so, can't click "Edit in Photo" for the Unsharp Mask (and other sharpening filters), only have Designer, then you might want to go with lanczos 3 non-separated, if really want a lot of crispness. PD: Might be my 50 years old eyes, but, exporting direct from Designer 2.0.3, a design with text exported as PNG Bilinear (even bicubic) seems as good as lanczos 3 non-separated. And in any case -as another professional- I am not seeing anything bad in any of the exports (but I am trying to). Definitely even the most strict client would not complain. Besides most of the times the clients know little about technical matters, deeper matters in composition, color, the concept itself would be more of my priority.

Hello! It appears to me that you can change the keys to any other keys in all of those tools (just checked myself). So, in Preferences-> Shortcuts, leaving the 1st deploying menu as "Photo", the below one set it to Brush tool, Clone tool, Eraser tool... set on each them two keys you would want for increase size/decrase brush/clone/etc size. Can use the same pair for all the tools. Always that don't interfere with shortcuts of other tools that you use heavily. I indeed have two other keys as the Wacom Panel does not love the brackets, either... And years ago I'd just any other pair of keys that were comfortable for me. Currently (since years, and in all the apps I use) I assigned those two keys to my Wacom tablet's Disc/ring, adjusting to lower speed the ring sensitivity, and I have my left hand there on the disc/ring (close to the keyboard, too). One of the best life-quality improvements changes in my painting activity.

I would have some questions (mostly curiosity) - Which algorithm for resampling are you using in the PNG export properties, in Designer? I mean once clicking on the "More" button. Bilineal, Bicubic, Lanczos 3 (and if so, separated or non separated). Spoiler alert, I love Lanczos 3. (apparently there's already Lanczos 8, but in my several brands of 2D and 3D apps I seem yet to only find Lanczos 3. Is thought by many (I do so) to be superior not just to bilinear, also to bicubic). - Where are you viewing the results, to compare them? In a specific image viewer ? Which is it? Or are you seeing the PNgs in their respective viewports (in Corel Draw's and Affinity's viewport). As that could be viewport-specific, often not true to the actual quality saved in the file, and shown in browsers, etc (also, some browsers apply smart scaling and other stuff, so, a bit of extra variants and factors there...), and very different in one app vs the other. - Myclay might be onto something: barely lighter blacks do produce a less sharp perception, specially in smaller fonts. When coming from a CMYK image, where the black should be formed (to print well and sharp, but this is for the actual printing machine, not display) only by black tint (100% "K" while c,my,y at zero). This produces a "light black", not perceived as full black. Now, the conversion of the CMYK profile towards RGB (PNG is always rgb, it does not support CMYK) could be happening towards a richer black (a rich black is a black formed by the mix of several colors, obtaining a deeper black than a pure cmyk black of only k at 100% and other "inks" at zero) in one app (ie, Corel) than the other. Resulting in a quite lighter "black" in one. Where it happens so, the font is no doubt going to look less sharp, as has less range for everything, and way less contrast to play with. So, I would try to make sure that I am using -as a result- the same level of black exactly, once converted to PNG, as yep it can affect our perception of sharpness. - Affinity apps do a sort of viewport optimization for performance (Photoshop used to do this for zoom factors other than round numbers, today I dunno) , so, if you are evaluating the exported png sharpness in Affinity viewport, you might be seeing less sharpness than the png will show in image viewers, other graphic apps, or even a web browser. - I made a recent test (related to other matters) with PNG and PSD exports, and concluded that the export when using Lanczos 3, and "separated" or "non separated" (can't remember which now) produced a sharper export, but then I realized that when myself applying (to the less sharp one) an unsharp mask with good values (that are typically always the same for low res graphics), the export would look as sharp as the export of any other "standard" 2D application. As if in Affinity, it could be leaving the unsharp mask pass to your criteria. I would give a chance to play with unsharp mask (Photo's live filter and normal filter, but I believe Designer's Pixel Persona has it too) and then compare the best output you can get of that to the 8pt font export from Corel, and see then what is the conclusion. If the unsharp mask is the solution, as it was in my case, I'd just add it as a live filter to my projects, almost by default, when I'd want very clear and sharp edges. I am not stating anything. This is just what I would do if I'd find such a problem myself.

I'm curious to see if after running those utilities and everything, you don't ever see Affinity crashing with those files ever again. If you have some version of that file (better if emptied of all specific content) that can be shared, I would like to test if it crashes my systems, and report it so here... even if now it does not crash your PCs anymore. Edit: If it's not crashing anymore, could be the open cl being off, now....

It was actually a good idea, BlueLiner. If it had worked , we'd have now 3 ways, not just two, and the more, the merrier, as projects can be very different and there's never enough workarounds. Also, it somehow works (well, for some cases, from what I am seeing) despite the fact that smooth curves, well, "smoothes" the lines, and so this detail can give another clue to the developers. 😎 Nothing to regret, at all!

But when you smooth the curves, you are only do one vertex/node . When converting to curves, you enter in nodes mode, but only one node will be selected), you had only one selected. If you get all nodes selected, it modifies the shape (makes all corners round, probably also make several straight line curves), which is not desirable. Edit: Apparently in some situations it smooths (deforms) the entire shape even if one vertex is only selected... not good, tho. Edit: Sorry, nothing of the above makes sense (again, slept too little last night...). However, is not working here... (besides smooth deforms the shapes..) Anyway, tested (with subtract) with several letters (a word. But also tried with one single letter...) and then the boolean/compound (and I guess neither knife and shapebuilder) does not work here... Does not work smoothing only one vertex, neither if smoothing all vertices, neither if not selecting anything, just hitting the smooth curve button like you did (I'd love to have a 3rd workaround, tho). Are you using 2.0 or 2.0.3 ? Edit: tested that it works on single letter, but it deforms and rounds all curves. But the subtract then work in that particular letter (an W). testing with Arial, and seems that letters with very straight lines are the most deformed (like Arial's capital W). Those with some curves, also get their vertices displaced and curves modified, but in some cases is less perceivable. It works also with several letters, convert to curves, then Geometry/Melt Curves, then smooth curve, then subtract. But it's also all deformed/rounded...I don't understand why it did not do it to your letter....

Yep, there are several threads about the matter. I believe it is a same issue. So, "One ring to bring them all..." ( -- Gandalf (c) ). I mean, perhaps one single fix will solve many problems (probably). And yes it happens when text is converted to curves, whether is such operation by itself what changed (only with text: with shapes works great), or some characteristic of text elements in v2 that has changed from v1. The tools not working well due to this, appear to be (till further notice about more tools affected) : Knife, Booleans (add, subtract, etc), and ShapeBuilder. We (forum people) have found two methods that seem to make possible to work with all these tools without problems (the simple, easy and elegant one is from @,,, , the one about changing document's width to 1px). In case you are curious or need a workaround to continue working on your project(/s) until they fix this (linked below a post with a summary of both methods. You can skip to "method 1, method 2 paragraph. The previous text is only about that case's specifics): https://forum.affinity.serif.com/index.php?/topic/178299-affinity-designer-crashes-after-using-shape-tool/&do=findComment&comment=1027498

It's unclear to me if with Open CL off you are still having the problem, or that you want to have it on, and then if so, it keeps crashing. The advice was not to set it off and then back on. I would still leave it unchecked (open CL), it has been reported multiple problems with it (at least till a future release). Also, if you are using one graphic app at a given time (imo best use with 16gb, different case with 32 or 64), I would increase the RAM setting there in preferences like to 10 or 12. Undos, I know by default is 1024, but I suspect that eats memory, too. I usually set it at 30 or 70 as much. That scene has many nodes, and the boolean operations might be very intensive. So, imo both doing the above (for memory) and maybe simplifying not with shape builder or booleans, but "old style", manually, the scene, and by all means -as also wouldn't be proper for a logo- discard any raster layer effect, live filter, live anything, etc. Flatten all as much as you can. Maybe once it is a lighter scene, shape builder can help better. Also, it might be related to certain bug... we've been having a problem (actually several problems, but I think all come from a same root) with text converted to curves lately. Generating problems with knife, booleans and shapebuilder. There's some sort of bug. We've found two "dirty" tricks that allow to work in all those situations meanwhile that gets fixed : Method 1) - (credit for this one goes to @,,, ) In document properties (document setup in File menu) set the width of the document to 1 pixel. Then do all your booleans (add, subtract, etc), knife or shapebuilder tool operations then, and once you are finished with all those operations (logo simplified, etc), then you can set in document properties the correct dimensions you want it to have (in mm, inches, points or whatever). Method 2) - Wouldn't recommend this one (I discovered it, btw) for a complex project like this, it'd be tedious (or maybe not, if you can just melt all). But in case the above doesn't work in this scene. My trick is to set in preferences-> general-> "clipboard to copy as SVG" (no need to restart). Then, select all and do right click, 'geometry', melt curves (unless you already did so, it'd be fine) so it's combined to one thing (not group), then with it selected, copy (ctrl + c or right click "copy"). Now in top menu Edit, click on "Special Paste" (you can set a shortcut key for this) and in the tiny window that shows up, click on "Scalable Vector Graphics". It creates a "cured" curves element, but with like a parent layer or group, just grab the generated curves layer out of that layer, and then delete then the empty layer. This new pasted curve object can receive all knife, booleans, and shapebuilder operations without certain bugs. But I don't know if this is would avoid your crash (it might). If the pasted object does not get placed in the exact position of the original, with snapping activated (and the right settings in snapping) you can place it (it will snap to the old) matching with the old melted curves object's position.

Hardware acceleration-Open CL is off, unchecked, in preferences-> performance ? (if not, I'd try to set that off, first thing). (maybe also would help a screenshot of your preferences->performance screen) Edit: Also, be sure you have installed a recent version of your graphic card's driver (if not, uninstall it, install the newest one) And something very required here, to have all the latest windows updates.

One question... When you right click on an Affinity Photo file, *.afphoto, and in the floating menu that appears, you click on "Open With", what does it show, then? A list in what appears all the v1 and v2 apps that you have purchased? Or only V1 ones ? In my case it lists all 6, v1 and v2 apps. I can't test anything as I am in my Win 10 right now, and this one does not have the problem. I can think of 4 things to do (not to do all 4, but the first that works, you stop there, of course). But I'd try them in the listed order. One idea that comes is to check in Windows Settings-> Apps -> Default apps -> Set defaults by app. And check if Affinity Photo v2 settings are correct. Or if the app is actually listed there (it should). Other could be to fiddle in Windows folder settings in one particular folder. Set the view as 'details' or 'list' (to ensure it really takes it I do it setting "for all folders", clicking that button in folder options, but that would change settings for other folders, too), restart Windows, set again that folder as full thumbnails, restart . Thumbnail problems have gone away for me sometimes doing that, with other applications/issues (I haven't got them yet with Affinity). If it is solved by this, then in folder options you can click the button "set all folders like this folder", but only if you know what you're doing, as maybe you prefer other folders to display as details, etc (anyway, you can later on manually displays those specific folders as list, etc). I use the button a lot, as mostly I want all my graphic folders to display thumbnails. Other problems have gone (again, with other apps) by setting on Windows Settings-> About -> clicking on the "Advanced system settings" link at the very right of that screen -> then you get a tiny window, and just in the 'Advanced' tab you appear on, on the "performance" area, click on the "Settings" button. -> You will be now in a new window, in "visual effects" tab. Now uncheck the box "Show thumbnails instead of icons". Restart Windows. No folder should show thumbnails now, all just bare icons. Go back to the setting I just explained, and set as checked "Show thumbnails instead of icons" back, as you want it on, this just helps to fix thumbnails issues in some cases. Restart Windows and see if it solves it. Also , there was a way to "flush" the Windows thumbnails cache, but was complicated and I don't remember the procedure right now... All the things above, I'd try before this. But if nothing above works (all are fast, slower to explain than to do), I'd try to fully uninstall all Affinity V2 apps, and install them again. As I say, as a last resource.

Fantastic! I'm very glad it ended so

If you can re-import them or download them from your Serif account... I mean, you have the sources to install them... Maybe try to reset the Affinity apps where it's failing, by double clicking on the V2 app (ie, Photo 2) but whilst having ctrl key pressed, as this triggers a dialog where you can delete all defaults and presets, if I'm not wrong. Restart later the app and then try to import your brushes again. Until someone gives a better advice

It's been a while for me... But ctrl + shift + z used to be redo, in Photoshop (edit: seems still it is). It became second nature to me at the job. And I guess to a lot of people. Many more Photoshop users than of any other graphic application, in the planet... One could say it's an industry standard now, the ctrl + shift +z. Many apps use ctrl + y, too. So, I guess both are (but PS and Illustrator have no competition in terms of user base size, to be honest). I recon tho that only since recently (embarrassingly enough) is that I barely have to look that much to the keyboard for whatever.. never went to those typing classes/courses... I should have. Yeah, I don't know, ctrl + y is used quite for preview in outlines-only, not only in Illustrator, but also other vector apps (Figma (With and Adobe XD, Sketch, InVision, it's one of the main tools for web/mobile/apps UI prototyping) and other vector apps (some don't even exist anymore, though)). It'd be a problem to use redo with a shortcut when working with one app of the suite, then use another in other app. As then is not a period of adaptation and that's it.. it'd then be constantly a total change of habit even every half hour. Or that's my take. Ctrl Y -> outlines is second nature for many (in vectors the world and industry is ruled by Illustrator) while working with vectors, and ctrl + shift + z as redo is second nature as well for even more people (Photoshop). Tough decision. I use a tad of different 2D/3D apps per week, ones have ctrl + y, others ctrl shift z, and worse, others none of these, and can't get it configured in preferences. Thankfully, in Affinity you can (but I'm leaving ctrl shift z). Ctrl + y (or whatever keys you set for that command) is super useful in Designer. It lets you see in outlines mode, but indeed, in the last mode you used. For some people, the most useful one is not the new current default one for outlines, but the "pure" old outlines one. If you are working in one mode, ctrl + y will get you that one, even if you restart. Super good feature (I know, this is praise for a feature, not the keyboard shortcut) . When in complex projects, I don't know what I'd do without an outline mode (that's OT, sorry). If I remember well, in Photoshop ctrl + y is for getting into proof mode for whatever the color profile assigned (I mention it as a curiosity, only). Somehow a view mode as well.