NathanC

It sounds like you may be running into this known bug that's currently logged with the developers, the FAQ also contains a workaround in the event this bug is encountered when changing active displays.

Welcome to the forums @will_barbo, How are you applying the perspective function to the art text object? If you're in Photo 2 and use the Perspective tool, this automatically rasterises the art text as it's a destructive Pixel filter. If you opt to use the non-destructive Perspective Live filter, this won't immediately rasterise your art text layer as it's a live filter, but if you export out to a vector format such as PDF or SVG, it will automatically rasterise the text on export since it has a filter applied, you can check this by re-importing the PDF file back in to the app or using a PDF viewer to inspect the object, it will be a raster image type layer. If you wanted to apply a perspective warp to art text you would need to use the Warp Group > Perspective function available in Designer 2, on export this will convert the art text to curves, losing text editability but will preserve it's vector properties. Vector warp info: https://affinity.help/designer2/English.lproj/pages/ObjectControl/warp.html

Thanks for sending those over, I'm getting a pretty generic error from two and the other two of the reports fail to debug, however the scenarios that you have described when the app runs into a crash do point towards a GPU driver/rendering issue. As you've already ensured that your drivers are up to date and Hardware Acceleration is disabled within the app, could you try doing a clean install of your drivers by using a tool such as DDU (linked below) to wipe your existing GPU drivers, reboot and then re-install the latest available, before rebooting and trying a stitch again in Photo 2? https://www.guru3d.com/download/display-driver-uninstaller-download/

Hi @zgwangbo, I've since tested this on a M1 Macbook Air running Ventura 13.5.1 and using the trackpad the dialog always prompts as expected in 2.3, if possible could you try using a mouse for comparison just to confirm it's nothing odd to do with the trackpad/trackpad settings? Failing that, could you try resetting your Snapping presets in one of the apps by doing the following: Close all affinity apps Hold down CTRL and launch the app while still holding CTRL A 'Clear user data' menu will appear, in addition to the already ticked boxes tick 'Reset snapping presets' Press 'Clear' and the app will now launch, try opening the snapping menu again If both of the above don't work I can only think it's a problem specific to Catalina, so I'll see if I can get this tested on a Mac running Catalina.

Willkommen im Forum @Jürgen Kemmerer Beziehen Sie sich auf die Option "Nach Name sortieren" im Kontextmenü der Asset-Unterkategorie? Wenn ja, funktioniert sie bei mir wie erwartet. Ich habe eine neue Anlagenunterkategorie erstellt und 4 Objekte zur Anlagenkategorie hinzugefügt. Dann habe ich diese Assets umbenannt: '1', 'A', 'B', 'C' und sie dann per Drag & Drop verschoben, um ihre Position zu ändern. Mit der Funktion 'Nach Namen sortieren' im Kontextmenü habe ich sie dann wieder in die numerische und alphabetische Reihenfolge gebracht. Wenn dies bei Ihnen nicht funktioniert, könnten Sie mir eine exportierte .afassets-Datei zur Verfügung stellen, in der dieses Problem auftritt, sowie eine Bildschirmaufnahme? Bildschirmaufnahme FAQ: Herzlichen Dank!

Welcome to the forums @RH49, Could you provide us with a few recent crash reports from Photo 2? The FAQ below details how to find these. Many thanks

Welcome to the forums @Buglagur, There's a known bug with the Canvas rotation past 90° or lower than -90° causes the grid to disappear/fail to redraw, I can see in your screen recording that your canvas has been rotated at some stage so it's possible that you're encountering this bug. If you were to reset your rotation to 0° in the Navigator panel (Double tap the value) and then zoom into the canvas to force a redraw, does the grid then re-appear?

Hi @zgwangbo, I've also tested this in both 2.2.1 and 2.3 and I was able to access the snapping preset context menu without any issues, I also didn't have have any presets prior to updating, this was on an M1 running Sonoma 14.1.1. What MacOS version are you using, and not that it should matter but are you using a standard mouse or a MacBook trackpad?

Your embedded link is just re-directing me back to this post, was this meant to be to a different post? 🙂

Ah yes my mistake as I had not been following the exact same steps after updating giving the impression it was fixed. I was drawing the rectangle immediately over the text frame without transforming it, and then subsequently wrapping, floating and then copy/pasting the frame which wasn't triggering the bug. I'll get this logged, thanks.

Hi @dcgall, It will likely be 'Lock Children' which is toggled on, with the move tool selected go to the tool options menu on the context toolbar (shown below) and then toggle this setting off and then try re-sizing your artboard container again. https://affinity.help/designer2ipad/English.lproj/pages/Tools/tools_move.html

Welcome to the forums @Marlique, To add to what Walt's mentioned above, if you are a V1 owner you are entitled to an additional discount on the Universal License (All three V2 apps), you can find out more about this upgrade offer below. https://affinity.serif.com/en-gb/store/upgrade-offer/

Hi @MikeTO, I was about to log this as I could replicate this every time in 2.2.1, but after updating Publisher release to 2.3 today this appears to have been fixed as I can no longer replicate it, can you confirm?

Hi @Gnaciux, Thanks for the files, you're correct in that it's not possible to export your .afbook file out to a PDF with the bleedbox included, though the problem is not specific to your file as on Windows I cannot export a basic blank document with bleed included via the Book export function, the option remains disabled regardless and I have to manually export out the individual chapter(s) to get a bleed. In my earlier post I had only conducted the test on Mac where the 'Include Bleed' option remains accessible so long as there is a bleed set on the chapters, i'll get this Windows-specific bug logged with the developers. I've not identified a way to workaround this on Windows outside of manually exporting out the individual chapters, though as a one off since I have access to both Mac and Windows I can offer to export your .afbook file from MacOS with bleed if you send me a screenshot of your desired PDF export settings and send you a private download link for the file.

Hi @MikeTO, I've replicated and logged both of these issues with the developers.

Hi @Hietaharju, I'll get your SVG file logged with the developers for further investigation with regards to it failing to open in V2 as it should at minimum open the file as V1 was able to.

Welcome to the forums @Anonymous Puddle, The issue doesn't appear to be specific to Affinity, if you open any of your attached .SVG files in a web browser view or another SVG compatible app such as Illustrator the text also isn't centred, see the screenshot below for reference. The problem could be the fact that both the top and bottom text exists as a part of the same text object in Inkscape with alignment rules and a high leading value set, and when this is exported to SVG and parsed in Affinity/Other apps the singular text frame is split into two separate Art text layers and the original text alignment is lost as a result. I'm not overly experienced in Inkscape but you could try separating this single text object into two separate text frames like i've done in the attached document and then exporting to SVG again, as this appears to prevent the alignment issue from occurring by retaining the separate text object's relative position on the canvas. CR Shirts Test ORIGINAL INKSCAPE FILE updated in Inkscape.svg

Hi @Sikaru welcome to the forums, The Affinity apps don't currently support Indic Language text/typing features unfortunately, this has been discussed and requested in previous forum threads. Feel free to voice your support for this to be added in the feedback thread linked below.

Welcome to the forums @zzz, I've now logged this translation/mislabelling error internally. The half blue/Grey crescent button to the right hand side will show you a Split Before/After preview, the button shown in your screenshot will only show a 'Single View' mode so it won't change the view to a before/after comparison.

Good spot, we've not known the apps to crash when opening them using Rosetta and i've not had to advise on doing this before, but it would certainly worth be ruling out @Paddys Parlor if you could try running the app with this option turned off so the app is running natively (Right click Publisher in the 'Applications' folder > 'Get Info' > uncheck 'Open using Rosetta'). ---- In addition to what I mentioned in my previous reply I would suggest disabling your custom installed fonts (Should be in the Font Book app under 'My Fonts' on the sidebar) on your user by highlighting them all and then selecting 'Deactivate' before trying to launch the app again, if that works you could then try re-enabling a few at a time until the culprit font is found.

Hi @joe_l, There's a known bug on Windows only where the manually entering in an image scale % value the output value is arbitrary/unexpected, for example if I had an image with 25% X axis scaling and tried to set this to 100% by manually entering in the value the output is 400%. I'm wondering if this is the bug you're encountering? As a workaround using the slider from scale field dropdown will update the scale value correctly, but it's not ideal since the slider scale makes it difficult to set precise values and it's alot more work then just manually entering the value.

Thanks, that at least rules out it being a font cache problem and does potentially point towards there being a problem with the app reading one of your existing active fonts. I was under the impression that this is a System default font so the font isn't replaceable by any standard means (i.e Font Book). When you mention the font was overwritten, did you re-download the 'Arial' font from an external source and then press 'Keep both'? If so, you could try just right-clicking Arial in the Font Book > Deactivate which should leave just the standard system font and try launching the app again. The crash likely only occurs on your user profile as your font installation directory will be configured to your local library (~/Library/Fonts/). Do you have many custom fonts installed locally or installed by a third party font manager?

Hi @Paddys Parlor, The Crash report backtrace makes multiple references to Fonts leading up to the crash, so you could try the following to clear the font cache: Ensure that you’re logged in to an Admin account before following the below. 1. Quit all open applications. 2. Start Terminal (Finder > Applications > Utilities Folder) 3. Type sudo atsutil databases -remove and press Return. 4. Type your password at the prompt (no characters will echo back to the screen). 5. When the process is complete, type exit to end your command line session, choose File > Quit to exit Terminal, then restart your Mac After you've cleared the cache, try opening Publisher again.

I've now replied in your separate bug report thread regarding these issues. 🙂 Hmm.. I can't get it to look like your image preview with my provided config files using the original EXR image, have you unzipped the file in the iPad's local storage (I've just used the root directory of 'On my iPad') and linked Photo 2 to the entire folder on local storage? In my example I also had all the OCIO specific settings turned on under the App settings > Colour. It may also be worth trying a different .EXR file for comparison.

Hey @DM1, This is a known issue on iPad with adjustment interface which can flicker/disappear when the screen is tilted at certain angles. I'll bump the existing issue with your report and hopefully we'll see this fixed soon as it is disruptive. The OCIO adjustment dropdown menus lack of space has also been logged previously so i'll bump this.