Jump to content
You must now use your email address to sign in [click for more info] ×

stokerg

Staff
  • Posts

    5,920
  • Joined

Posts posted by stokerg

  1. 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?

     

     

  2. 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?

    12 hours ago, walt.farrell said:

    (I have not had a chance to check macOS, yet.)

    Mac is defaulting to the selected Artboard, so there is a difference.  This will need logging as it doesn't appear it already is.

  3. 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.

  4. 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.

  5. @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 :) 

  6. 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.

  7. 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.

  8. 42 minutes ago, Hangman said:

    If you copy and paste the artwork onto a Canvas there is no longer an issue with either the export preview or the exported file so I'm not sure this is related to the Colour Dodge Blend Mode since that is present with both Artboard and Canvas though I could be completely wrong... :)

    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 :) 

     

  9. 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 :) 

  10. 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  :) 

  11. On 4/11/2024 at 6:14 PM, Timtoon said:

    Were that the case, I wouldn't have filed the bug. The original images are not broken; they're the same ones I was using before. The aliases aren't broken because the originals they point to are still there.

    Try this and see what you get:

    1. Create Publisher doc1.afpub and a directory of images at `images1/`
    2. Duplicate doc1.afpub to doc2.afpub
    3. Duplicate the `images1/` directory and its contents for doc2.afpub and name it `images2/`
    4. Open doc2.afpub and in the Resource Manager, update the image directory to `images2/`. It should all still work.
    5. In the Finder, delete the contents of `images2/` and replace them with an alias to each file in `images1/`. These are aliases to the fundamentally identical image.
    6. Open doc2.afpub and Update the Modified images
    7. Error "Failed to open file"

    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 :) 

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.