NathanC

There is also an official affinity tutorial below on creating vector mandalas with symbols, it is demonstrated on desktop but the same workflow can be replicated on iPad. 🙂

Looks like you have the 'Life as a Genealogist' assigned to the 'Main header' style hidden at the bottom of page 1 along with some additional hidden text, if you reveal this text at the bottom of the frame by pressing the Eye icon and then delete it and update your TOC, it will remove this entry. Before: You can then assign the correct 'Life as a Genealogist' title on page 2 to the 'Main header' style and update your TOC again, and it will correctly update the page number to 2. After: Edit: Assigning the 'Main Header' on the correct page does push the last line of text onto the next flowed text frame, if you want to prevent this try reducing the 'Space after paragraph' value on either the text style settings or locally via the paragraph panel to remove the extra space. TOC error updated.afpub

Hi @John T, Check in the section manager in the pages panel, as you may have created a separate section starting from page 2, like in the example below. If not, it would be beneficial if you could upload your document so we can take a look, if you don't wish to share it publicly I can provide a private upload link. Thanks!

Yep, perfect timing on the posts, I can now replicate the issue with 'scale with object' enabled, I'll confirm if this has been logged previously and if not I'll get it logged, thanks. 🙂

Hi @anto, I'm also unable to replicate any issue with this after setting up the same document and setting the zoom level >600% on W10, at no point did rendering artefacts appear during my tests. This may be something specific to either your Hardware or your document setup. As a temporary measure, if you set your 'Renderer' in the Performance Preferences to WARP, turn H/A off, close the interface and restart the app when prompted to and try again, does it persist? Could you perhaps upload your sample document in case the setup is somehow related? Thanks

Going back to the original example, this does look like a bug with bounding box snapping, the non-rotated curve refuses to snap to the newly transformed bounding box of the rotated symbol, and instead snaps to the bounding box's original bounds as if the rotated symbol wasn't being simultaneously transformed, but this does work vice-versa if you start with the rotated curve. I've now logged this with the developers.

Hi @LCamachoDesign, Thanks for providing detail, I've discussed this internally with the QA team and it looks like this is likely by design, the expand stroke function separates the original shape into it's two components: the stroke and the fill. In this scenario you do have a stroke applied to the object since you have a stroke width, it just doesn't have a colour which the function isn't checking for, as objects can exist on the canvas without a fill. However, I do agree that I can't really see the intention behind it's current functionality, so I'll be logging this as an improvement internally based on your suggested remedies so that it does not leave a secondary curve object for the invisible stroke.

Hallo @xul1, Soweit ich weiß, muss die Indizierung derzeit pro Kapitel erfolgen, wie Sie es beschrieben haben. Die Funktion "Im Dokument suchen" im Indexfenster sucht nur nach Einträgen in Ihrem aktuell geöffneten Dokument und nicht im gesamten Buch. Wenn Sie eine globale Bucheinstellung für die Indizierung wünschen, können Sie dies gerne im Feedback-Bereich des Forums posten. 🙂 https://forum.affinity.serif.com/index.php?/forum/52-feedback-suggestions/

Hi @TheSnooze, This is a known issue that has now been fixed in the 2.2 beta, if you wish to give the beta a try feel free to signup for the beta from the link below. 🙂 https://affinity.serif.com/en-gb/affinity-beta-program/

The dedicated 'Personas' help article references that switching personas is done by 'select a persona from the popup menu' which is far more accurate description for iPad: https://affinity.help/designer2ipad/English.lproj/pages/Introduction/about_Personas.html The dedicated 'Switching Personas' help article you've shown should also reference this same instruction, as at the moment that is more applicable to desktop. I'll get this raised with the docs team, thanks. 🙂

Hallo @Red Al, Vielen Dank für die ausführlichen Informationen. Ich habe dieses Problem repliziert und es wurde nun bei den Entwicklern protokolliert.

Hi @susroc welcome to the forums, Changing Personas can be done at the top left hand corner of the screen as you've previously mentioned, but dependant on the size of your screen and the tool you have currently selected it may have been pushed off the context toolbar, with your finger if your drag to the right on the context toolbar, the additional options (including the document menu, persona button and edit menu) should all reveal themselves. If you're still having issues it would be beneficial if you could provide us with a screenshot of your app window. 🙂 Thanks

Hi @Chricken welcome to the forums, This is likely the result of the pattern layer being created from an image which is placed on a non-precise pixel location. This can be easily corrected by changing your document unit of measurement to 'Pixels' with the view tool selected and then select the image, in the transform panel you should see that the image's X/Y (and possibly W/H) having non-integer values, simply remove the values after the decimal to convert the values to be whole pixels again. If you don't see the decimal values you may need to enable Decimal places for pixels under Preferences > User Interface. Pattern layer created from non-pixel precise image layer: Pattern layer created from pixel precise image layer:

Hi @Astara, The minimum OS requirement for the V2 applications is the Windows 10 May 2020 update or higher, so unfortunately it's not possible to use the apps on Windows 7, you can find the full list of minimum requirements on the tech spec page below. https://affinity.serif.com/en-gb/photo/full-feature-list/

Hi @MrFish0409 welcome to the forums, It sounds like your problem might be better directed towards Apple support, as the forums are intended for discussions and questions surrounding the Affinity products. 🙂

Hi @Hangman, Many thanks for the detailed steps, I've replicated this on MacOS (worked fine on windows for me) and logged it with the developers.

Hi @a b welcome to the forums, We'll need a little more info so we can get a better idea of what's happening, i've included some follow up queries below: What Operating System are you using? What App version are you using? (E.G v2.1.1) If you're using Affinity Publisher, are you using the Photo persona to access the healing brush tool? Could you provide us with a screenshot of the healing brush being used before and after for comparison? The healing brush tool works very similar to the clone brush tool but blends the target pixels with the sampled area pixels, so if the cloned area is tonally and texturally different to the sampled area this might result in the blurring/unsharpness that you have described when the brush stroke is used on two completely different areas of the image, is the choice of this tool intentional or might the clone tool work better? https://affinity.help/photo2/English.lproj/pages/Retouching/retouching_cloningHealing.html If you could include any other relevant information and sample files that would also be great. Many thanks!

Hi @DartmoorDays welcome to the forums, The Desktop and iPad apps are completely separate purchases as they are sold per OS, if you purchased the desktop version of Photo you will need to also purchase the iPad version in order to use it. However, if you purchased the Universal License, this will allow you to access all three apps across all three platforms without requiring any additional purchases.

Hi @maxen, It looks like you've posted in the release V2 bugs section which is for bugs which affect the current release builds, for future reference if your issue is specific to the beta apps and is not re-producible in the release builds it's best to post this over in the beta software forums. A recent intentional change in 2.2 meant that Num Pad + and Num Pad - are treated independently from = and - on the main keyboard, so it's now essentially using one or the other for zooming. You could keybind the number pad +/- keys for zooming in and out instead, but this would mean that the standard = and - no longer work. This can understandably be frustrating since both cannot be concurrently used and it is logged with the developers so that both can be used again in some form, i've now bumped it with your report. 🙂

Hi @Luiz Sko, It's likely that official support for stage manager will be added in a future app update, but I wouldn't be able to give any specifics on an ETA/timeframe for this currently as we don't have any news to share on this particular feature. I would suggest following the forum thread I've linked below as it will be updated when support is added. 🙂

Hi @arifg, The App Preferences and Shortcuts are not included as a part of the content migration process, if you wanted to use the same preferences that you used in V1 you would need to manually replicate the preferences used in V1 and then set the same preferences in V2. As for shortcuts, you can export your V1 shortcuts to an .afshort file (Via Preferences > Shortcuts > Save) which can be imported into V2 file in the shortcut preferences by pressing 'Load' and then loading the V1 file, however due to some of the menus being changed between versions and new features being added you may find some shortcuts are missing.

If you're exporting to a format which requires this PDF version but have placed an incompatible PDF, using 'Fix' should just change the policy of your placed document from Passthrough to Interpret, while Passthrough is an exact reproduction of your original PDF, Interpret is the app interpreting the placed PDF's contents, which may result in some elements not appearing as they were originally intended, such as a bitmap preview but also may have no real change at all. From what I'm aware placing any PDF file which isn't also a PDF/X-1a file will result in this error due to the version mismatch, so your original PDF prior to placing it would also need to be PDF/X-1a to maintain the Passthrough, or an Interpret is forced.

Hi @Stolzy, Apologies I had missed your reply, I've included some follow up queries/requests below: - Which OS version are you using? - Do you have a screen recording which demonstrates the problem with the lag on larger brush sizes? - Could you provide a screenshot of your app Performance Preferences window? - Which affinity app(s) are you using and are you using a pixel brush? If it is a pixel brush, are you testing this with the default round brush or a custom brush? - Are you running the latest app version (2.1.1)? Screen recording guide: Many thanks!

Hi @Dan Sumption welcome to the forums, The default Preflight profile warning for placed PDF files set to passthrough is working off the assumption you're exporting your document to the PDF/X-1a:2003 PDF version and will warn you if your placed PDF file is incompatible with this version, if you're not exporting to PDF/X-1a this error can be ignored, or alternatively you can change your Preflight compatibility version or disable the warning altogether. This can all be done in the Preflight edit profile menu, accessed via the three line/burger menu to the right hand side of 'Profile'. You can then edit the behaviour of the PDF passthrough notification or turn it off altogether in Preflight, this will then create you a <Custom> Preflight profile which can then be turned into a permanent one via the 'Create profile' button found in the same burger menu. More info on Preflight profiles: https://affinity.help/publisher2/English.lproj/pages/Publishing/preflight.html https://affinity.help/publisher2/English.lproj/pages/Panels/preflightPanel.html

Hi @MikeTO, Thanks for providing detail and a recording demo, I've logged this with the developers as an improvement to the existing functionality to remove the Preflight check limitation so that it can be run on chapters which are not actively open in Pub. As it currently stands it is slightly misleading since the option does indicate it can be run on all chapters whether they're open or not, and that this could be a tedious task to open each chapter particularly on larger books.