Leigh
-
Posts
3,222 -
Joined
Posts posted by Leigh
-
-
I have logged your document with our developers to see if they can figure out what's causing the issue. When I have an update, I will let you know.
-
-
Hi @Hilltop - Just wanted to let you know that I can replicate this on Windows using both 2.4.2 and the 2.5 beta. I'm just waiting to hear back from our QA team to see if they have any idea what this issue could be or if the document needs logging with our developers. Will get back to you as soon as possible.
-
-
On 4/11/2024 at 12:39 PM, Hilltop said:
It's three weeks after I submitted the requested Publisher and log files to Serif. It's the first time I sent in such files and as I haven't heard anything back yet, I was wondering: Is there a typical timeline for Serif staff to respond? I also noticed that Lee_T didn't respond to a PM and also that he hasn't been around for a couple of weeks.
Sorry about this - I will get someone to look into this ASAP and get back to you with an update.
-
On 4/1/2024 at 7:50 PM, Granddaddy said:
I'm disappointed that my simple question about the future of these Affinity forums has not been answered by any forum moderators, Affinity staff, or Canva/Serif principals who might actually know whether Affinity technical support will remain free under Canva ownership.
Thanks for your patience @Granddaddy you'll understand we've had a much higher volume of contacts to respond to since the announcement but to answer your question, things will remain the same i.e the forums and Technical Support will remain free.
-
On 3/31/2024 at 4:31 PM, rash said:
Thanks for your reply @Leigh. Of course I can send you whatever you need – although not to the public of the forum. I could offer the complete package including images, fonts and both mentioned PDFs. I will upload it to my own server and send you a link via PM to download it. If you prefer dropbox, that would be possible too.
Thank you for the PM and Link - will have a look and get back to you ASAP.
-
On 3/23/2024 at 3:07 PM, rash said:
Maybe it’s getting a bit boring, but I don’t consider the file sizes of exported PDFs as acceptable. What bores me is the apparent ignorance of an issue known at least since 2019 and broadly discussed in this forum quite a few times. Admittedly, I don’t know if the problem is always the same or if we’re talking about different problems leading to similar results – none of the discussions ended up in clarification by the Serif staff, as far as I remember their participations were limited to ask for an upload of suspicious files to get them checked. We’ve never heard what’s going on, so the discussions mostly stopped without getting solved substantially.
A real world example with Publisher 2.4.0 on Mac: Photo booklet, 40 pages, 210 x 297 mm, pages covered largely with pictures, an absolute minimum of accompanying text, two fonts in use. The photos are (linked) 8-bit RGB TIFs (no difference with JPGs), document color space is CMYK. The resulting PDF is around 170 MB with the settings in the left column (screenshot below) and 370 MB with those in the right column. Only difference is the image conversion (red circle) – the print shop prefers the images converted to CMYK, but has an upload size limit on the other hand.
Thanks for posting and sorry for the delayed response.
I think i've found the post you're referring to and you're right, there's no real outcome. So that I can look into this further and hopefully get some answers, can you send me an example Publisher document showing this on export? If you require a dropbox link, just let me know.
-
On 3/12/2024 at 9:25 AM, NicKraneis said:
Hi, sadly this doesnt change anything
That's disappointing to hear. If you haven't already, can you update to 2.4 and send me a Crash Report from this version? Is it also possible to send me your Log.txt from %APPDATA%\Affinity\Publisher\2.0\
-
-
Sorry to hear that you're having these issues when making changes. Can you check to see if you have OpenCL enabled in Edit > Settings > Performance. If you have, please disable it and try again.
-
Welcome to forum @Feystag - I don't have much experience with FontForge but I've just created a crude font with it and wasn't able to replicate the issue on macOS. After updating my font, exporting and importing in Font Book, it's still detected in my AFD document correctly and the characters remain.
If you could provide more details of the steps you're taking or some example files we can investigate this further for you.
-
@NotMyFault Just wanted to let you know that we've not forgotten about this post - we're trying to get some clarification on this issue for you. When we have an update, we'll let you know.
-
2 hours ago, rikkarlo2 said:
Thanks for your fast answer, I'm sorry if I sounded rude, but after three years from the first bug report on this we still don't have any clue about when it could be fixed or if it will be fixed at all, and I'm starting losing hopes :).
No need to apologise
-
A small number of users are running our x64 (64 bit) apps on Windows ARM with an ARM CPU. After updating to 2.4 they have noticed that documents fail to render when loaded into the app. This is a known issue and appears to be related to OpenCL being enabled in the 2.4 update.
Turning off OpenCL should resolve this issue for now. To do this, go to Edit > Settings > Performance and untick Enable OpenCL
This has been logged with our developers to be fixed. -
We've had several reports of RAW files having Artefacts or Green Lines after updating to 2.4 on Windows. This is a known issue and appears to be related to OpenCL.
Turning off OpenCL should resolve this issue for now. To do this, go to Edit > Settings > Performance and untick Enable OpenCL
This has been logged with our developers to be fixed.- JSP75, Paul Creedy and Mik Laver
-
3
-
On 2/27/2024 at 11:01 AM, Demys said:
Hello,
Yes it's still happening regulary, still can't pinpoint why, always same setup, some file works, some don't
As i'm using linked file only with exr render i can't say about other type of images, but i saw some people here with almost the same problems, i guess it comes from a bug in the loading phase of the linked file but finding where is the hard part...
Regards
Thanks for the update @Demys - Is it possible to install the 2.4 update and see if the issue sill persists?
-
22 hours ago, rikkarlo2 said:
2.4 still not fixed.... I'd really like to know how the dev team/management decides priorities... They already have the correct code to make it work since the same tool works in the develop persona for raw files... it's just a matter of copy pasting the same code into the photo persona and in the develop persona for non-raw files... I can't understand a single reason why every new feature they included in the 2.4 is more important than the bugged white balance tool... who cares about sorting stuff XD if I can't make my photos look good.
I completely understand your frustration @rikkarlo2 I have bumped this logged issue with our developers.
-
11 minutes ago, YentheJoline said:
Yes I have this issue too! Are there any fixes available yet?
Not yet, sorry. I've bumped the bug report with our developers.
-
15 hours ago, dlampel said:
I am not ungrateful for the work done on this situation by the Affinity crew, but, honestly, this is getting to be truly frustrating for me. Today I began working on a monthly newsletter, based on a tried and true template of my own creation. Did this, did that, imported/copied text, moved frames about, inserted graphics, etc. All handled perfectly--until I accidently right-clicked in a text frame.
Crash. Disappear.
C'mon guys, this is basic!
I understand you're frustration and if we knew what was causing your issue, we would provide a fix but unfortunately, your issues appear to be isolated to your setup or workflow. All of the advice we have given so far would normally get us to a point where we can replicate or find the cause of the issue but that's not the case for you, sorry.
We will continue to investigate but without us being able to replicate the issue or get any meaningful information from your crash reports, it's proving tricky.
Did you manage to try the advice from @debraspicher posted above? If so, what was the outcome? Can you provide a copy of your latest logs from EventViewer (steps on how to do that can be found here) and will get a developer to have another look to see if anything springs to mind.
-
I've removed the files from your post but i've made them available to our support team.
-
Thanks for your patience. I've had a look at your Log.txt and it looks like the drivers for your GTX 1650 SUPER are 31.0.15.3619 but the latest version is 31.0.15.4609. It also looks like your UHD Graphics 630 drivers are 27.20.100.9664 but the latest version is 31.0.101.2125. Is it possible to try and update to latest version for both to see if that improves things?
Also, have you been able to try the 2.4 beta to see if that provides better stability?
-
On 1/14/2024 at 10:22 PM, mangoes said:
I'm having the same issue. I created a number of files within the past two weeks and now half won't open.
I'm on a Mac and I recently (in the last 4 days) upgraded to the latest OS. But it doesn't explain why half the files do open even if they were created prior to my OS update.
It does seem random. Some of the larger files open, no problem. The ones I tried but can't seem to open are about 10MB. Help??
Update: Holy cow. I just left it running and it finally opened after 30 min. WTH?? Is this normal? I'm new to Affinity and this is making me regret the decision to jump to Affinity from Adobe.
Can you try the steps mentioned in this post to see if that improves your situation?
-
Just wanted to post a quick update on this. Our developers have confirmed that it's a bug and will be fixed in an upcoming update.
Thanks for letting us know.
- Dan C and KarlLegion
-
2
AF-Photo 2.2 Loading linked file from network drive
in V2 Bugs found on Windows
Posted
I've not forgotten about your issue @Demys. I've been trying to replicate it, on and off, with my Synology using 2.4 & 2.4.2 and different files, but still struggling to replicate.
I can see that Nathan logged a similar issue in this thread that could be related and when fixed, may resolve your issue too.
Would it be possible to provide a screen recording of the process you're going through and the issue occurring? Might help us replicate - feel free to DM me with a link to a recording if you're not wanting to share it publicly. I can also provide a Dropbox link if needed to upload the files to.