Sukavi
Members-
Posts
59 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
ugh. well at least you are able to get it done. sorry for your troubles.
-
Sukavi reacted to a post in a topic: Publisher Crashing on Export
-
That's not fun. sorry to hear about your troubles. I don't think considering the power of my Mac Studio that it should take so long to do some things. especially the resource manager is always throwing up beachballs. Maybe there is some problem with memory as you say. I hope you can get this figured out.
-
AlainP reacted to a post in a topic: Problems with Affinity 2.5.5 and MacOS Sequoia Beta
-
Juhani reacted to a post in a topic: Problems with Affinity 2.5.5 and MacOS Sequoia Beta
-
whatimissthemost reacted to a post in a topic: Problems with Affinity 2.5.5 and MacOS Sequoia Beta
-
Problems with Affinity 2.5.5 and MacOS Sequoia Beta
Sukavi replied to dcarvalho84's topic in V2 Bugs found on macOS
Thank you @Trustedsource It's been a really difficult year and I am tired of people mistreating others. The problems are certainly more than annoying, they affect our ability to make money and do our jobs. However, blaming people for things like upgrading doesn't help the situation and just dumps fuel on a fire. Frankly it also taints my feelings of feeling comfortable adopting this software suite for my work. http://gudkarma.org/ I am doing it all on Affinity software, and while I want to be critical the finger pointing and victim blaming mentality is really discouraging and tiring. -
Sukavi reacted to a post in a topic: Problems with Affinity 2.5.5 and MacOS Sequoia Beta
-
norbinw reacted to a post in a topic: Problems with Affinity 2.5.5 and MacOS Sequoia Beta
-
Problems with Affinity 2.5.5 and MacOS Sequoia Beta
Sukavi replied to dcarvalho84's topic in V2 Bugs found on macOS
It is not helpful to blame people for upgrading. There are various reasons some of us updated to a new OS version. Some times people with disabilities have to update in order to use some features etc. So, to bash people that upgraded is a bit ignorant. What I think the issue is, Serif did not take steps to even let customers know there are known issues. They certainly have my email address, and everyone else registered here on the forum. I do not think its a stretch to say they could send out or post a notice that it would not be great idea to upgrade as there are known issues that could impact workflow negatively. I run a business where I serve customers food I make. Certainly they have the right to complain to me if I serve cold food that should be hot. I also inform every customer that the food is extremely hot so please be careful. I could tell a customer its their fault if they burnt their mouths, as what fool would quickly take a bite of something coming out of an oven right away..but they are not privy to how hot the oven is or how soon it was served. Ultimately I have the lions share of responsibility. Serif certainly has a responsibility to their customers. It is at the least ignorant and mean spirited for someone to blame us, the paying customers, for upgrading. I had not seen any notices and assumed there would not be big issues. To the posters blaming Apple shifting from Serif... Yeah, sorry that doesnt work well because Betas are available and Serif at the very least should have known the issues. They were reported by users as well. So I think its appropriate for customers to be upset. I am not interested in getting on any hate train. I am quite frustrated though, and I had to take two days to roll back to Sonoma and iron out the small issues. I am hoping the company continues strong as earlier this year I bought into their suite coming from Adobe. Being with Adobe since mid 90s. I am rooting for Serif and hoping this is just a blemish and fumble and not an indication of a rough road ahead. -
I guess if it happens again i will try that but as a one off crash that is not possible obivously.
-
youre welcome. as i spent a whole day with this b.s. problem and going through a 40 page publisher file trying to figure out what the problem is. to solely thank him, and leave out me and not even say sorry to a customer is pretty crappy. pile on top of that I had to roll back from sequoia OS due to problems with thumbnails just to get work done. Not a real feel good moment as a customer here. Who stupidly bought each app separately so i paid almost 300 dollars for all three apps. meh.
-
Sukavi reacted to a post in a topic: Publisher Crashing on Export
-
Sukavi reacted to a post in a topic: Publisher Crashing on Export
-
Sorry Walt. I couldn't take a screenshot at time of crash. for obvious reasons. I am not now sure which exact file that was. since this is work it is a bit difficult to throw up the files. I just wanted to add this issue to whomever attention that it needs, so I included the crash file.
-
Sukavi started following Designer crash when dragging group
-
I duplicated a group in designer by holding down Option key and dragging..while doing that it crashed. Mac OS 14.7 Mac Studio Affinity Designer 2 Affinity Store-2024-10-16-091218.ips
-
Hangman reacted to a post in a topic: Publisher Crashing on Export
-
Sukavi reacted to a post in a topic: Publisher Crashing on Export
-
Ah so its the pressure curve. Took me a few hours this morning to figure out which file was wrong. Thanks for the hard work! At least now i know what to check if it happens again with this file. Still not sure why other curves didnt create the issue as its being used in other files.
-
Created a new Designer file. Copy and pasted the layers from the offending Designer file into the new one. In Publisher I re-linked that new Designer file. Exported to PDF and crashed. So there is something in this designer file causing an issue. ugh. A lot of these graphics are being reused in the Designer files so I am confused. Designer is having no issue opening them. Tried exporting from Designer to PDF and bam...a crash. so something in this file is preventing export to pdf. Attaching crash report. Affinity Designer 2 Affinity Store-2024-10-15-101047.ips
-
Exporting try on spread whole document keeping that designer file unlinked on page 30. and it worked. seems like that one designer file is an issue which is interesting because I was duplicating designer files.
-
went to the spread for pages 30-31 Went into export pdf. Selected "current spread...bam. Publisher crashed.😮💨 Spread 28-29 and 30-31 are similar. Unlinked the Designer file linked and instead linked a random png file. tried exporting that spread and it worked. my guess is something in the designer file is causing an issue. Affinity Publisher 2 Affinity Store-2024-10-15-095316.ips
-
Exporting to PDF (full print) Pages 1-7. Exported without issue. 2nd attempt with pages 1-13..also exported without issue. Pages 1-13 are mostly text pages. 14 and onwards contain picture frames with linked design files. 3rd attempt with pages 1-15..also exported without issue. 4th attempt with pages 1-19.. no problem. ----- 5th attempt exporting with same settings except unchecked Layers...and..no problems. pleasantly surprised. I am guessing its something with the later pages. 6th attempt with same settings as 5th, pages 1-29. no problems. 7th attempt with same settings...pages 1-30...bam. crash. Affinity Publisher 2 Affinity Store-2024-10-15-093928.ips
-
uploaded and sent a DM
-
its 11gb. uploading now but sorry its almost midnight and I am getting sleepy so I might have to send a link in the morning. thank you for trying to help. attaching here some of the crash reports. Affinity Publisher 2 Affinity Store-2024-10-14-231810.ips Affinity Publisher 2 Affinity Store-2024-10-14-224606.ips