Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

SrPx

Members
  • Posts

    2,796
  • Joined

Everything posted by SrPx

  1. Very nice illustrations. And a lot of work! Edit: Also, I have visited your link, and while these shown here remind me a lot the Bosch's detailed art pieces... the internal pages (hey, you show all the book there! Isn't that a bit risky? or maybe I am too cautious in those cases) are absolutely gorgeous, I like them even more. Edit: ...Or maybe it's not all the book (I believe there are no 96 pages loading there) , but a really generous preview, nonetheless! Edit : Also, I have never written a book (only short comics) but I have made (illustration and design) book covers for authors that published on Amazon, and "Amazon KDP" help pages are OK-ish in detailing how you need to prepare the cover for them, in what is all the specs. They could have gone in more detail, and some choices in such specs are a bit strange (for printing) but quite fine, though. No idea about what site has more traffic or sells potential, if Amazon or Ingram Spark. In writers' forums I've often read that it is Amazon (due to its massive traffic in general), but I don't know if that is really so. That's the one aspect I'd like to know more about.
  2. I believe it is enough to have done it with one Affinity app and show it here. I mean, it's not a requirement to do further...
  3. I have made now a test setting the two windows (chrome web browser and Affinity Designer) in mosaic mode, side to side, with a text frame with a bunch of text. Even losing the focus by clicking on the browser, no blur happens on the Affinity Designer's text. Indeed, it works great also with Retina rendering: Auto. I have tested that the other two modes work as well without producing text blur. Still, in your case I'd do the test setting "high quality", just in case. I am using 2.0.3 yet, haven't done the update to 2.0.4. But for this matter it's surely the same. Also, I don't notice any slowing down/lag in typing in a text frame in Designer, even with a bunch of text in it (and I have gazillions of fonts in my system). My guess/bet would be the card's graphic driver. You are using a 1060... This is very old.. Are you forced to use a very old driver version for some other stuff to work well ? An old driver could be the culprit... (again, even if everything else on the planet works well in your machine; Affinity is kindda picky...But this aspect made me discover some stuff that wasn't as correct as I thought, in my system. So, there's that, too).
  4. Some people having graphic glitches have solved the problems by fully uninstalling the nvidia drivers using a free tool (the link is in some forum post here) as in some cases the simple uninstall is not clean, and the installing the newest drivers (I use the nVidia "Studio" version), as sometimes is an issue with the graphic driver.
  5. I have a laptop with those specs (the one in my signature), and Affinity seems to work very fast in it. In the matter of disk, any SSD will be fast in a DTP app (Indeed, I work fast saving in HDDs yet, no problems). Yep, I never thought your case would be due to hardware (a 5950X (the most efficient (frame per watt, not render speed) PC CPU for rendering, including the new 7000s) with 128GB RAM should find barriers in nothing), there's a lot of people around working (with Affinity) with even laptops with APUs and iGPUs, no discrete cards, 16GB RAM, even being low consume "U" CPUs, yet they don't have the typing issue. There's something going on there, but it's surely software/config or the like. That yep, it happens more with Affinity than other apps. I don't have any issues now, but I have needed to heavily cure (not meaning that I should have...) my system to reach this point. I know some fonts give problems (did happen to other ppl too, in the forum and they also solved it so), not necessarily being a complex/fancy font. But it can also be issues with the .NET libraries (.NET version installed on the system), or some other system files, etc. That is only a part of the reasons why I recommended trying it on another system, be it a laptop or a more vanilla PC. As it is a way to determine that there's something in that system that is not playing well with Affinity (even if every other app on earth gives no problems at all).
  6. This is a different problem (different cause, I suppose, too). Super random idea, but have you tried setting "retina rendering" as "High Quality", instead of "Auto" (auto is default, if I am not wrong). The auto thing might be doing its optimization. I mean, in Affinity's Preferences -> Performance. And of course, having in View Quality, "Bilinear (Best quality)", and in "Display", your graphic card (nVidia 1060). (and, yep, I disable Open CL, as it works best for me) .
  7. In the past, I had issues with type/text lagging (in 1.x, surely would have them in v2 with that font) which I solved by discovering a particular very heavy font (sometimes it's some other odd factor of that font) which had issues with Affinity (just one font). I didn't really used it, so I eliminated that one from Windows/fonts (I also set Windows/fonts on a SSD, as in my HDD would make things go slower in Affinity (I believe even the app start became faster); I still use HDDs for work files and caching ...), and it started to work well and snappy. One thing I'd try is to install v2.0.4 in a laptop or other computer, which would have only basic system fonts, see if then the type tool lags there or if it doesn't.
  8. Have you tried disabling it? My performance issues (brush lag) went away for ever by disabling it. I can paint in Photo and Designer's Pixel Persona as fast as in any non Affinity app. Indeed, this is so for both 1.x and 2.x (I have both suites installed). The other thing that was giving me problems (while I had been recommending it before, as it did seem to work smoothly at first) was setting "Windows Ink" both in the Wacom panel and Affinity preferences (tools/input method). Setting High Precision, instead, (I advice not to set Low Precision) works best for me in terms of lag and avoiding other issues. Also, yes that card (1060) is now highly unbalanced in features and capability with your great system: it is perhaps being a bottleneck. My 3060 works very fast with the 3900X in Affinity apps -can't complain, certainly- , with very large canvases and huge brushes (probably the GPU does little there, though, but it was definitely slower with my 1650. But because my card upgrade has been almost at the same time than me getting back to using more Affinity, during the time when v1 updated to 1.10.6, and v2 was released, not sure about how much of it can be attributed to a newer card. But even with the 3060, it was lagging before disabling Open CL). It is surely the problems that Open CL causes in some systems. I have not noticed anything slowing down in any of the 6 Affinity apps after disabling Open CL. But maybe it is that I don't use very heavy filters, content-aware tools or etc. I just paint and edit images (but huge ones, for print). I still notice slowing down/lag if I work with live layers while I paint. I tend to rasterize them for that (I work mainly in Photo, also Designer for vectors, but surely the core issues are common).
  9. Does this mean that "copy as SVG" preference and "paste special- as SVG" produces inaccurate geometry? I'd be worried for other workflows, not just this... I mean, supposedly, nothing should ruin the geometry, inside the software...
  10. Also, if I remember well and it'd have not changed in years, VMs don't get direct hardware access to the GPU (there's a method for doing so, though, surely not practical in this multiple installations case). So, while I would test first disabling the Open CL-hardware acceleration (by launching the apps (just once needed, the first time) as I just posted, or in preferences/performance in any Affinity app), if this does not solve it, you might then set it in software mode, setting in preferences->performance "Display" to be "Warp". This should as well discard any issues being caused by the GPU or iGPU/APU or stuff related to it. In regular desktop PCs setting it so makes some things go slower, but it depends on use cases, etc. In worst case scenario, serves to rule things out.
  11. If it only lets you 2 seconds, you will have not been able to disable Open CL in preferences in any of your VMs. Please, try running it with the following parameter, it disables Open CL on launch :
  12. I notice lag in painting (I use very large canvases and large brushes) if I have set several "live" filters/fx etc layers. With just simple pixel layers (even using many) and nothing live (I don't need it for painting, or I do whatever and then rasterize) I don't have lag. I have this paranoid obsession with the default number of undos (in preferences/performance) being excessive, 1024, as that did cause performance issues in very old versions of Photoshop (I set it in Affinity apps always to 30 - 70). Also, most problems I had of it not being snappy did vanish by setting Open Cl/hardware acceleration off (but setting there my nvidia card, not Warp). Some other slighter issues have gone away by not using anymore Windows INK in both the Wacom panel and the Affinity preferences/input method. Setting there "High precision", instead. Surely has helped curing all the graphic driver/.NET/win updates/sfc & dism cleanup. But for sure I know that if I set Open CL on, I get lag. So, it's off, in all the Affinity 2.0.3 apps, and goes fluid (at least here) with very large canvases and large brushes, after doing those things, specially OCL stuff. Also, I have 32GB RAM. Not sure if there's also a problem with people with 16gb or less.
  13. @darkcrowgraphics as I just wrote in other thread (and some others, longer ago) it's a bug with text converted to curves, and it causes problems to booleans (add, subtract, divide...), shapebuilder and knife. There are two workarounds. 1) One is setting all document (in document properties) width to 1px, doing all operations with booelans, shapebuilder or knife, then set in document properties the width to what it was. or 2) And the one I found out (also for booleans, shapebuilder and knife), set 'copy as svg' in preferences->general. Leave it permanent or not, as you prefer. Do a copy of your curves (converted from text) with ctrl+c or right click, 'copy', then, top menu Edit/Paste Special, then "paste as Scalable vector Graphics (svg)" (advice: make a preference shortcut for it). Get rid of a layer or group that it generates, and place with snapping the new curves object to snap to the old one, to get it in same position (no needed if it pasted in-place). Get rid of the old one. I just detailed it better here. It's very fast to do. I have not tested much the first one, but yep a pair of times, and it worked. I suppose each is better for different cases (ie, not willing to use the copy as svg preference or not willing to change temporarily the document dimensions, but I don't see much issue with any of the two). Edit: When using several letters, I would recommend using right click-> Geometry-> melt, as it combines all curves into one single object/layer.
  14. If you set in preferences/general to allow to "copy as svg". After that, all you need to do is first convert to curves (as usual) your text , letter, glyph or etc, then you can do a geometry/melt -if needed- , copy the curves with ctrl + c or right click->copy, (but the actual curves not a "group"), then menu Edit/Special Paste, and choose Paste as Scalable Vector Graphics (SVG) (it generates a group, get rid of it (ctrl+shift+g or right click->ungroup) or pull the curves out of it). I have set in preferences/shortcuts a key shortcut to use it instead of regular ctrl+v (only when needing to "curate" a curves object), for the sake of speed. Which is the only real difference to a normal workflow. You can leave the "copy as SVG" preference permanent, some people do it as they are frequently fast copy & pasting among apps like Inkscape and Designer). So, the difference with a normal workflow is that you are making a copy of your converted-to-curves text, place it over the old one (using snapping on as it places it exactly in place, then get rid of the old, of course). It's all done in 5 seconds. From then on, no need to make it to the object anymore, can do then any boolean, knife or shapebuilder operation to it. The object is permanently "curated". It's a workaround I found till they fix it. But it works for now with this issue, workaround that works to be able to use without this and other issues : booleans, shapebuilder and knife. But in other threads I can see that a few people don't realize yet that it is related to the same bug. Note that setting in preferences ' copy as svg', it takes it on or off without needing to restart the app. You can change it on and off as you wish during your process.
  15. Yep, I think so, too. You select a new brush and then you will be using that one. But there might be a small bug. [ Off topic: You can (double click on any brush on the list, to permanently set its properties and behavior) link a tool in such settings dialog/window. In the "general" tab, last drop-down item. If you click to deploy that, you can set what tool gets triggered just when clicking on the brush of the list. IE, if you want a brush for cloning (you can have several for several ways of cloning, etc), you can do so, and clicking on the brush on the list will swap you to clone tool, in your cursor. Now, is not exactly what you asked, but might help you to make a workflow that works for you. ] But what you mention might be a bug. Sometimes, when selecting a new brush from the brush list, it does not take the new brush, you keep painting with the one you were using before clicking another. This gets solved by just clicking again on it, or several times (just not as fast as double clicking, or you'd trigger the brush properties dialog). The bug happens rarely (but often enough to replicate it in 2 minutes), often when having painted more than one stroke. And is (temporarily) fixed how I said.
  16. 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).
  17. 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.
  18. 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.
  19. 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.
  20. I do that with Inkscape - Designer (but several of those features are now in Designer).
  21. 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.
  22. 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:
  23. @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.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.