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

Sukavi

Members
  • Posts

    28
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well at least it can kind of be avoided. I assume it has nothing to do with my memory size? I guess you are testing it on your 16gb Macbook Pro.
  2. ok. so...its the Layer groups. I wonder why that wasnt happening before? Is there something to turn off that prevents that auto filling? I noticed that behavior when i started using the App. It is handy, but sometimes it is annoying that selecting a swatch will change the stroke or fill. I was working with a much larger file and experienced no problems before. Maybe its just a coincidence. I didn't think those groups were complex. I appreciate you sticking with this problem and helping me figure out what is going on.
  3. i am using os 14.4.1 i am waiting for someone to reach out to me. this is puzzling.
  4. I am seeing this error in the console. error 18:36:19.182913+0900 Affinity Designer 2 Affinity Store Unable to open mach-O at path: <private> Error:2 fault 18:36:19.196300+0900 Affinity Designer 2 Affinity Store FAULT: <private> determined it was necessary to configure <private> to support remote view vibrancy error 18:36:19.575011+0900 mdworker_shared All kCFPreferencesCurrentUser domains in this process will be volatile, because homeDirPath starts with /var/empty
  5. my hackintosh (with 24 gigs of memory and 8gig for GPU) is currently running mojave because i am using photoshop cs6. I cant use affinity apps on Mojave apparently. so i have been using my M2 Macbook air.it only has 8gigs of memory. i worked on larger files without any issues all week. I know I keep harping on it, but as soon as I updated, I had the issue.
  6. Interesting. It seems that if the first thing I do is select a swatch it hangs. but if i fiddle with other thihngs in the app first it and THEN tough the swatches its ok. very bizzare. Screen Recording 2024-04-10 at 18.15.31.mov
  7. So i turned off the HArdware acceleration..and same issue. I also deactivated a font I installed the other day. But not sure why that would be an issue as I used that font and things have been working. The only thing that changed was I clicked that damn update button. Here is a screen shot of my settings (before I turned off Hardware accel) Also, yes they arent crashing, they are hanging for infinity (well for an abnormally long time)
  8. ok. so i though i would open up a Designer file. and that went tits up too. hmmm. This is a big problem now. I need to get work done and suddenly things are broken. I dont know what that update did but after that everything started having issues. How exactly can i figure this out? is there a way to do a clean install of the app? i dont want to but..what are the options?
  9. Well, thank you for the check. I've been working with that file for a couple of months. In the last couple of weeks, haven't changed any fonts, etc. Hmmm. i will see what happens with font changes. The issue happens regardless of what layer I am on.
  10. I am still having this problem. I cant get any of my work done now.
  11. I rolled back to yesterdays version of the file and it seems to work. i feel like having that open while updating did something. its strange. I can provide the file privately for someone to check, yes. I dont have or use Dropbox. If i can upload without an account. I can also provide a link to download it. Please let me know.
  12. So I opened the same file and kept having the same issue any time i chose a color swatch in Affinity Photo v2. I then rolled back to using version 2.4.1 of Affinity Photo. I am still having that issue. This wasnt happening all day while using the app. After I updated to 2.4.2 i got that lock up when choosing a swatch. Now I see its just on this one file. Is it because that was opened in 2.4.1 and then I updated the app, and opened it again in 2.4.2? I am confused why this file seems to be currupted now.
  13. Did a restart of the computer. Had the same problem. I guess I will use Time Machine to roll back to the previous version so I can keep working until this issue is fixed.
×
×
  • 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.