Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Andreas Scherer

  • Posts

  • Joined

  • Last visited

Profile Information

  • Location
    Munich, Bavaria, Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Side note: The Affinity Help page for Layer Blending claims that Divide is one of the most commonly used modes. Either that's not quite so and nobody stumbled on the misbehaviour, or users are content with the false results. (Or my multi-layered and multi-fx'ed approach was too much for the poor program.)
  2. @HangmanCool. I'll stick with the V1 bug, because it's unlikely that the project will ever be updated to V2. Case closed.
  3. Affinity 2.0.4 MacOS 12.6.3 Monterey The canonical way to Import Content does not work for affont files, e.g., the Publication Typefaces from the Creative Collection. See multiple threads and in the support forum. A workaround is to drag and drop the affont files from Finder to the main Affinity windows (all three apps on MacOS). Note that Import Content does work for afbrushes and afassets files, e.g. Spray Paint Brushes and Textures by MiksKS.
  4. There's at least one more report from a Mac user; @walt.farrellI think you are running the Windows version.
  5. @walt.farrell The problem (at least for me) is less that the fonts have to be activated in each of the three programs separately, but that the canonical method of using “File / Import content...” as described by @Patrick Connordoesn't work at this time. (I could, of course, open a genuine bug report, but after dragging all *.affont files into the three app windows all is fine, and I don't want to “uninstall” the fonts in order to reproduce the “bug”.)
  6. Here is the nested group of “Pearls” that actually reproduces the malign effect. Perlen.afdesign
  7. For my configuration (German version of Affinity 2.0.4 on MacOS 12.6.3 Monterey) this did not work, i.e., the fonts were not displayed in the avaiable fonts list. However, dragging the *.affont files from Finder into the main app window works fine.
  8. I'm working on a complex design in AD V1 with lots of effects on levels and groups; see first screenshot (with rulers on top). When I open this project in AD V2, several effects have no effect; see second screenshot.
  9. At least in the German version of all three apps (2.0.4 on Monterey 12.6.3) “Datei / Inhalt importieren...” does not bring the fonts into the available fonts list. Dragging the *.affont files into the main app window works fine, though.
  10. I'm using the base model (8GB RAM, 256GB SSD) of the Mac Mini M1 (both at home and at work) and it is definitively comfortable to use with the Affinity suite, so I'd be confident that the Mac Mini M2 would be a great tool as well (and allegedly, it's even cheaper than the M1 machine).
  11. macOS Monterey version 12.6.2 Affinity General License version 2.0.3 This seems to affect all three apps, but I miss it most for APub: Right-clicking on either of the three app icons in the dock bar doesn't show any ”Recently used objects“, although inside the programs (ATTOW, AD and APub), there are such objects to choose from in the ”Recently used files“ tab of the project start panel. I reallly miss this functionality when working with two or three documents and want to open one with a simple mouse click.
  12. I'll keep both versions installed on my private Mac Mini. ATTOW, I have not started a new project with any of the V2 apps. All existing projects will remain in V1 format, as long as I want to exchange them with others who have/can not upgrade/d to Affinity V2.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.