NathanC

Hi @marco_chacon, If you export your Google drive document to a .DOCX file in Google Drive via the 3 dot menu under 'Download' this should automatically start a download of your document to your default downloads folder, this .DOCX file can then be file > placed into an existing Publisher document, where you can adjust the text and auto-flow it (if required). I've linked a couple of relevant help guides below on supported file formats and text auto flow for more info. Supported file formats: https://affinity.help/publisher2/English.lproj/pages/Appendix/fileformat.html Auto Flow: https://affinity.help/publisher2/English.lproj/pages/Text/flowingText.html

Hi @MikeTO, This is an issue that has been previously logged with the developers, I've now bumped it with your report. 🙂

Hi @Thomasdelange, The Affinity Apps have not been updated to officially support MacOS Sonoma yet since it is currently a preview/beta build, and as a result this can result in unexpected issues whilst using the apps, I would therefore recommend rolling back to Ventura until official support has been added. The apps will likely be updated to support Sonoma likely nearer the time of it's official release (And possibly in the upcoming 2.2 beta). 🙂

Hi @Subclavius, The App language under 'Settings' and the assigned spelling language under the Character panel exist as two completely separate entitles, the character panel 'language' field only apply to text frame's spellcheck since it is just a spelling dictionary which can be freely added and removed from the dictionaries directory. The app locale set under the app Settings > General to translate the whole software suite to Dutch would require implementation via the developers as a part of an app update which is quite a significant undertaking, since this would require the apps, documentation, website etc. to all be updated to that language. There is an outstanding feature request thread for the Dutch language to be added, feel free to voice your support on the thread below. Also, if you want your text frames to default to Dutch as your spelling language, after assigning this to a text frame with it highlighted go to Edit > Defaults > Synchronise and then repeat with 'Save'. This should ensure that all future text frames created default to the Dutch spelling dictionary.

@walt.farrell for me it doesn't make any sound and just fails to recognise it as a shortcut input in both V1 and V2, perhaps there is a legitimate reason for this but the shortcut doesn't appear to do anything in MacOS Ventura or In-app. I'll log it with the developers for further investigation.

Hi @laurilli74, No problem, It looks like you've linked the help guide for V1 Designer, I've linked the updated version 2 one below for reference. https://affinity.help/designer2/English.lproj/pages/Panels/assetsPanel.html

It looks like for the most part your finger taps are not being registered on the canvas. Have you perhaps got 'Touch for Gestures Only' turned on in the app settings > tools? I wouldn't expect it to be enabled since your marquee selection worked on the second attempt, but it might be worth toggling this setting on and off. Is it also the same following a reboot of your iPad? Also, if you create a new document and add some shapes/curves to the canvas instead of text, do they also experience this selection issue or is it just text frames?

Hi @laurilli74 welcome to the forums, The iOS 12 assets were not included as a default asset pack in V2, however I have exported them from V1 and attached the .AFASSET file below, to import this press on the burger/3 line menu at the top right hand corner of the panel and select 'Import Assets' and navigate to where you saved the file to. 🙂 iOS 12.afassets

Hi @LEB, I've not been able to replicate your issue on my Mac, after enabling the tab stop function on my style, adding a new tab stop and pressing 'Ok' If I go back into my style I can see that the tab stop setting has updated correctly to reflect my change. It would be helpful if you could provide a screen recording which demonstrates the issue with your text style, if you're unsure on how to do this I've linked a brief guide below. https://support.apple.com/en-gb/HT208721 Many thanks!

Strange, you'll need to keep 'auto select' always on otherwise this will prevent any object selection on the canvas, have you tried it with the option turned on and the dropdown menu to the right set to 'Default'? If it doesn't work, could you possibly provide another screen recording which shows what's happening?

Hi @Pixero, Many thanks for providing recording comparisons, they are extremely helpful 🙂. V2 introduced some additional functionality to the move tool in the form of the 'Auto Select' feature (Button with the hand along the context toolbar). When 'Auto select' is enabled this restricts your selection based on the option set along the context toolbar. In your V2 recording you currently have the auto select function enabled and set to 'Groups', this means that only objects that exist within a group container can be selected on the canvas. You'll want to keep 'Auto select' turned on in order to select objects on the canvas, but change the context setting to the right. Try changing this setting from 'Groups' to 'Default' along the context toolbar with the move tool selected and repeat your test again. More info: https://affinity.help/designer2ipad/English.lproj/pages/Tools/tools_move.html

Hi @DEF13, This is still working as expected for me on Mac and Windows, though I have to make sure that my window focus is on the filter settings that is currently open and not the canvas area by left clicking anywhere in the filter settings, I can then begin using TAB to switch between the options. If my focus is on the canvas area, TAB will invoke the 'Toggle UI' shortcut.

Hi @Larry Fjeldstrom, The apps won't allow you to add placed SVG/EPS/PDF files in your document directly into your assets, and this should result in the notification message that anto has shown above in the upper right hand corner (Independent of Linked/embedded placement policy the notification should prompt). However, if your SVG exists as an embedded resource if you select it and then click 'edit document' along the context toolbar or just double click the layer this should open it in a separate document tab, where you can select the SVG layer in the layers panel and then use 'add from selection' in the asset panel to create an asset out of it. 🙂

Hi @awakenedbyowls, Your active brush on the eraser brush tool stands out as a little odd to me because there doesn't appear to be a visible brush head preview, you could change to a different brush such as a brush in the 'basic' category. It could also be that the opacity of the brush has been set to 0%, try tapping on the accumulation button highlighted below and change it to opacity and increase the opacity value and try erasing again.

Welcome to the forums @Alexandre Paes, If you're encountering an app hang on startup, I would initially suggest trying a basic CTRL run up to do a basic reset of the user defaults and most recent documents by following the below: Close all Affinity apps Hold down CTRL and launch Photo 2 whilst still holding CTRL This will prompt a 'Clear user data' menu with three boxes ticked, in addition to these tick 'Reset Most Recent Documents' Press 'Clear' and the app will now hopefully launch. If that fails, I wouldn't expect this to be the cause if the app launched prior to updating to 2.1, but it would be worth ruling out Hardware Acceleration being the problem by running the app with the --no-ocl flag which will disable the setting from outside the application, i've linked the full FAQ below.

Hi @tylerdo welcome to the forums, The Affinity Apps have not been updated to officially support MacOS Sonoma yet since it is currently a preview/beta build, and as a result this can result in unexpected issues whilst using the apps, I would therefore recommend rolling back to Ventura until official support has been added. The apps will likely be updated to support Sonoma likely nearer the time of it's official release (And possibly in the upcoming 2.2 beta). 🙂

Hi @Erick Flores welcome to the forums, After installing the font shown in your screenshot via CC and then restarting each of my apps twice the font is appearing as expected and available for use within all three apps, there's a known issue currently logged with the developers where fonts installed via CC fail to appear for the first app session, but after restarting the apps (Might take two restarts) the fonts should load in as expected. I'm wondering if this is perhaps the issue, so I would first suggest restarting Publisher a few times and then create a new document and see if the font is available for selection and use in the character panel. If not, if you close the apps, remove the font in CC and then re-add it and then restart the app twice, does it then appear?

Hi @piccolamimi welcome to the forums, I'm also unable to replicate this using your described document setup, the pixel brush aligns perfectly with my grid, have you checked that your grid spacing is indeed set to 1px, and not 1.1px for example? Setting my grid spacing to 1.1px is the only way I can get the pixel brush to offset from the grid in a similar way to your screenshot. As well as advising on what Old Bruce mentioned above, it would beneficial if you could provide us with your document.

Hi @jgarza, I've not been able to replicate an issue with this on a network shared folder/drive by placing an linked resource which was also located on the network share (Or stored locally), this works as expected after saving again. It may be something specific to your setup/network which has caused the issue, the developers are aware of certain issues when saving to network locations such as when access to the drive has been temporarily lost this can cause a file to fail to save, even if the network drive is re-connected thereafter. This will hopefully be improved/fixed in a future update. As RichardMH mentioned, we generally advise opening and saving your files to a local location, and then moving the file to the network/removable storage after to prevent any file corruptions/issues with saving.

Bienvenue sur les forums @iprfrphshp, Je vois que vous avez répondu dans un autre fil de discussion lié ci-dessous en ce qui concerne votre plugin Topaz AI, pourriez-vous confirmer si le plugin ne fonctionne toujours pas ou s'il fonctionne depuis que vous avez supprimé le fichier référencé ?

Hi @Ezbaze, This issue has been previously logged with the developers and has been fixed in 2.2, once this version has been released/in beta it should be working as expected. 🙂

Hi @Bryce, As Hangman's mentioned there is a known issue with live filters causing the bleed area to export completely blank when it isn't nested, i've bumped the existing issue with your report. 🙂

Ahh I'm following you now, I'm not aware of a way to do this on a per layer basis currently as it is a document wide setting, if this is something you would like to see added feel free to make a post over on the feedback forum i've linked below. https://forum.affinity.serif.com/index.php?/forum/52-feedback-suggestions/

No problem at all! As far as I'm aware the content always needs to be a pixel layer in order to be affected by re-sampling methods similar to if you wanted to change the colour space of the document, it would need to be converted to a pixel layer via rasterization first since image layers exist to preserve their original image resolution and colour space. 🙂

Hi @snh230, The Affinity apps don't currently support stage manager which can result in some unexpected issues with the app when it's enabled such as the one you have described. Support for stage manager will hopefully be added in a future update but it's not something that we can provide a timeframe for currently.