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

VeganPete

Members
  • Posts

    42
  • Joined

  • Last visited

Everything posted by VeganPete

  1. That's great. They have my name and address and a log of this entire forum thread and the accompanying email correspondence - I'll look forward to any Court Proceedings it'll be great to see which side it falls on - the vendor or the consumer. Just so you know - saying you're going to download cracked software is not illegal, however - they've actually taken my money, they've not provided a service I paid for, they have not offered the support I've paid for and they have refused to refund the payment and broken GPDR rules by contacting me with marketing - asking me for more money for updated software - all those things are unlawful. So take your keyboard-warrior fantasy version of a disgruntled hacker going prison - and actually push for a real prosecution - lets see what happens in the real world.
  2. Not sure why you (Affinity/Serif) emailed me again asking for money, despite me having already opted out marketing emails. The support for V1 was atrocious, as are the updates. Like I said (above) with V1, you broke it and couldn't be bothered to fix it - you expected me to roll back to a much older version, even though I'd paid for support up to V2. You preferred to argue with me (and others on this thread instead). You've now made V2 which presumably (probably not) fixes the fatal bug in V1 that so many of us complained about - but now you expect us all to pay $120 for those bug fixes and a new GUI? Er, no. Like I said to you in the past (and in reply to your, "Buy V2 Now!" email) - I'll be grabbing a cracked version of V2 - The Pirate Bay offers better support for your software (for free). Now F**king take me off your marketing email and don't ask me for any more money or I'll consider pursuing this as harassment or consider hitting you with an LOIC, DDOS or MailBomb campaign.
  3. ̶W̶̶̶a̶̶̶s̶̶̶ ̶̶̶j̶̶̶u̶̶̶s̶̶̶t̶̶̶ ̶̶̶t̶̶̶h̶̶̶i̶̶̶n̶̶̶k̶̶̶i̶̶̶n̶̶̶g̶̶̶ ̶̶̶-̶̶̶ ̶̶̶h̶̶̶a̶̶̶s̶̶̶ ̶̶̶a̶̶̶n̶̶̶y̶̶̶o̶̶̶n̶̶̶e̶̶̶ ̶̶̶t̶̶̶r̶̶̶i̶̶̶e̶̶̶d̶̶̶ ̶̶̶i̶̶̶n̶̶̶s̶̶̶t̶̶̶a̶̶̶l̶̶̶l̶̶̶i̶̶̶n̶̶̶g̶̶̶ ̶̶̶A̶̶̶f̶̶̶f̶̶̶i̶̶̶n̶̶̶i̶̶̶t̶̶̶y̶̶̶ ̶̶̶t̶̶̶o̶̶̶ ̶̶̶a̶̶̶ ̶̶̶R̶̶̶A̶̶̶M̶̶̶ ̶̶̶d̶̶̶i̶̶̶s̶̶̶k̶̶̶ ̶̶̶t̶̶̶o̶̶̶ ̶̶̶t̶̶̶r̶̶̶y̶̶̶ ̶̶̶t̶̶̶o̶̶̶ ̶̶̶i̶̶̶m̶̶̶p̶̶̶r̶̶̶o̶̶̶v̶̶̶e̶̶̶ ̶̶̶i̶̶̶t̶̶̶'̶̶̶s̶̶̶ ̶̶̶s̶̶̶l̶̶̶u̶̶̶g̶̶̶g̶̶̶i̶̶̶s̶̶̶h̶̶̶ ̶̶̶p̶̶̶e̶̶̶r̶̶̶f̶̶̶o̶̶̶r̶̶̶m̶̶̶a̶̶̶n̶̶̶c̶̶̶e̶̶̶?̶̶̶ ̶̶̶ ̶̶̶I̶̶̶'̶̶̶v̶̶̶e̶̶̶ ̶̶̶h̶̶̶e̶̶̶a̶̶̶r̶̶̶d̶̶̶ ̶̶̶y̶̶̶o̶̶̶u̶̶̶ ̶̶̶c̶̶̶a̶̶̶n̶̶̶ ̶̶̶g̶̶̶e̶̶̶t̶̶̶ ̶̶̶a̶̶̶n̶̶̶ ̶̶̶a̶̶̶v̶̶̶e̶̶̶r̶̶̶a̶̶̶g̶̶̶e̶̶̶ ̶̶̶2̶̶̶0̶̶̶0̶̶̶%̶̶̶ ̶̶̶s̶̶̶p̶̶̶e̶̶̶e̶̶̶d̶̶̶ ̶̶̶i̶̶̶m̶̶̶p̶̶̶r̶̶̶o̶̶̶v̶̶̶e̶̶̶m̶̶̶e̶̶̶n̶̶̶t̶̶̶ ̶̶̶o̶̶̶v̶̶̶e̶̶̶r̶̶̶ ̶̶̶a̶̶̶ ̶̶̶t̶̶̶o̶̶̶p̶̶̶-̶̶̶o̶̶̶f̶̶̶ ̶̶̶-̶̶̶t̶̶̶h̶̶̶e̶̶̶-̶̶̶r̶̶̶a̶̶̶n̶̶̶g̶̶̶e̶̶̶ ̶̶̶S̶̶̶S̶̶̶D̶̶̶ ̶̶̶b̶̶̶y̶̶̶ ̶̶̶i̶̶̶n̶̶̶s̶̶̶t̶̶̶a̶̶̶l̶̶̶l̶̶̶i̶̶̶n̶̶̶g̶̶̶ ̶̶̶t̶̶̶o̶̶̶ ̶̶̶R̶̶̶A̶̶̶M̶̶̶.̶̶̶ ̶̶̶ ̶̶̶O̶̶̶b̶̶̶v̶̶̶i̶̶̶o̶̶̶u̶̶̶s̶̶̶ ̶̶̶d̶̶̶o̶̶̶w̶̶̶n̶̶̶s̶̶̶i̶̶̶d̶̶̶e̶̶̶ ̶̶̶i̶̶̶s̶̶̶ ̶̶̶t̶̶̶h̶̶̶a̶̶̶t̶̶̶ ̶̶̶t̶̶̶h̶̶̶e̶̶̶ ̶̶̶R̶̶̶A̶̶̶M̶̶̶ ̶̶̶i̶̶̶s̶̶̶ ̶̶̶t̶̶̶h̶̶̶e̶̶̶n̶̶̶ ̶̶̶r̶̶̶e̶̶̶s̶̶̶e̶̶̶r̶̶̶v̶̶̶e̶̶̶d̶̶̶ ̶̶̶a̶̶̶s̶̶̶ ̶̶̶a̶̶̶ ̶̶̶D̶̶̶i̶̶̶s̶̶̶k̶̶̶D̶̶̶r̶̶̶i̶̶̶v̶̶̶e̶̶̶ ̶̶̶a̶̶̶n̶̶̶d̶̶̶ ̶̶̶w̶̶̶o̶̶̶n̶̶̶'̶̶̶t̶̶̶ ̶̶̶b̶̶̶e̶̶̶ ̶̶̶a̶̶̶l̶̶̶l̶̶̶o̶̶̶c̶̶̶a̶̶̶t̶̶̶e̶̶̶d̶̶̶ ̶̶̶a̶̶̶s̶̶̶ ̶̶̶s̶̶̶y̶̶̶s̶̶̶t̶̶̶e̶̶̶m̶̶̶ ̶̶̶R̶̶̶A̶̶̶M̶̶̶ ̶̶̶-̶̶̶ ̶̶̶b̶̶̶u̶̶̶t̶̶̶ ̶̶̶i̶̶̶f̶̶̶ ̶̶̶y̶̶̶o̶̶̶u̶̶̶ ̶̶̶h̶̶̶a̶̶̶v̶̶̶e̶̶̶ ̶̶̶1̶̶̶6̶̶̶G̶̶̶B̶̶̶ ̶̶̶o̶̶̶r̶̶̶ ̶̶̶m̶̶̶o̶̶̶r̶̶̶e̶̶̶ ̶̶̶R̶̶̶A̶̶̶M̶̶̶,̶̶̶ ̶̶̶i̶̶̶t̶̶̶ ̶̶̶m̶̶̶a̶̶̶y̶̶̶b̶̶̶e̶̶̶ ̶̶̶w̶̶̶o̶̶̶r̶̶̶t̶̶̶h̶̶̶ ̶̶̶c̶̶̶r̶̶̶e̶̶̶a̶̶̶t̶̶̶i̶̶̶n̶̶̶g̶̶̶ ̶̶̶a̶̶̶ ̶̶̶v̶̶̶i̶̶̶r̶̶̶t̶̶̶u̶̶̶a̶̶̶l̶̶̶ ̶̶̶d̶̶̶r̶̶̶i̶̶̶v̶̶̶e̶̶̶ ̶̶̶(̶̶̶u̶̶̶s̶̶̶i̶̶̶n̶̶̶g̶̶̶ ̶̶̶R̶̶̶A̶̶̶M̶̶̶)̶̶̶ ̶̶̶j̶̶̶u̶̶̶s̶̶̶t̶̶̶ ̶̶̶f̶̶̶o̶̶̶r̶̶̶ ̶̶̶A̶̶̶f̶̶̶f̶̶̶i̶̶̶n̶̶̶i̶̶̶t̶̶̶y̶̶̶ ̶̶̶p̶̶̶e̶̶̶r̶̶̶f̶̶̶o̶̶̶r̶̶̶m̶̶̶a̶̶̶n̶̶̶c̶̶̶e̶̶̶ ̶̶̶b̶̶̶o̶̶̶o̶̶̶s̶̶̶t̶̶̶s̶̶̶.̶̶̶ ̶̶̶I̶̶̶f̶̶̶ ̶̶̶y̶̶̶o̶̶̶u̶̶̶ ̶̶̶d̶̶̶o̶̶̶ ̶̶̶f̶̶̶i̶̶̶n̶̶̶d̶̶̶ ̶̶̶y̶̶̶o̶̶̶u̶̶̶ ̶̶̶n̶̶̶e̶̶̶e̶̶̶d̶̶̶ ̶̶̶m̶̶̶o̶̶̶r̶̶̶e̶̶̶ ̶̶̶s̶̶̶y̶̶̶s̶̶̶t̶̶̶e̶̶̶m̶̶̶ ̶̶̶R̶̶̶A̶̶̶M̶̶̶ ̶̶̶a̶̶̶f̶̶̶t̶̶̶e̶̶̶r̶̶̶w̶̶̶a̶̶̶r̶̶̶d̶̶̶s̶̶̶,̶̶̶ ̶̶̶y̶̶̶o̶̶̶u̶̶̶ ̶̶̶c̶̶̶o̶̶̶u̶̶̶l̶̶̶d̶̶̶ ̶̶̶u̶̶̶s̶̶̶e̶̶̶ ̶̶̶a̶̶̶ ̶̶̶a̶̶̶ ̶̶̶f̶̶̶l̶̶̶a̶̶̶s̶̶̶h̶̶̶-̶̶̶d̶̶̶r̶̶̶i̶̶̶v̶̶̶e̶̶̶ ̶̶̶(̶̶̶o̶̶̶r̶̶̶ ̶̶̶S̶̶̶D̶̶̶)̶̶̶ ̶̶̶c̶̶̶a̶̶̶r̶̶̶d̶̶̶ ̶̶̶a̶̶̶s̶̶̶ ̶̶̶s̶̶̶y̶̶̶s̶̶̶t̶̶̶e̶̶̶m̶̶̶R̶̶̶A̶̶̶M̶̶̶ ̶̶̶b̶̶̶y̶̶̶ ̶̶̶u̶̶̶s̶̶̶i̶̶̶n̶̶̶g̶̶̶ ̶̶̶W̶̶̶i̶̶̶n̶̶̶d̶̶̶o̶̶̶w̶̶̶s̶̶̶-̶̶̶R̶̶̶e̶̶̶a̶̶̶d̶̶̶y̶̶̶-̶̶̶B̶̶̶o̶̶̶o̶̶̶s̶̶̶t̶̶̶ ̶̶̶(̶̶̶o̶̶̶r̶̶̶ ̶̶̶a̶̶̶s̶̶̶ ̶̶̶a̶̶̶ ̶̶̶l̶̶̶a̶̶̶s̶̶̶t̶̶̶ ̶̶̶r̶̶̶e̶̶̶s̶̶̶o̶̶̶r̶̶̶t̶̶̶ ̶̶̶y̶̶̶o̶̶̶u̶̶̶ ̶̶̶c̶̶̶o̶̶̶u̶̶̶l̶̶̶d̶̶̶ ̶̶̶u̶̶̶s̶̶̶e̶̶̶ ̶̶̶a̶̶̶ ̶̶̶p̶̶̶a̶̶̶g̶̶̶i̶̶̶n̶̶̶g̶̶̶ ̶̶̶f̶̶̶i̶̶̶l̶̶̶e̶̶̶ ̶̶̶o̶̶̶n̶̶̶ ̶̶̶a̶̶̶ ̶̶̶h̶̶̶a̶̶̶r̶̶̶d̶̶̶d̶̶̶i̶̶̶s̶̶̶k̶̶̶ ̶̶̶i̶̶̶n̶̶̶s̶̶̶t̶̶̶e̶̶̶a̶̶̶d̶̶̶)̶̶̶.̶̶̶ ̶̶̶ ̶̶̶T̶̶̶h̶̶̶e̶̶̶ ̶̶̶p̶̶̶e̶̶̶r̶̶̶f̶̶̶o̶̶̶r̶̶̶m̶̶̶a̶̶̶n̶̶̶c̶̶̶e̶̶̶ ̶̶̶o̶̶̶f̶̶̶ ̶̶̶t̶̶̶h̶̶̶e̶̶̶ ̶̶̶R̶̶̶A̶̶̶M̶̶̶ ̶̶̶d̶̶̶i̶̶̶s̶̶̶k̶̶̶ ̶̶̶w̶̶̶o̶̶̶u̶̶̶l̶̶̶d̶̶̶ ̶̶̶m̶̶̶o̶̶̶r̶̶̶e̶̶̶ ̶̶̶t̶̶̶h̶̶̶a̶̶̶n̶̶̶ ̶̶̶l̶̶̶i̶̶̶k̶̶̶e̶̶̶l̶̶̶y̶̶̶ ̶̶̶o̶̶̶u̶̶̶t̶̶̶w̶̶̶e̶̶̶i̶̶̶g̶̶̶h̶̶̶ ̶̶̶t̶̶̶h̶̶̶e̶̶̶ ̶̶̶s̶̶̶l̶̶̶i̶̶̶g̶̶̶h̶̶̶t̶̶̶ ̶̶̶l̶̶̶o̶̶̶s̶̶̶s̶̶̶ ̶̶̶o̶̶̶f̶̶̶ ̶̶̶a̶̶̶v̶̶̶a̶̶̶i̶̶̶l̶̶̶a̶̶̶b̶̶̶l̶̶̶e̶̶̶ ̶̶̶s̶̶̶y̶̶̶s̶̶̶t̶̶̶e̶̶̶m̶̶̶ ̶̶̶R̶̶̶A̶̶̶M̶̶̶ ̶̶̶-̶̶̶ ̶̶̶e̶̶̶s̶̶̶p̶̶̶e̶̶̶c̶̶̶i̶̶̶a̶̶̶l̶̶̶l̶̶̶y̶̶̶ ̶̶̶w̶̶̶h̶̶̶e̶̶̶n̶̶̶ ̶̶̶t̶̶̶h̶̶̶e̶̶̶ ̶̶̶u̶̶̶s̶̶̶e̶̶̶d̶̶̶ ̶̶̶R̶̶̶A̶̶̶M̶̶̶ ̶̶̶i̶̶̶s̶̶̶ ̶̶̶r̶̶̶e̶̶̶-̶̶̶i̶̶̶n̶̶̶s̶̶̶t̶̶̶a̶̶̶t̶̶̶e̶̶̶d̶̶̶ ̶̶̶a̶̶̶s̶̶̶ ̶̶̶R̶̶̶e̶̶̶a̶̶̶d̶̶̶y̶̶̶-̶̶̶B̶̶̶o̶̶̶o̶̶̶s̶̶̶t̶̶̶/̶̶̶P̶̶̶a̶̶̶g̶̶̶e̶̶̶-̶̶̶F̶̶̶i̶̶̶l̶̶̶e̶̶̶ ̶̶̶R̶̶̶A̶̶̶M̶̶̶.̶̶̶ ̶̶̶ ̶̶̶M̶̶̶i̶̶̶g̶̶̶h̶̶̶t̶̶̶ ̶̶̶b̶̶̶e̶̶̶ ̶̶̶w̶̶̶o̶̶̶r̶̶̶t̶̶̶h̶̶̶ ̶̶̶a̶̶̶ ̶̶̶t̶̶̶r̶̶̶y̶̶̶.̶̶̶ Scrap that - I just created a RAM drive and installed Affinity Photo to it. The program does boot and and run A LOT quicker from RAM than SSD - but it still slows to a crawl as soon as windows file explorer is called to open/save a file. I think the best fix would be for Affinity to build their own file browser for future versions.
  4. Thanks R C-R. If it's there as a feature, do you know if there is any way to turn it off? Possibly the devs can add an option for it in a future update sometime. Thinking about it, I'm sure it's handy for most people - for me it's a little bit of a hindrance - I use affinity to make transparent png's and transparent screen bezles for game overlays and layered art. It's usually only after import to the game engine that I notice the stray lines that weren't there by my design - or after a final render of an art piece, on closer inspection, I'll notice something not quite as I intended. For quite a while, I assumed the game engine was at fault, so I was offsetting the position and scale by a few pixels to move the lines off the screen - this affected the resolution, so I had to deliberately make the images 1 pixel larger and force sharpness and use a forced aspect-ratio in the game engine (which affects performance). The ambiera forum suggested I inspect my images in case the lines were actually part of the image. They were correct. Once I realsied it was actually the image at fault, I then had to go back and edit them (or worst case scenario, create them again from scratch - although in most cases, I had saved the .aphoto file along with the render). A similar thing occasionally happens when I select text, under certain circumstances, it switches back to the previously used colour - rather than the colour I currently have selected. I think it's related but it may be a different issue. If I could switch those features off, it would fit my workflow a lot more reliable. I suppose as a workaround, I can go back and double check everything before a final render and just manually erase the lines with the marquee selector and cut tool (possible even the eraser with a steady hand) if they're rasterised - or I can just try to get in the habit of adding the extra steps to revert it back to zero stroke width whenever I click on the switch button - or I suppose I can even add a "dummy" raster-layer which I can select prior to making make any changes to colour (as it only happens with vector layers) - then once the changes are made safely (without adding the previously-stored width), I can then switch back to the vector layer I was working on. As a final option, I can convert all the vectors and text to rasters so this doesn't happen at all, then if I want to go back and edit them in the future, I can just delete the layers and re-draw them all as vectors again. Thanks.
  5. As for the second part of my post.... if you manually change the stroke width to any value (say 10), then manually set it back to zero, the stroke width will remain at zero, even if the swap arrow is clicked - it's as if it remembers the last setting and applies it when the swap arrow is clicked. It's a workaround but also may help to bug fix it - assuming indeed it is a bug and not a short-cut/feature. Hope that makes sense, Sorry I'm not too great at explaining.
  6. Yes, possibly my workflow is non-standard or maybe I just don't fully understand the UI properly yet. For me, if I click the little circles (swatches?) of colour (black/white in example - not the red sample colour or the transparency) or if I click the swap front/back colour arrows (next to the colour picker/pipette), it will add an outline (always 1 pixel wide) to whichever shape layer is selected in the "layers" window. This is mildly frustrating when I want to retrospectively change the colour of a shape, as I then also often have to delete the extra outline stroke that's generated. I do notice it doesn't happen all the time so it's probably something I'm doing wrong. bandicam 2022-03-14 16-14-08-709.mp4
  7. If I select Stroke width as "none, then draw a shape..... If I later click the colour pallete, is it meant to be retrospectively adding an outline? If not, you can reproduce the problem by clicking shape, clicking "stroke width - none", draw the shape, click the colour pallet swatch. It adds an outline to previously drawn shapes, even though stroke width was set to zero at the time of drawing - is that normal or is it a bug? Thanks. (PS- app restart didn't fix). I can make a video to demonstrate if required).
  8. Exactly my point - If I set the stroke width to "none" in the shape's toolbar settings, surely it shouldn't be drawing an outline at all. To remove it, I then have to select the shape, then change the stroke with to "any value" then click "none". It's as if (sometimes) it ignores the fact that I had set "stroke width" to "none" prior to drawing the shape. Another glitch along the same theme - if I select a fill colour, it sometimes automatically switches back to the outline colour when I draw the shape or write text. It (sometimes) just ignores the fact that I've switched the colour prior to drawing a shape/text.
  9. True but as you can see in the image, strike width was already set to "none".
  10. OK, solved it - you need to increase the stroke with to any value, then click "None" again to turn it off.
  11. Is there a way to draw a shape (a square for example) without it having crappy edges? Seems to be a bug. Whenever I draw a layer, it adds an edge with the secondary colour - even if "Stroke width is 0" and even if "Outline FX is off". There are quite a few annoying little glitches like this. 2 other annoyances are: Cropping the image usually makes it extremely blurry (regardless of resolution) - probably an issue with the Affinity's resampling algorithm. Cropping an image then screws up any subsequent filters (such as affine) - because the filters are calculated using the original canvas size, not the newer cropped one. Glitch.afphoto
  12. @PeteMacca -Also was advised that if you have disabled Windows search, you should also disable "File Indexing". Disabling/enabling the "Search Index" does not harm your system and is also a 1-click action, if ever you'd like to test if it improves your Affinity Performance. "If you have a decent CPU/GPU combo (or if you have an SSD drive), you should turn off "file indexing" (which is "On" by default on Windows 10). Disabling this feature often improves performance of SSD access speeds - especially when you have thousands of individual, small files (such as images/samples/presets etc). With an SSD and decent CPU, the search speed is not hindered by turning off the indexing - but you can get a considerable performance boost (specifically in Windows Explorer - which is called by apps when opening/saving files) as windows does not not need to continuously update a huge index every time a file name/property is created/changed." To confirm the steps I took to improve Affinity Photo Speed: Updated Windows 10 to version 20H2 (No improvement in performance) Checked Firmware/Chipset/Graphics drivers were up to date (Was already up-to-date) Cleaned my desktop of as many non-essential project files as I could (No improvement in performance) Installed the latest Beta version of Affinity (Temporary improvement - went really slow again next day) Set "Nvidia GTX 1060" as the default renderer in Affinity (Was already default but no no real difference when switching to InternalGPU) Disabled "Open CL" Hardware Acceleration for Affinity (After updating Windows, finally being able to enable OpenCL made Affinity slower) Disabled "Windows Search" (Main Fix - massively sped up Affinity and all other software) Disabled "File Indexing" (Seems to have sped up my entire PC) Turned off "Thumbnail Previews" when Affinity called "Windows File Explorer" with "Open File" command (Small Boost when browsing files with Affinity)
  13. I think this is the link I used to switch off Windows Explorer Search.... https://www.tenforums.com/performance-maintenance/15702-file-explorer-slow-never-loading-solution.html I think this is the conversation I found about Affinity being slow..... https://www.dpreview.com/forums/thread/4120727
  14. Yes, I'll t find it for you later today. I didn't save the link but it will be in my browser history. It'll take me a while to find it again because I spent quite a few hours trawling through various solutions until I found that one saying windows search feature trashes Windows Explorer if there are a lot of files. Windows search service can be re-enabled with a click so I was able to directly compare before/after performance and several other people said it had helped them. I had switched to Krita but didn't like the workflow as much as Affinity Photo, so I went on a quest to find a solution. I realised it was probably a windows related problem because even the oldest Version of Affinity Photo I could find suffered the same problem, when in the past, it had worked perfectly well. It seems that recent windows updates have changed some of the core features of Explorer which have retrospectively affected Affinity performance. Not sure why this problem manifests for some people and not others but it brings Affinity to a crawl and can be completely unusable. For me, disabling Windows Search fixed it and (so far) seems to be a permanent fix.
  15. Spoke too soon; the beta version still has the exact same problem. As a few people have mentioned previously, it does appear to be a Windows10 problem, not an affinity problem - Affinity doesn't have a built-in file-browser, instead it calls the Windows File Explorer. This is problematic as it makes Affinity dependent on Windows File Explorer and susceptible to any 3rd party flaws therein. I advise the Serif developers to incorporate their own file-browser to improve speed and stability of the software on various platforms. In the mean-time, there is a reliable workaround (for Windows). After exhausting help here, I managed to find this response on another graphics forum which also mentioned Affinity being unusably slow on Windows 10. This helped to speed up Affinity and appears to have fixed the issue for me... 1. Hold Win+r to open run 2. Type msconfig and hit ok or enter 3. Click Services 4. Navigate to Windows search (you can sort the list in descending alphabetical order) 5. Uncheck tickbox 6. Click apply then ok 7. Select to restart now I hope this helps resolve the issue for others that are experiencing this deal-breaking issue. If not, I suggest trying Krita until it gets fixed in future updates - Krita looks similar to Affinity and is free. Personally I prefer Affinity, especially now it's working again.
  16. Ah, OK thank you! I'll have to turn off indexing as I can't really move the files without trashing all my projects.
  17. Still had some slow-down even with Nvidia HA option enabled but I think I've managed to fix it by going to "file>open" then select "View" and disable "navigation and "preview option". I think the problem is that (as a hobbyist artist and music maker and game dev), I have thousands of nested folders (folders within folders) for images, audio samples, VSTi presets and 3D model assets - both on the desktop and in my downloads folders. Whilst it hasn't caused any problems before, these nested folder seem to wreak havoc with Affinity photo - turning off "Navigation" seems to have fixed it.. so it may be worth a try for others who are experiencing similar problems.
  18. Boom! Beta version works flawlessly! HA is enabled and no slowdown at all. Nice one Walt - you're a star. Really appreciate the help.
  19. Thanks Walt. Yes, I did manage to successfully update to Win 10.0.19 but by then I'd I'd already reverted to the older version of Affinity. It was so stressful yesterday - lost an entire day to updates and re-installs etc. I'll try today to see if hardware acceleration can be enabled on the new Affinity Photo and see if enabling OpenCL addressed any of the issues now my Windows has updated to a supported version. Regardless, the old version of Affinity Photo is perfect in all regards except one - none of my newer projects will open any more - they all say something along the lines of "This Project uses features from a newer version of Affinity Photo". So, as suggested, I guess I'll to try the new version of Affinity Photo one last time. If it doesn't work, I've no issues with using an older version and just abandon those projects (they're all rendered to file anyway - so they're essentially just backups for if I wanted to edit anything) - the old version is so stable and outperforms the new version (even without the Hardware Acceleration) that I've made my peace with not being able to upgrade. Thanks.
  20. @Richard No, OpenCL is not "on by default". Please actually go back and read my comments and take a look at my screenshots instead of making the same incorrect assumptions as Walt and everyone else. If I try to manually enable HA, it says: "Your operating system is not supported". It's always been disabled on my system with Affinity Photo, even if it does default as "on" with other versions of Windows 10. SO, as I said before "try disabling it" is not a solution because it was never enabled. The only working solution for me (and many others I've seen on the forum) was to uninstall the newer versions and install an older version 1.8.5 (and then hack the registry to disable the annoying "update now" nag screen).
  21. Same for me, doesn't fix it. Just had a few freezes since - so can confirm it's not a valid workaround. I guess I'll just go back to a much older version to fix it. Interesting, when I searched for an older version of Affinity, it took me to this link - someone else with the exact same unresolved issue - so I'll link it here because it's unlikely to get fixed any time soon. For anyone facing the same issue and doesn't want to be harangued on the forum, just download an older version (as mentioned there and on the Affinity Photo "Unsupported Machine Configuration" Warning) As Chris B says -Affinity Photo version 1.8.5 seems to be the last version which worked with Windows v10.0.18 and GTX 1060)...
  22. "%AppData\Roaming\Affinity\Photo\1.0\CrashReports\reports\%" for me, is an empty folder, even if I show hidden files/folders. Probably because the issue (for me) is that it steadily slows down to a crawl and sometimes completely freezes my system, needing a hard-reset (which I hate doing because I don't think it's particularly healthy for the system). If I catch it in time, I can get away with opening the task manager and closing Affinity Photo from there (the close button often wont respond - especially if I open/import a file). It's often as if I'm running it on a pocket PC with very little RAM, rather than a power PC. Affinity Photo used to fly, now it just crawls.
  23. OK so I think I've found a possible workaround for your dev team to fix the bug in Affinity Photo 1.10.4. If I use Affinity Photo and try to use it as normal, it will crash early on (every session - guaranteed) - especially if I use "File>Open" or "File>Import". If however, I open Windows File Explorer first and minimise it, then open Affinity Photo. It doesn't crash at all. If I drag-and-drop files from Desktop or Windows File Explorer onto Affinity Photo, also works fine. In conclusion, the bug is definitely something to do with the file-browser or the way affinity caches its thumbnails- as it looks and behaves completely differently when opened natively in Windows and when "called" from inside Affinity Photo.
×
×
  • 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.