Jump to content


  • Posts

  • Joined

  • Last visited

  1. Hi Callum, I loaded the beta at defaults and over all it was a HUGE improvement. I looked in the prefs and see that by default most of them are turned up to their highest settings. Many of the brushes seem much faster even at very large sizes (1-2k). A few brushes are still really slow even at default sizes and have that faceted look when drawing fast strokes like the Matte Acrylic 01 brush (first in list by default AFAIK) and the Comics Ink brush. I haven't tested them all but maybe there is a common feature enabled for some of them that is still slowing things down? Nearest neighbor didn't seem to change things much for those brushes. Over all though it's much better than before so this beta is looking really promising on that front. 👍
  2. I've tried restoring defaults, using openCL, turning windows ink on and off etc. but no mater what my brush in Affinity Photo is REALLY slow to update. Doesn't seem to mater if it's a basic brush or a complex one. Size only effects it somewhat, but even a tiny brush has issues. Canvas size doesn't seem to be an issue. a 2k x 2k image has the same brush issues as a 5k x 5k. With a mouse it's a little slow. With my wacom tablet, it's nearly unusable. Same canvas size and similar brushes in the ipad version works flawlessly. Photoshop on the same PC is plenty fast. Oddly using a raster brush in affinity designer has none of these issues or they're much less so. Any ideas of what to try to get the speed back up? Version on windows. 1950x, 64GB RAM, 2070GTX
  3. I guess I don't get why the OS build should effect this at all? I'd think it would be more related to video card driver or something. That's how it works for V-ray and Octane for me. Why is this feature so closely tied to the OS build? I'm stuck on the 1909 line with my 2070 RTX until they move out of beta preview on 21H1 since I value stability above new features. Is there some windows graphics driver or something I can update separately? Latest PS lets me use OpenCL. Not that it matters much as I don't really trust anything graphics acceleration much when it comes to the PS team LOL! I'm not ranting or anything, just more curious. I'm not really as informed about OpenCL vs. CUDA, RTX, Optix and all the other Nvidia happenings.
  4. To use a number of functions (one being pattern layers) on curves, procedural shapes or layers with certain live filters on them we have to rasterize them first. It would be really nice if there was a rasterize live filter. We could maybe place that above a stack or in a group and then maybe Affinity could some how rasterize the contents so we could use them more widely? Ideally this rasterizing would happen on the fly anyway and we wouldn't have to even think about a live rasterize filter or ever having to rasterize anything except for specific export reasons, but baring that maybe we could have some kind of rasterizing live filter?
  5. Any news on getting a gradient to flow along the path of a curve like some other apps can use? One of those small things that sends me back to Illustrator at times. I use these mainly for effects in AE or in substance designer where you can drive certain things based on gradient inputs. Things like animated writing etc. Thanks for the new additions to 1.9 BTW- really like the select same as tools etc.
  6. Thanks for adding the select same and select object functions. Those are a few of the small things that had me sometimes sticking in Illustrator more than designer. I know they're not the most "sexy" features but they're real work horses. Thank you!
  7. LOL, I get how it works, it just honestly is really, really weird. It's like the parent even though visually there is no indication of that. I have no comparison to draw from any other software that works exactly this way. I mean, if it was a node based editor, I could probably see it still linked up to some channels, but it's opaque to the user. IMHO, if I disable the layer, then to the comp the layer shouldn't be there and should be passed through, but in Affinity it's still "there" and acting like it's the parent of everything. Very, very confusing. I think for me I'll just delete a pixel layer in this usage case instead of "disabling" it or throwing in some junk layer at the bottom of a group that is always on, else I'm bound to run into some confusion on more complex (to me) comps.
  8. I'm not trying to fight the system or anything, just want to know how it works. 😁 I know now how to get it to do what I want now, but I was more curious as to why a pixel layer even when disabled, acts like a mask in a group. I figured if I disabled it, then the group would act like it does without a pixel layer, but instead it just acts like the pixel layer has a black alpha channel and everything in the group disappears. This is the only part I can't really get my head around as a design feature.
  9. I'm sure this has been talked about a lot so feel free to point me to resources. I'm only asking here because all the videos I've watched don't address these things AFIAK. OK, so say you have a group, and in it you have adjustment layers. Without a pixel layer in the group all the adjustments pass through to what is underneath as expect. If you put a pixel or shape layer in the group, it acts like a mask on the group. This is different than PS but I can get my head around it. OK so far. What is weird is...why does it effect the groups visibility too? If I disable that pixel layer, everything in the group disappears. I can get around this with more sub groups and masks, but I'm just wondering what the reasoning is. I'd think if I disabled the pixel layer, the rest of the group contents would just act like I'd never put it in the group. This behavior persists even if I set the pixel layer to have a blending mode so I guess it's only looking at the alpha channel for this part yeah?
  10. After years of using PS for my work I recently started using Affinity Photo for work on my 3D product renderings after some colleagues made me finally take the plunge. My main reasons are: Work in 32bit the whole time vs. 16bit with some 32bit smart objects File sizes that save fast on any of my drives at 100-500mb vs. 3-5GB in PS compressed (saves painfully slow) or 10-15GB uncompressed PS files that only saves fast on my NVME drives. Performance while working. Affinity isn't crazy fast on my files, but it's faster than PS, and the previews are nicer/faster. AMD 1950x and a 2070 RTX system for ref. Affinity has many non-destructive tools. I have only watched a few PS 2021 previews, but most of the things added seem more applicable to photo editing in a photo-retouch work grind way and using AI/machine learning in ways that don't seem to enhance my workflow. Is there anything in there that makes all the tools work in 32bit, enhances performance on large files or cuts down on the file size bloat? I think the only thing I saw of interest to me was the seamless texture painting, but honestly 99% of the time now I'm going to use Substance (which is probably where the tech for PS comes from) or something else for these things. Maybe it will be more useful for pattern designers, though a lot of them will just work in vector using AI or AD or even on the ipad in apps like procreate so this is a bit of a nice to have but not ground breaking IMHO. For me it has nothing to do with the cost as I can easily afford PS and affinity and will continue to do so, it's just more about actual work flow and time. I'm probably not the target audience for either PS or Affinity Photo, but at least Serif seems to take more notice of 3D workflows. We just need an actual cryptomate workflow (not just color ID like the tutorials are showing). 😁
  11. That was it! Didn't event think to look there since I've never edited it. What might have caused it to change? Is it maybe that this was added at some point, but my old preferences which didn't have it, were carried over?
  12. I'm seeing this too. I don't get why it's doing that given the default in Affinity photo is pass through. I'm using 1.8.703 on windows. Has this been fixed yet? I guess I'll check for updates, though I think I'm using the latest build.
  13. I can't seem to get the D keyboard short cut to work in Affinity Photo: "Set Stroke/Fill (or Color 1/Color 2) color selectors to black and white, respectively - D" What should I check to get it to work right?
  14. I'm having this problem too. I go to move nodes and end up moving the control handles on the node instead. The closer the handles are to the node, the worse the problem is and the closer I have to zoom in to change them. Really breaks up the work flow in an unfortunate way. I almost wish there was an option to enable "edit node handles only with finger hold" or something, where if you use a single finger or the pencil it only moves the node, not it's control handles, but if you add a finger held down on the screen, it now moves the handles. Something similar to that might be nice for the ipad work flow.
  15. I like some of the touch and drag options for sizing things. This should probably be taken further if it can be for some options. For instance, it would be really nice if we could touch then drag on the duplicate option to create more duplicates. So as you drag, more are created. This could be really powerful for things like power transforms.
  • 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.