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,787
  • Joined

6 Followers

Profile Information

  • Gender
    Male
  • Location
    Spain
  • Interests
    Illustration, graphic design (web and print), game artwork (every profile), comic creation, 2D/3D animation, 3D modeling, pixel art (UI and games), web design, web development.
  • Member Title
    SrPx

Recent Profile Visitors

7,880 profile views
  1. 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...
  2. 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.
  3. 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 :
  4. 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.
  5. @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.
  6. 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.
  7. 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.
  8. 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).
  9. 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.
  10. 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.
  11. 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.
  12. I do that with Inkscape - Designer (but several of those features are now in Designer).
  13. 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.
  14. 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:
×
×
  • 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.