Leigh
-
Posts
3,231 -
Joined
Posts posted by Leigh
-
-
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.
- KarlLegion and Dan C
-
2
-
On 12/18/2023 at 1:30 PM, dlampel said:
Thank you for your response, Leigh.
I can understand the inability to replicate this problem, for it is certainly not consistent. But, to answer your question, yes, it still occurs from time to time even in 2.3 (Note: I am now back to running the Affinity EXE programs, instead of the apps. They seem more stable for me.). Attached is the Log.txt file you requested. I use a wired mouse (Logitech) without any third-party drivers or software--just your basic mouse. And this errant behavior never occurs in any other programs.
Although it may not be pertinent to this bug, I am still (once in a while) experiencing the same inexplicable crash mentioned in my original post, which seems to occur more often than not when opening a second file. The program freezes for about 10-15 seconds, then disappears.
Thanks for log file and the additional information.
Sorry to be a pain but would it be possible to delete the Log.txt that's currently in %AppData%\Affinity\Publisher\2.0\ and then launch the app again to generate a new one. Once you've done this can you send this again to me and also include a screenshot of the devices listed in Edit > Settings > Performance > Renderer?
-
Just wanted to let you know that i've been able to replicate what you're seeing. I'm going to ask our developers for clarification on how it should work - when I have an update I will let you know. Please be aware that we're heading into our annual Christmas closure so I might not be able to provide an update until the New Year.
Out of curiosity, what happens if go to Rasterization and enable Rasterize Entire Page within the Print settings before printing? I'm finding the issue is related to how vector objects and raster objects are being handled. -
On 10/30/2023 at 5:06 PM, nick l said:
Thanks very much for responding. I understand that this may not be a priority. It sounds like people have had a variety of problems with printing. I would love to have a clearer picture of the process involved in going from my RGB document to the inks of my CMYK printer. But there are so many issues.... My hope with this report is that it at least gives an illustration of what appears to be a concrete problem (or two....) Meanwhile, until further notice, I'm just setting color handling to "performed by app".
We're still looking into this but it looks like Red River Paper advise to use "Performed by App" with their Printer Profiles: https://www.redrivercatalog.com/profiles/how-to-use-inkjet-printer-profiles-affinity-photo-windows.html
Still doesn't explain why the gradients in the original post are changing colour - will get back to you on that.
-
We're sorry for the delay in replying @dlampel - we've been trying replicate your right click crash but without success.
Are you still getting the crash after updating 2.3? Would it be possible to send me copy of our Log.txt from %AppData%\Affinity\Publisher\2.0\
Are you using a wired or wireless mouse? Do you have any third party drivers/software installed for the mouse? Not sure if related but worth asking at this point.
-
FYI: Have split this discussion from the following thread in Resources:
- walt.farrell, v_kyr and loukash
-
3
-
On 12/16/2023 at 8:22 PM, markimark said:
I submitted a report requesting this get sent to affinity dev team for bug review.
I can see that you reported the post. We'll get it logged.
-
4 hours ago, Klaang said:
I have Affinity V2.3 installed on Mac OS 13.6.2. I want to deactivate Affinity and move the activation / license to a different user. At the Account window "This application is licensed to:", select the 3 bars - "Deactivate This Device ...", get the warning "Deactivating this device will remove all your license date and require a license activation the next time any Affinity application starts. Do you want to continue?", select "Yes" and the dialog box goes away, but nothing appears to have happened. Affinity still appears to be active. So I close the Affinity program (Publisher, Designer or Photo) and start Affinity program again just to see if it deactivated, but it still appears to be active ... there is no request to activate the program I (thought) I just deactivated. Is the software active, or not? How can I tell? Help 🙂 Trying to do the right thing and not loose an activation ( I have purchased 4 licenses).
FYI: I've replied to you outside of the forum
-
16 hours ago, MatthiasNRW said:
Hello,
same problem here. I want to purchase several licenses for my design-class (All 3 Apps for 9 iPad Pros = 27 licences). Our Mobile Device Management (MDM) doesn't allow In-App-Purchases. Even there are no restrictions in configuration (already spoke to our it-admin).
Is there an alternate way to buy and activate iPad Licenses?
Thx in advance.
Morning and welcome to our forum.
Please contact our Education Sales Team - they can provide a Managed AppConfig for use with our iPad apps when deployed via your MDM.
https://affinity.serif.com/education/contact/ -
@Demys Just wanted let you know that we've logged the EXR thumbnail preview issue with our developers to be fixed. Are you still getting the blurring issue for linked images? Is it just EXR files or most images?
-
-
We're aware of an issue in V2.2 and above that will cause text, using a PostScript (Type 1) font, to be converted to curves when exported to PDF.
This is currently logged with our developers but a workaround would be to use a similar or alternative non-PostScript (Type 1) font for the affected text elements.We're sorry for any inconvenience this might cause.
-
3 hours ago, Hangman said:
Hi @Leigh,
Maybe a blue 'tip' should be added to the appropriate section of the Help file to point this out, then at least it's acknowledged for those experiencing the same issue...
I've logged this with the developers to see if there's anything that can be done. I will make an FAQ in the meantime but if we can't improve the workflow then I will see if we can update the help. Thanks again @Hangman
-
Just wanted to let you know that I've logged this with our developers to see if there's anything we can do to improve this situation.
-
That's good to hear. I've been sat on a plane where the Captain announced he was turning it off and back on to fix an issue. Didn't Crash, true story
Hoping it continues to work 🤞
-
Thanks for sending the log.txt. Sorry for the delay in replying, it's been really busy with Black Friday 😰
I've not really spoken to any other users using KVM/QEMU but I know the apps work in virtualised environments. The "Please Try Again" message can happen if there's an issue with the app accessing the %APPDATA%\Affinity\Common\2.0 folder or the .dat files inside it. Can you try renaming this folder and try again?
The issues you're having could also be down to how the VM is setup to access the network from within KVM/QEMU. Do you know how it's setup? -
[KNOWN ISSUE] RAW files have Artefacts or Green Lines after updating to 2.4 on Windows
in Frequently Asked Questions about V2 software
Posted
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.