Jump to content
You must now use your email address to sign in [click for more info] ×

dmstraker

Members
  • Posts

    827
  • Joined

  • Last visited

Recent Profile Visitors

5,048 profile views
  1. Thanks, NMF. I'll probably leave it where it is for now as it only happens occasionally and I know how to fix it. The suggestion to configure temp and backup stores on other drives still stands. Not an original idea, but would still make life easier.
  2. I've an SSD C drive, which most people have these days. More than once I've had to trawl through Affinity folders there to root out files clogging up the drive until it becomes unusable. The latest was .affinity/Photo/2.0/temp/personabackstore.dat which was 117Gb. I've also found loads of old files in the autosave folder before now. I'm an old techie and was comfortable doing a name change to check that deletion wouldn't mess up the works. I can imagine people with a creative background being stymied by the problem. More info: On Windows, I got a 'disk full' complaint, along with a list of culpable folders. Affinity was the 1000lb gorilla here. It would be sensible to be able to locate temporary and backup storage on another drive (I have a second SSD just for this purpose). Set it up through Settings. Cheers and best to all you good folks at Serif!
  3. No worries. I found it confusing. Done my duty and reported it. Now over to you. Take care, Dave.
  4. Use an adjustment, eg Curves. Paint black on the mask. Can be seen in mask that appears alongside adjustment in Layers panel. Channels, Right-click (eg) Curves Adjustment Alpha, Fill (this erases black on mask). Mask as appearing in Layers tab is now white and I'd guess should now disappear. It actually disappears next time the layers panel is repainted, eg when moving a layer. Yes, I know, not a biggie. But then you good people have squared away most other things. HNY to all Serifims and Cherubims!
  5. A thought: If shortcuts have been changed, does 2.2 install step back? Looking at Photo/Paint Brush Tool settings, for example, there are no shortcut keys set for changing brush hardness. I've not set these myself, but have changed a number of other settings. It does highlight a potential dilemma, but maybe the install can check for user settings and put the new ones in for each change only if the user has not already set them.
  6. Testing brush improvements on Win10, APh 2.2: Shift + number key now changes flow percentage (in the same way that number key on its own adjusts opacity) WORKS FINE Shift + square brackets now changes hardness in 10% increments DOESN'T WORK (TRIED SHIFT ON BOTH SIDES) Number key in Paint Mixer and Smudge Brush now adjusts strength percentage WORKS FINE Fill with Primary colour has now been set with a default shortcut of Alt/⌥ + Backspace DOESN'T WORK (OK FROM EDIT MENU) Fill with Secondary colour has now been set with a default shortcut of Ctrl/⌘ + Backspace DOESN'T WORK (OK FROM EDIT MENU)
  7. In Procedural Texture, adding Z or R numbers as custom inputs, you can type in a number and it's immediately calculated. The little up/down arrows work fine too. But when you roll the mouse wheel over the number, it is not calculated (and so has no effect).
  8. It's a new one on me and I'm still puzzled as to what exactly might be going on. I've not heard of this happening with other applications. It would be enormously helpful if AP is unable to save remotely that it gave you an option to save locally rather than crashing out. Nevertheless I'm grateful for the knowledge and will follow your advice, Walt. Thanks!
  9. Yes, 2.1.1. Saved to pCloud, a Swiss service and has proved very reliable. How might saving to a server cause such a problem?
  10. I've just lost hours of critical work after "Save failed because ownership of the file could not be verified. The document must now be closed." I re-edited the image. An early save worked. A later save didn't. To say I'm unhappy would be an understatement. Version 2.2.1 Affinity Photo Edit: I tried resaving the original image (a jpg) with different algorithm (Lanczos) and restarted edit. I saved at regular points along the way. Eventually I hit the same barrier. I exported the original jpg as tiff and restarted, with the same effect. I also hit the same problem with a separate image which was a RAW .NEF file.
  11. When a live mask preview is turned on, it still impacts the visible image when the mask is turned off in the layers panel. Effect is also seen when adjustment to which live mask is attached is turned off.
  12. "Save failed because ownership of the file could not be verified." Plus the delightful "The document must now be closed" (with no chance of saving). Boom. Fortunately when I reopened it, it recovered where I was. Got me going for a moment there, chaps.
  13. Well done and thank you to everyone at Serif for a momentous 2022. Please do have a splendid Christmas and New Year break, and try not to think about work too often (difficult, I know). As we say in Wales, Nadolig Llawen a Blwyddyn Newydd Dda (Merry Christmas and Happy New Year).
  14. Looks like it's Windows-specific. Attached is what I saw after loading the Luminosity mask OK.afphoto file to 2.0.3. Thanks for checking on Mac.
  15. Can't remember if I submitted these (also not found on search here, and beta database unavailable): As in attached and starting with gradient layer, black to white along x-axis. Add Luminosity Range Mask and adjust nodes as shown. When curve hits top or bottom edge of adjustment square, the effect is sudden, unexpected and presumably incorrect. Also when blur is increase, an edge effect around the periphery of the image is seen, much as would be found using a Gaussian Blur. It looks like a 'Preserve Alpha' checkbox is needed.
×
×
  • Create New...

Important Information

Terms of Use | 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.