Jump to content


  • Content Count

  • Joined

  • Last visited

  1. ooh, so I don't need to ignore the assistant right? so I have to create pixel layer/curve layer beforehand manually? ok, got it oh, and the crash thing due Appearance Panel visible, is it also fixed on 1.90? -- rad features update btw! nicely done!
  2. thanks for replying. doing it now, and will get back to you if I encounter this again. Oh, and the laggy brush? is it caused by the same event?
  3. Step to reproduce: Open affinity designer (with huion connected) Create a new pixel layer using cmd shift n Strike a brush using drawing pen Undo Strike again (and then it crashed) My file setup was: Filesize: 3MB in iCloud folder Using multiple artboards (two so far) Oh, and really slow brush on the first stroke using drawing tablet. If I release the pen and create another strike, it ran smooth on the second and later. But later on after a while this thing happened again. Please help, thanks. Process: Affinity Designer [48821] Path: /Applications/Affinity Designer.app/Contents/MacOS/Affinity Designer Identifier: com.seriflabs.affinitydesigner Version: 1.8.6 (1.8.15) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Affinity Designer [48821] User ID: 501 Date/Time: 2021-01-30 17:27:51.954 +0700 OS Version: macOS 11.1 (20C69) Report Version: 12 Anonymous UUID: E41B67C7-3EA1-34E7-87DE-3401BAF84D96 Sleep/Wake UUID: 42FA1637-F610-4600-9E77-5039A9065722 Time Awake Since Boot: 140000 seconds Time Since Wake: 1200 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [48821] VM Regions Near 0x18: --> __TEXT 10a763000-10a7bf000 [ 368K] r-x/r-x SM=COW /Applications/Affinity Designer.app/Contents/MacOS/Affinity Designer bug-affinity designer.txt
  4. wow, 2019 and this issue still exist. how is the progress?
  5. Woah, it's August 2018, planned to bought this and encounter this bug as well. Lucky I got the trial one. Still no fixes?
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.