Jump to content


  • Content count

  • Joined

  • Last visited

About thomasp

  • Rank

Profile Information

  • Gender
    Not Telling
  • Location

Recent Profile Visitors

334 profile views
  1. thomasp

    Clone Brush no longer working

    Works for me: Alt+LMB on Intuos Pro M 6.30.30-2 on High Sierra
  2. Not sure if this is a feature or a bug but currently AP lets me draw on hidden layers - that seems like very unusual software behaviour to me. IMO a hidden layer should stay off limits for any canvas manipulation until unhidden by the user, else it's too easy to accidentially ruin one's work without noticing (until too late).
  3. One more voice for Targa export (with alpha channel).
  4. Yes please, so much time spent recentering the canvas inside its window borders.
  5. In separated window mode the context help bar attached to the document window vanishes: 1. With AP and active document in focus and a tool active it displays as expected 2. Switching to another app (like Finder) and switching back to AP leads to the bar staying empty until another tool is chosen (applies to Designer 1.7.0 as well) Just to be clear: I'm talking about this window element (not sure what it's called):
  6. Thanks for finally making a release available that has all the improved brush behaviour and performance improvements. I am so unable to use 1.6.7 for painting (nor anything else really) after being spoiled by the beta. Is it possible to simply copy over all preferences manually - including window placement and so on and just have them work in the release (same for Windows)?
  7. thomasp

    Beta 122: Batch processing issues

    Certainly! I'm seeing these issues when running batches on -TGA files, typically 2k-4k video resolution out of 3D rendering packages, no alpha channel -JPG files, up to 24 Mpix resolution, straight out of my DSLR (Pentax K3) The actions I'm using are just simple rescale and export operations - these are typical settings: I've just run with these settings multiple times over the same list of 400 TGA files in 2560x1440 (14,7 MB per file). Results - 1st run: 400 files generated, 1 zero byte file: frame 211 2nd run: 399 files generated (!), missing file: frame 260 3rd run: 400 files generated, all ok 4th run: 400 files generated, 2 zero byte files: frame 196, frame 255 5th run: 400 files generated, 3 zero byte files: frame 66, frame 114, frame 185 This was on AP Beta 125, macOS 10.13.6, 6-core Mac Pro 6,1 (aka 'Trashcan'), 64 GB RAM. Source and target in this test was the internal NVMe drive (Samsung 970 Pro, APFS). I had the zero-bytes issue happen on external USB3 spinning disks (FAT) as well.
  8. thomasp

    Beta 122: Batch processing issues

    In Beta 125 parallel processing no longer omits files, yay! However, zero-byte files are still a thing for me.
  9. Running a batch on file sequences I can observe these behaviours: Running a batch sometimes - not always - produces zero-byte files (one or two out of around 200 images in my case). The exact files that ends up as zero bytes do not stay the same when I run the same batch several times over. With the 'Parallel processing' option ticked there are usually several files missing on longer batches, also zero byte files may happen. These issues have been in the beta for some time now and I believe at least the parallel processing leaving out files was brought up before.
  10. Are you referring to the 'use SHIFT to cycle tools' option?
  11. Don't worry, this isn't one of these requests for a Linux port (not that I'd complain). I'm just curious if anyone has tried running the Affinity products through WINE or any other solution on Linux: ideal choice of distro, performance impressions, problems encountered, anything else that would be good to know? I mainly use Affinity on Mac these days but do have Windows licenses that I'd like to put to proper use - and seeing as the Macbook Pro is not what it used to be I'm seriously considering a Linux based laptop as my next portable, hence the question.
  12. thomasp

    Beta .112: random crashes

    Thanks Chris, I'll try the older builds this week (before toying around with the Wacom driver) and let you know. In the last couple days I had little opportunity to use the Beta but just today experienced repeated crashes with Batch process on the same list of files - which has never crashed before in any Beta I tried. Simple batch (resize and save to JPG) that I have been using since whenever, no special characters in the file names or anything. The stable build 1.6.11 just chews through it no issue. I have another crash dump log but not sure how helpful these actually are?
  13. thomasp

    Beta .112: random crashes

    Well, I could - but is this really likely to remedy these crashes? Asking because I have a love-hate relationship with Wacom drivers and don't trust their latest & greatest much. These I have now do seem to do the job in general though. No odd behaviour elsewhere, no sleep issues either. Wish they all worked like this. I'd be down for trying out .109 or older again though to see where it started to go south or if my memory is just a bit rose-tinted.
  14. thomasp

    Beta .112: random crashes

    Hey Chris, it's 6.3.30-2 from sometime in 2018.