stokerg

That could certainly upset things, as that would change the path to the Linked file.

Hi @Jpburns, This isn't something I can replicate, so doesn't look like a bug that affects placing files from iCloud in general, otherwise, i'd be able to replicate it. I do know, that if you renamed a file that's linked on iCloud it would then show as Linked Remote BUT it would also show as missing. Same if you deleted the image from iCloud. This specific situation was raised with the Developers but closed as By Design with this comment 'Cloud resources are assumed to be remote unless we can prove they have been downloaded and transitioned to the local state.' This might be the issue @MikeTOwas referring to, but it doesn't apply here due to your Status showing as okay. If you select one of the Linked Remote images in the Resource Manager and click on Show In Finder, does it open Finder and display the correct image?

Hi @ChasS, What format are you exporting to? I'm finding if exporting to PDF, then it defaults to Whole Document but exporting to a PNG or JPG allows me to export the selected artboard and I've gone right back to the first version of 2.0 and it was the same then. Could you have been exporting to an image format before and now you are exporting to PDF? For the preview issue, can you attach one of your files? Mac is defaulting to the selected Artboard, so there is a difference. This will need logging as it doesn't appear it already is.

Hi @Brant Nalderand Welcome to the Forums, Please click View>Show Context Toolbar and that will bring those options back

Hallo @miss peppelsund Willkommen in den Foren, Woher platzierst du die Bilder? Apple-Fotos oder ein Cloud-Laufwerk wie iCloud oder aus dem iPads-Speicher? Eine Sache, die Sie versuchen können, ist, Affinity zu beenden und dann neu zu starten. Sobald Sie den Ladebildschirm sehen, tippen Sie zweimal auf den Bildschirm. Es wird ein übersichtlicher Benutzerdatenbildschirm angezeigt. Sie können einfach auf Zurücksetzen tippen. Affinität wird dann wie gewohnt geladen.Prüfen Sie nun, ob Sie mehrere Bilder platzieren können. Wenn Sie nicht können, könnten Sie eine Bildschirmaufnahme mit dem Problem anhängen und ich werde sehen, ob ich einen Grund dafür erkennen kann, dass die Aufnahme nicht mehr funktioniert.

Hi @garrettm30, Thanks for reporting this. I've just logged this with the Developers to resolve

Hi @evtonic3, Which model iPad are you using? Were you just using only brushes or were there Adjustment Layers also applied? I can't say I've had this happen on my iPad, but I've got access to a stack of iPads here in the office so i'm happy to see if I can replicate this.

HI @mmlacand Welcome to the Forums, I can't confirm when this will be added, as the feature is still being developed and we don't comment on when a New Feature will be introduced, for various reasons.

Hi @matthewphamand Welcome to the Forums, Where are you importing from and exporting to? If you can start Affinity and as soon as the loading screen appears, double tap the screen and you should get shown a Clear User Data screen. At this point, tap on reset and the Affinity will then start as normal. Now try exporting and importing again and let me know the results.

Thanks for reporting this @MikeTO, I've logged it with the Developers and i'll make sure the Affinity Info Bot tags that other thread

Hi @Ryw, Thats great the beta is working but it still doesn't explain why the main release build isn't. It would be interesting to see if you have the same issue with the EXE version of the release build of 2.4.2

@Ryw, if going for a reinstall, can you download the MSI/EXE version and not the MSIX one? To get the EXE version, go to this link: https://store.serif.com/update/windows/photo/2/ and click text under the main download button that says 'Also available: EXE (699.18MB)'

Hi @Austen Lennon Could you give me the full specs of your Mac and a screen recording of the issue? Did you install Affinity from the Mac App Store or direct from our Store?

@Ryw Thanks for the screenshot. Its very odd that your Renderer felid is blank. The couple of times i've seen that, if i remember correctly is when Affinity is being run on a Virtual Machine, which i take isn't the case here? Could you also attach your log.txt which can be found in this location: %userprofile%\.affinity\Designer\2.0 If you paste that path into the Windows run box and click okay, it should open that folder with the log.txt file in

Hi @Ryw, I'm just going to debug the crash report but while i wait for that, can you try disabling Hardware Acceleration (if enabled) under Edit>Settings>Performance and see if that stops the crashing?

Hi @revpub, It's a bit tricky to tell from just the recording, as i don't have a file setup in the same way as yourself but for placing the image, can you try instead of clicking in the text box you want the image in and then clicking Place Image, don't click in the text box and instead just click Place Image and then place the image on the page, size it and along the top toolbar, next to the Pin icon, is an Inline with text option, click that and it should place the image into the text box. For the Heading issue, the text will be SOMEWHERE in the document. Could you attach or upload your afpub file to our Dropbox here and i'll be able to have a poke and see where its going and what we need to do to correct it.

Hi @allyann, Can you try doing a basic reset of Affinity Publisher. To do this, start Affinity Publisher from Applications, while holding down the Control key and you should get shown a Clear User Data screen and 3 options will be ticked and you can just click on Clear. Affinity should then start as normal. Now start a New Document and let me know if there's been any improvement for you. @IllusionStudioDa Ihr Problem mit Affinity nach dem Öffnen eines Dokuments auftritt, hängt dies wahrscheinlich mit Ihrem Dokument zusammen und ist ein ganz anderes Problem @allyannbeschreibt. Probieren Sie das oben beschriebene Zurücksetzen aus und prüfen Sie, ob dadurch eine Verbesserung erzielt wird. Wenn dies nicht der Fall ist, starten Sie bitte einen neuen Thread. Wir können dann versuchen, die Datei von Ihnen zu erhalten.

Hi @PixelPoetix, Can you check and see if you have a crash report that you can attach? Also if you have a copy of the original file you were adding the pages from that you could attach, I can see if I can replicate the crash and it logged with the Developers

@antoThank you for uploading the file. I've replicated it here and will get this written up and logged with the Developers

Hi @anto, Can you attach the file you use in the recording or upload it to our Dropbox here and I'll get this logged with the Developers if it isn't already

Nope you are correct, delete the artboard and keep the objects and the export/preview is fine. Just ran this past QA and they have informed me it's actually AF-1318 so has already been logged. This is caused by the Gradient Overlay Layer Effect using non-100% stops. I'll get the report updated with a link back to this thread so the Affinity Info Bot can update here when it has been resolved

Hi @simonsanchezart, I wonder if you are running into another version of the bug reported in this thread which affects the Colour Dodge blend mode and that likely would account for the colour issue on the egg? I'll try and confirm if that's the case and make sure there isn't a separate issue here that needs logging. @NotMyFaultThanks for reporting the issue with the Preview, as that is a separate issue. The Tech Agent who has that ticket will reply shortly

Hi @Hangman, Thanks for bringing this up. I was pretty sure this rang a bell with me and I've just found the original bug report (AFB-5840) This was a bug logged in a very early version of Affinity V2 and was fixed. So looks like this is a regression, sadly the bug report doesn't say what the fix was, so I'll need to do a bit of digging here. Let me find out when this regressed and I'll get the issue reopened and also confirm the expected behavior

Hi @gregj, Did exporting to a folder not managed by OneDrive, allow you to export?

At first i couldn't replicate this, but I've found out why. I was creating my alias in the same folder as the images, so the files were named 'imagename.png alias' and this just worked. However, I then created the alias outside of the folder with the images in so they are missing the 'alias' part from the file name and then I can replicate the issue you show. If you can just confirm I've done this the same way as you have, I'll get this logged with the Developers