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

Search the Community

Showing results for tags 'v2.3'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.5 Beta New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 4 results

  1. I have a photo I applied an adjustment to and I want to apply the same adjustment layer to other photos. I found I can copy my adjustment layer and paste it as a child layer onto other photos. That does the job (but is sometimes tedious as to copy it I have to find back where this particular setting is used). But I see there is also a button "Add preset": I suppose it's there to help us reusing the same adjustment? Problem is that once I have given a name to my adjustment preset, I have not found, neither by exploring the UI neither in the help, how I can reapply it? I give it a new name and then… What do I do if I want to reuse this preset (in the same document or in another)? Sorry if it's obvious but I don't find it by myself…
  2. Hi support, it looks like I found a - now more or less reproducible - issue with the index in Affinity Publisher V2.3.0. With three (bigger) documents I created, I very often get a crash to desktop (no alert or anything) just after loading them (normally about the time the auto-correction has just finished underlining wrong words). I'm using the German UI (but I have had the same crash when using the English version, too, so I guess this is not really relevant). All three documents have in common that they have an index. I've created a new document with some filler text to try it out, and it crashed Publisher basically every time I load it. I have attached it to this post. I can often prevent the crash with my bigger documents if I'm fast enough to click the "Update index" button (in "Index" studio) before it has finished rendering after loading (even though it doesn't work reliably with the below test document), which seems to point at some issues with the index itself. This bug is really annoying, especially when you are just loading a second document to check something in there, only for Publisher to crash, and as such losing your work since the last save from the document you were working with at that time you loaded the second document! Can you please have a look and get this fixed (I have this problem basically since V2.1 already, but couldn't easily reproduce or pinpoint it. I think it worked with V2.0 without issues, if I remember it correctly). My system: Windows 10 Home, 22H2, build 19045.3803 Hardware acceleration setting doesn't change anything, it crashes with enabled and disabled. 16 GB RAM, SSD Harddisks AMD Ryzen 5 2600 Six-Core Processor 3.40 GHz NVidia GeForce RTX 2060 (6 GB) I have a small Adesso tablet connected, but don't use it for Publisher I have an Elgato Stream Deck (15 key version) connected as well, but again don't use it for Publisher Index-Issue_Example.afpub
  3. 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.
  4. Now what happened to my doc ? All is gone wild !! Have you seen this before ? Thanks for your ideas…
×
×
  • 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.