-
Posts
3,381 -
Joined
Posts posted by NathanC
-
-
Welcome to the forums @cerjio,
Could you provide us with a copy of the .afdesign file before export so we can investigate further? I've provided a private upload link below in case you don't want to share it publicly.
https://www.dropbox.com/request/nIWKdeyoAlWh5VoWRF79
Many thanks
-
Hi @PafCaf,
The affinity apps are user-mode applications and are therefore not capable of causing a system freeze/crash or BSOD (Blue Screen Of Death). The Affinity apps may have been the trigger for the crash likely due to the high Memory and/or CPU usage and also that the apps utilise kernel-mode drivers, but the apps themselves won't be the cause. This will be an underlying system issue (E.G Driver issues, Windows Corruption, or Hardware issues such as unstable RAM/CPU Overclock) System Event Viewer may reveal more but it can vary dependant on the cause.
-
Welcome to the forums @Wusuraambya,
I've debugged your crash report, which indicates 'pdfcore.dll' as the fault, which appears to be a component of PDFsam Enhanced 7 app 'hooking' into the Publisher and likely triggering the crash. I'd suggest terminating this app and then try opening the same .PDF in publisher again.
-
Hi @Viktor CR,
Any chance you could provide a sample file where you've encountered this issue? It doesn't need to be the whole document, just the original + flipped layer symbol. 🙂
Many thanks
-
Can confirm I can replicate the 'Find in document' issue with the language set to French I've logged this issue with the developers. 👍
-
Hi @hunter_sk,
I've replicated and logged this issue with the developers, thanks for the detailed report.
-
Welcome to the forums @Micasael,
On 10/28/2024 at 9:44 PM, Micasael said:I've probably found the problem: there is an embedded document (a logo) on the master pager. Always when I try to change that, affinity crashes. So i decided to set up the document again. Probably you have an idea, what the problem could be…?
If you could provide us with a copy of the .afpub file where you're encountering this crash we can look into it further and confirm if it's replicable on our side. I can provide a private upload link if required.
-
Hi @KLE-France,
I've logged this with the developers, thanks for your report.
-
4 minutes ago, RobWu said:
Have you tried any 2.5.x version, to see if the problem also exist on your end? So it's not just me?
Yeah it's not just you, it's an issue that's logged internally with the Type-1 fonts failing to list in-app. When 2.6 is officially released this fix should also get included. 👍
-
Hi @4dimage,
On 10/31/2024 at 3:54 PM, 4dimage said:Long story short: there is a difference between the destructive Perspective filter (pixel level) and the non-destructive Live Perspective filter. The latter produces unpredictable results both during use and in further processing of the document.
Just catching up with this one, but I'm observing this same poor-quality render using the live perspective filter on the full-res placed image compared to the better destructive filter output using your sample files, I'll log this with the developers for further investigation and confirmation.
-
Many thanks. I'm now observing the same issue with your document, modifying the text at the bottom of 62 such as removing the full stop from '1985.' also appears to clear the phantom text at the bottom of 61, this is certainly a bug so I've now logged this with the developers for further investigation and resolution.
-
Hi @RobWu,
I'd recommend downloading the latest 2.6 beta and checking the font list, I've installed a few type 1 decorative fonts via FontExpert 2025 and they're all present in Pub 2.6.
-
Hi @Bojan-MDN,
Thanks for uploading the files, I've installed the necessary fonts but the text on page 61 appears to be in a completely different place than what's shown in your screenshots, the last point on page 61 is .196 and the year shown is 1984. I have all the fonts installed (other than 'Times' and 'Times Regular'), but I don't have your spelling/hyphenation dictionaries so i'm wondering if this may be why, could you possibly provide me with these?
-
Hi @Bojan-MDN,
Feel free to upload the problematic file to the private upload link below and we can investigate further.
https://www.dropbox.com/request/KQ8a7u743v0qIZjYR0fl
Let me know once it's uploaded. 🙂
-
Welcome to the forums @himopi,
I've logged this with the translation team, thanks for your report.
-
-
Hi @garrettm30,
I've logged this with the developers. 🙂
-
16 hours ago, sbk said:
If I understand your last comment. It sounds as if any Color FITS images that are processed via the Batch operation will not be properly converted to a color TIF or JPG, or ...?
If this is the case then the current Batch operation would not be of any help for processing FITS images. Is this correct?
Yes, that's correct. It's logged with the developers to add the 'Develop FITS' step as a part of a Batch Job.
-
Thanks, I'm just getting DirectX errors as the faulting component so it is certainly GPU/Driver related if you've already got the Studio Driver installed it may be worth switching it around to game-ready, I'd suggest checking 'Perform a clean installation' as well.
-
Welcome to the forums @Rudy70,
To be clear, are you referring to the Affinity app language or the keyboard input language? We don't support Polish as an app language.
-
Many thanks, I'll get this logged with your answers provided. As some general guidance, we do recommend saving to a local drive and moving to external storage after, as doing so often significantly reduces the chances of encountering a file corruption.
I have been able to successfully recover your file, I've PM'd you a download link.
-
Hi @garrettm30,
This offset creep does appear to be unexpected behaviour, so i'll get this logged with the developers.
-
Welcome to the forums @Mark Osborne-Burns,
This isn't an issue I can replicate so far, pasting into metadata fields includes the entire string. Have you tried pasting into a different app such as Notepad first to check that it's not an issue with the copy source?
If the issue is limited to just affinity it would be beneifical if you could provide a screen recording demonstrating the problem.
-
Hi @bobbybosler,
This is indeed a bug and one that I can replicate, however it appears to have been fixed in the current 2.6 beta.
Refine Selection preview issue
in Affinity on Desktop Questions (macOS and Windows)
Posted
Welcome to the forums @mark9
I can confirm this is a known issue with quick mask + refinement currently logged with the developers, I've bumped the existing issue with your report.