Search the Community

G13RL: That's indeed a usable workaround for artistic text. I don't mind choosing the layers and not the group. For Frame-text: Yes, it changes the box only, not font-size

I don’t think you can change the size if the text if you have a group selected. You can change the size of the text the way I mentioned above if all of your text is of the same size but you can’t do it if the text is formatted to different sizes. I don’t know if this is by design. However, you can change the size of many selected text layers – when each text layer has a different font size – via the Horizontal Scale and Vertical Scale fields of the Character Panel. I don’t know if this will cause problems with other things later. Note: As iconoclast mentioned above, when you mention that you are working with text, it’s better to say whether you are using Artistic Text, Frame Text, or a mix of the two, as some functionalities differ between the two.

A good answer will depend on what you mean by the words “group”, “fonts”, “scale” and “all”, but a quick answer, if it will help, is that you can select all of the Artistic Text layers, or Frame Text layers, and then use something like “*2” or “*0.5” (without the quotes) in the Font Size field in the Context Toolbar to change the size of the text (when put in simplistic terms). If you want something different, and/or more specific, then you will probably need to give us more details about what you have and what you want to do with it.

Here is how to reproduce: Add a line Add a stroke and extremely large arrowheads to it (eg. the Bar type at maximum size) Add an Art Text layer Mess with Constraints and create a symbol (Constraint Group) from both Now the arrowheads are not taken into account in the bounding box computation and appear clipped. Additionally, maximum size for the Bar arrowheads is capped at 500%, even when higher values are typed into the text input field. In certain instances, this can be too small. Same on both Mac and Windows.

Okay. So now I want to copy one drawing to another page with other drawings. Thanks to poor GUI design I now have to spent my afternoon selecting all curves one by one, tick the stroke pulldown, tap the "scale to object" checkbox. So my transform "tool" will visually scale te drawing to the size I need it in to match the other objects. And no, making a transform group does not help, the text stays the same size. I now need to go in and change the font sizes of all text one by one. I can't beging to describe how bad GUI design this is.

Yes but as I mentioned originally, it's a waste of memory , disk size and inefficient to have to apply the clipping the text to every image in a group. The file I uploaded was just a simple example. In the real world, I often have 25-50 layers inside of a group. To apply the clipping to every layer in the group is unreasonable. Additionally, the lack of support for the gradient layer (and probably other layer types as well) means that I cannot truly replace photoshop with affinity photo. IMO, they should implement these basic levels of compatibility or they will lose customers who have these types of images but have to keep photoshop around in order to edit existing material...

The pdf was published last year from PP X9 for a group emailing. It was opened this year in Pub and tidied up as in the screenshot with the map in it. The saved afpub file was sent to my colleague, with problems that only show on the Mac (both full size and laptop). I have just discovered that Affinity on the big Mac seems unable to access the Calibri font. This is present on the Mac, and Word accesses it with no trouble. In Pub, it's shown as ?Calibri on the font indicator when text is highlighted, but Calibri does not show up in the font list. I don't know what it is displaying in, but it's a heavier looking font. Calibri works well on this Win 10 machine, and used to on the Mac (can't speak for the laptop, though). But apart from that, in the Mac display lines of text are split as they were when the pdf was opened, but these were corrected by me on Win 10 before saving as afpub. I'm used to that happening when importing things - I once had an article from someone typed on an iPad or similar that had three words on each page. (It was a three A5 page article when I'd taken it into LibreOffice, removed all the page breaks, and reimported it...). To Dazmondo: I have never come across 'package' as a way of doing things, never having had need to find out what it was. (If you're a carpenter, you seldom need a spanner, and mechamics have even less need of planes...)

One option would be to steal what apps like Pages, Word and even Publisher (attempt to) do with text styles. If you modify an existing style the app provides a visual marker indicating that while you are using this base style, you have made changes that aren't reflected in the current style settings. At this point you could choose to revert the style to the original settings, update the original style to match the current settings, or create an entirely new style based on the existing settings. Creating a similar workflow with brushes in the Affinity apps would be most welcome. You could even automatically group brushes by their parent so that you could immediately see all of the brush variants created from the original—kind of like drilling down in a layer group, but it would be a brush group. For example, you could create a number of pen variations including brush size and hardness based on one parent, which could all be accessed by selecting the parent and looking at the existing variations. This way you could create common sizes, variations that you use often and keep them associated with the original, default brush.

Hi, Here is a link to a YT vid that is VERY helpful explaining master pages and how to set them up for various projects. https://www.youtube.com/watch?v=Kr5je_swyJU How I build my books: I start with pen and paper to map out what pages I want my book template to have. This gives me an idea of what kind of master pages I might need. ( Disclaimer: I'm dyslexic so if I mix up sides, well, you know.) Title Page (starts on right, usual western book format) Copyright page (back of Title Page) Book Info page (title, author name, country of publication, year of publication. On Right) Blank Page Table of Contents pages (I usually set aside 3) Blank Page Chapter one page (no page numbers showing, no section name at top. Chapter 1 is centered in top third of page. First paragraph, first line is 1/3 down from top of page) Text Body pages- spread. Left page and right page have 3 text frames each. Running Text at top for Book Name on left. On Right, insert>section name. This pulls the section name from the section panel. Chapter 1 is the name of chapter 1's section. I like page # to start here at '1'. MIDDLE frame: Where the texts resides. Identical for L and R pages. BOTTOM frame: Where I like to put the page numbers. Identical for L and R pages. Historical Context page: starts on the Right, if I choose to insert one. Index spread: Much like the Text Body spread. Master Pages: 1. Title page. Book title is centered vertical and horizontal. I set the font, font weight and the size here. 2. Copyright - Book Info pages. One master page spread. I use dedicated text frames with the set info. Like logo, copyright wording, format of book info, etc. When this master is applied to actual pages, I just edit the place holders with the needed text on theses interior pages, NOT the master pages. 3. Table of contents: Starts on the Right, but I set the Left page of spread as if the TOC continues onto the BACK of right page. Just in case the TOC is long. 4. Blank page - Blank page spread. I like to use this at end of chapters so the Chapter always starts on the odd page (Right page) 5. Chapter page: no #, or running text at top. 6. Text interior - Text interior spread. Set up as described above. 7. Historical context continuation page (left) - Historical Context start page (right). This looks like the TOC master. 8. Index continuation (left) - Index start page (right). Like TOC master So I have 8 master page spreads to set up. I NAME each master so I know which master to apply when working fast. Next, I figure out what my section names will be. Usually this is just the 'Chapter _' name, but sometimes I might add a description. eg. Chapter 1: The Fight. Up next, I figure out my Text Styles. I'm setting a CHARACTER style for BOLD, and ITALICS. That way, then I place the raw text into the Publisher doc, I can do a Find and Replace for bold and italics in the original text, if it exists. BECAUSE, once I apply the body text style, the formatting pulled in from the original doc will be overwritten. The author will be upset if their bolds and italics are missing. In Find and Replace, I use a search for regex of each. I replace them with the appropriate CHARACTER STYLE so they remain bold or italics when the body text PARAGRAPH style is applied. I like my PARAGRAPH styles to be in a hierarchy, so I draw out on paper what I will need. Once I know, I DELETE all styles so I can start fresh with mine. Group Style: 'BASE'- here is where I set the body text font, size, leading and if text will be on the baseline or justified. Now my PARAGRAPH styles will refer to this group style, so if I change the font, I do it here on the base so it ripples through. PARAGRAPH Styles: BODY-main text: I name it like this. Here I tell it to refer to the BASE and set the 'next' style to be 'same'. I'm still learning about text styles, but in this one I will set the indents left and right of text frame and the indents for first line in a paragraph. (0.03in so text never touches the margins when uploaded to KDP) If I want a space between paragraphs, I set that here too. Flow, and baseline is set here as well. FIRST-paragraph: I will use this if I want to have a drop cap for the start of a chapter. It refers to the BODY-main. Next style is set as BODY-main. CHAPTER-head: This is where I input how many pts (or inches, cm, mm) I want the chapter name to appear from the top of the text frame. I set the font and such, and set next style as the "BODY-main." I also indicated here how much space will be between the head and the text. QUOTES-special: If there is a quote, song lyric, poem, portion of a letter, I set the left and right indents. I might set the font to something else or refer to BODY-main. LETTER-to: If I want to have the salutation indented in a certain way or change font. LETTER-from: I like this to be right side indented. And so forth. I honestly don't know if this is the proper way to set up a novel or if this is a good workflow. I'd love some suggestions from all the knowledgeable people on this forum on how to make this process faster, better, and logical. Stay safe! Nin

Publisher Features I use all the time: Master Pages Text Frames Text Styles, Paragraph and Character Styles. Master pages should hold things (graphics or text) that you want/need on every page or a set of pages. Sometimes you'll want an actual photograph on each page, most likely you'll just want a Picture Frame on each page so each page can have a different photo on it but in the same location. Text Frames are what hold the text in your ezine or newsletter. I put most of them in Master Pages but that is for the way I work. Text frames are in two flavours, Art Text and Frame Text. Learn about the differences. Frame Text text frames can have a background colour and a border, they can have offsets for the text on the top the bottom the left and the right. They can have a Baseline Grid so the text can be neatly aligned. Text Styles are great, you can set them up so the text size for all your text can be increased or decreased very easily. You can change the font from a Serif to a Sans Serif font with a simple click. Bolded text can be made more bold through the entire document by changing one setting in the Character Style. Paragraphs can be changed from a bulleted list to a numbered list quite easily. All you need is to use the Paragraph and Character and Group styles. If you are going to be using a lot of images, photographs or digital artwork drawings then read up on what the Picture Frame can do.

I cannot say that this problem started with upgrade to v 1.10.4.1198 because I haven't been editing for a while. But over the past 3 days, I upgraded and then have been working a lot on a project. I am finding frequent crashes are biting at my ankles. It is interesting, because it seems what has failed is response to clicks, attempted selections, etc. But the menu responds. But anything I try to do through the menu does not work. It's like everything is frozen except for opening and making selections on the menu, but nothing responds. So here is how I am using the program which is making this happen: I am using it somewhat like Adobe Illustrator. I will put a rectangle on the screen, use the points ruler to make certain sizes, move it to a place, put a text box on top and group. Later I may edit the size of the box. etc. I have been finding this freeze problem often. Once in a while it will have a auto saved version for me to open, but it does not offer that up unless I try to open the file I was working on. Any thoughts? Should I roll back to a previous version? (Not sure best method to do that).

Just in the UI as a general how to showup change, or in order for placed artistic text usage on documents? For the first, IMHO you can't change that for the UI-lookup. - For the latter, place a rect of the size of the artistic text below, group both together so you can handle them like one object. Change the rects stroke/fill colors to what you want.

Thanks for the file. The slice you're exporting has been created from the Text Layer, and then manually resized to fit the page's size. When a slice created from an object is exported, it will only export the contents that the slice is created from and ignore anything above or below it. In your case, creating the slice from the Group object would allow the image to export, however that would break the automation it looks like you've tried to create. Off the top of my head you could make the image into a symbol (to save you updating the image multiple times) and then duplicate it for however many slices you need to create (based on the text layers). If you created a group for each set of images and text layers, you could then just create a slice from each group like the attached example. Example.afdesign

Happens to me too on Windows. To place an asset with the text size unchanged, I have to move the group out of the Artboard and add it then to the Assets panel.

Hi all, Wonder if anyone can shed some light on this for me? I'm creating Symbols in AFD on the Mac but its just not working for me: I'm creating labels and have created a base, which I've grouped and then clicked 'Create' to create a symbol of that group. I then drag out the symbol to other areas of the artboard to replicate. But... The font sizes are all wrong in the symbol copy; for example - text a is Montserrat and size 14, in the symbol its size 8. text b is Times size 18, in the symbol its size 6. Have added a screenshot to what I mean. Does anyone know why it could be doing this? Cheers

I do agree with the definitions posted by @thomaso . In that definition it would definitely be a bug. I refuse to believe that it works as intentionally designed. Perhaps just badly designed and sort of an accidental design flaw. Proof of my statement is the following. Selecting multiple shapes (i.e. an instant grouping) transforms everything in scale. - This is logical. You could create a group and transform but this is faster. Selecting multiple shapes and selecting "Transform separately" implies a equal transformation (either relative or absolute) for all selected items. Just transforming 1 item out of the larger selection makes no sense as you could just select one item to have the same effect. So why design this function to work in this way. Selecting multiple text fields and changing the font size results in all text field changing the font size. Not just one. also does it not do a relative font size change. So the application has different behavior in comparable use cases. In most Mac applications resizing multiple (non grouped) objects with entering a new absolute size results in all objects getting that size. So this is de expected behavior. I can think of no reason of why it should work the way it does. If only developers can decide of something is a bug then nothing would be a bug. In my many years in software this is also very uncommon practice.

I made benchmark file for anyone who can be interested in measuring Affinity apps canvas performance with text layers. There are multiple groups of text layers each of them containing from 4 to 72 thousands of characters. To start testing, select any group you like and start dragging it around the canvas. If you're seeing good visual response from your system (in ideal it should be something around 60fps) then you may choose another group with more text. You can also select multiple groups of the same or different size. At some point you should start noticing significant performance decrease, delayed redrawing and fps drop. My observations: For some reason, all these drag operations are performed solely by CPU. GPU is not used at all (see that tiny blue line in screenshots below). This fact may explain the reason why performance is so bad with dragging text layers and any artboards or group of objects with text layers. I measured system load and recorded CPU and GPU activity (see the screenshots attached below). System was tested with i9-9900K fully enabled – 8 cores and 16 threads. And I also tested it with only 4 cores and 4 threads enabled, without Hyper-Threading. Visual response was nearly the same (low) in both cases which is quite surprising to me. Seems like no matter how many cores you may have, it will stutter and lag without proper help of GPU. Verdict: There's definitely a need for more intense usage of GPU in such operations like dragging and moving layers on canvas. P.S.: Also added diagnostics file about procedure calling stack (might be useful for developers). affinity_text_benchmark.afdesign resource_diag_during_text_layer_move.txt

We are pleased to announce an update for the Windows release of Affinity Designer, version 1.10.4 (replacing 1.10.3) (Note: 1.10.2 was an iPad only release) The detailed changes in Affinity Designer for Windows 1.10.4 (over the last release Affinity Designer for Windows 1.10.1) are as follows: Fixes & Improvements: Fixed Refine Selection as New Layer with Mask preventing rendering of Artboards Fixed Brush Hardness changing when swapping tools Fixed document with 'Save History' failing to save after promoting a Group to a Layer Fixed vector import potentially importing with the wrong document size Fixed PSD import of Linear Burn blend mode being imported as Multiply Fixed some occasionally fonts failing to be recognized at startup Fixed Borderless printing having a border Fixed 'Preset Manager' > 'Shape Presets' being unable to click Fixed hang on My Account page Fixed crash when closing the application Fixed potential crash on launch when a sync'd asset references an unavailable font Fixed 'Convert to Curves' crash with underlined text, emoji etc. Fixed Vector import (SVG etc) can be created at incorrect size Screen and UI corruption (in 1.10.3) on some desktops App hanging on shutdown due to font cache problem Help & localisation improvements. The improvements in 1.10 over 1.9 are listed in some detail in this 1.10.0 Designer Windows update announcement UPDATING TO THIS VERSION (free for existing customers) The software version can be seen on the splash screen and the About dialog (in Help > About Affinity Designer). If you’ve purchased from the Affinity Store— each time you start the Affinity Store software it will check for updates and offer any available update. The latest update will install over the top of any earlier version, with no need to uninstall. You can download the latest installer by logging into the affinity store here and find the order in your account and use the "Download" button in there. Alternatively, this new release (and previous versions of Affinity Designer for Windows) can be downloaded from this link (that installer is NOT for Windows Store purchases and needs a product key). If you’ve purchased from the Microsoft Store— Microsoft Store updates are done automatically by the operating system (each time you start the application). If this does not happen for you, open the Windows Store app and click the three dots in the top right corner of the app and then go to Downloads and Updates. Click Get Updates. This should hopefully force the update to show.

We are pleased to announce an update for the Windows release of Affinity Photo, version 1.10.4 (replacing 1.10.3) (Note: 1.10.2 was an iPad only release) The changes in Affinity Photo for Windows 1.10.4 (made since the last release Affinity Photo for Windows 1.10.1) are as follows: Fixes & Improvements: Fixed Refine Selection as New Layer with Mask preventing rendering of Artboards Fixed Brush Hardness changing when swapping tools Fixed Live Filters with Radius or Distance spuriously changing the Azimuth anticlockwise Fixed Toggling 'Quick Mask' not updating until you toggle the mask off and on again Fixed 'Overlay Paint' and 'Overlay Erase' tools in Develop Persona not painting with correct spacing Fixed document with 'Save History' failing to save after promoting a Group to a Layer Fixed vector import potentially importing with the wrong document size Fixed 16-bit 'Saturation blend mode' displaying white pixels Fixed crash painting on empty pattern layer Fixed 'Levels' > 'Output black and white' using the same values when changing channels Fixed files losing quality after a merge or export Fixed potential crash opening an EXR document Fixed crash opening multiple FITS files at once Fixed DNG files not being displayed in Develop Persona with Hardware Acceleration enabled Fixed Astrophotography to cope with Unicode file paths Fixed PSD import of Linear Burn blend mode being imported as Multiply Fixed some occasionally fonts failing to be recognised at startup Fixed Borderless printing having a border Improved 'Uninstall Pack' flow to auto-select the pack Fixed 'Preset Manager' > 'Shape Presets' being unable to click Fixed hang on My Account page Fixed 'Defringe' > 'Also remove complementary colour' Fixed crash when closing the application Fixed potential crash on launch when a sync'd asset references an unavailable font Fixed document pixel resolution being stored in the wrong format within XMP metadata (breaks later parsing of the same data; hides the values from the metadata panel's 'Detail' view) Increased maximum defringe radius Fixed 'Convert to Curves' crash with underlined text, emoji etc. Fixed Astrophotography Stack failing on some DNG's with no warning Improved Astrophotography 'Make Align Layers By Stars' to work for layers in transformed groups Screen and UI corruption (in 1.10.3) on some desktops. App hanging on shutdown due to font cache problem. Help & localisation improvements. The improvements in 1.10 since are listed in some detail in this 1.10.0 Photo Windows update announcement UPDATING TO THIS VERSION (Free for existing customers) The software version can be seen on the splash screen and the About dialog (in Help > About Affinity Photo). If you’ve purchased from the Affinity Store— each time you start the Affinity Store software it will check for updates and offer any available update. The latest update will install over the top of any earlier version, with no need to uninstall. You can download the latest installer by logging into the affinity store here and find the order in your account and use the "Download" button in there. Alternatively, this new release (and previous versions of Affinity Photo for Windows) can be downloaded from this link. (that installer is NOT for Windows Store purchases and needs a product key). If you’ve purchased from the Microsoft Store— Microsoft Store updates are done automatically by the operating system (each time you start the application). If this does not happen for you, open the Windows Store app and click the three dots in the top right corner of the app and then go to Downloads and Updates. Click Get Updates. This should hopefully force the update to show.

We are pleased to announce an update for the macOS release of Affinity Publisher, version 1.10.4 (replacing 1.10.3) (Note: 1.10.2 was an iPad only release) The detailed changes in Affinity Publisher for MacOS 1.10.4 over the release build Affinity Publisher for macOS 1.10.1 are as follows: Fixes & Improvements: Optimised for new ProMotion 120hz screen, M1 Pro and M1 Max. Architecture changes when Metal compute acceleration is enabled to better support M1 Pro and M1 Max. Fixed document with 'Save History' failing to save after promoting a Group to a Layer. Fixed PSD import of Linear Burn blend mode being imported as Multiply. Vector import (SVG, IDML etc) can be created at incorrect size. Space incorrectly gets added to text on clipboard if you double click a word to highlight. Fixed bug when deleting multiple pinned objects at the same time. Placed .afphoto documents can cause redraw issues. PDF Passthrough could crash when rendering entire placed document. Positioning pins should not find frames that are not editable. Hyperlinks with 'MailTo' fail to export when containing a space. Miscellaneous stability updates arising from specific cases. Invalid URL hyperlinks prevent PDF export. Fixed crash on Monterey editing embedded documents Screen and UI corruption (in 1.10.3) on some desktops Resource manager display was sometimes incorrect Date & Time field format options not appearing. Help & localisation improvements. The improvements in 1.10 since 1.9 are listed in some detail in this 1.10.0 Publisher macOS update announcement UPDATING TO THIS VERSION (Free for existing customers) The software version can be seen on the splash screen and the About dialog (in application menu, Affinity Publisher > About). If you’ve purchased from the Mac App Store— updates are done automatically next time you run your software after it is available in the Mac App Store. If this does not happen for you, open the Mac App Store app and go to the Updates page and then Store > Reload page or press CMD+R. This should hopefully force the update to show. Apple sometimes phase roll outs around the world which can mean it may take up to 72 hours for your update to be available. If you’ve purchased from the Affinity Store— each time you start the software it will check for updates and offer to download and install any available update, or in the application main menu there is an option Check for Updates. You can download the latest installer by logging into the affinity store here and find the order in your account and use the "download" button in there. Alternatively, this new release (and previous versions of Affinity Publisher for macOS) can be downloaded from this link (that installer is NOT for Mac App Store purchases and needs a product key).

We are pleased to announce an update for the Windows release of Affinity Publisher, version 1.10.4 (replacing 1.10.3) (Note: 1.10.2 was an iPad only release) The detailed changes in Affinity Publisher for Windows 1.10.4 over the release build Affinity Publisher for Windows 1.10.1 are as follows: Fixes & Improvements: Fixed document with 'Save History' failing to save after promoting a Group to a Layer. Fixed PSD import of Linear Burn blend mode being imported as Multiply. Vector import (SVG, IDML etc) can be created at incorrect size. Space incorrectly gets added to text on clipboard if you double click a word to highlight. Fixed bug when deleting multiple pinned objects at the same time. Placed .afphoto documents can cause redraw issues. PDF Passthrough could crash when rendering entire placed document. Positioning pins should not find frames that are not editable. Hyperlinks with 'MailTo' fail to export when containing a space. Miscellaneous stability updates arising from specific cases. Invalid URL hyperlinks prevent PDF export. Date & Time field format options not appearing. Screen and UI corruption (in 1.10.3) on some desktops. App hanging on shutdown due to font cache problem. Resource manager display is sometimes incorrect. Help & localisation improvements. The improvements in 1.10 are listed in some detail in this 1.10.0 Publisher Windows update announcement UPDATING TO THIS VERSION (Free for existing customers) The software version can be seen on the splash screen and the About dialog (in Help > About Affinity Publisher). If you’ve purchased from the Affinity Store— each time you start the Affinity Store software it will check for updates and offer any available update. The latest update will install over the top of any earlier version, with no need to uninstall. You can download the latest installer by logging into the affinity store here and find the order in your account and use the "Download" button in there. Alternatively, this new release (and previous versions of Affinity Publisher for Windows) can be downloaded from this link (that installer is NOT for Windows Store purchases and needs a product key). If you’ve purchased from the Microsoft Store— Microsoft Store updates are done automatically by the operating system (each time you start the application). If this does not happen for you, open the Windows Store app and click the three dots in the top right corner of the app and then go to Downloads and Updates. Click Get Updates. This should hopefully force the update to show.

Status: Beta Purpose: Fixes Requirements: Purchased Affinity Publisher Windows Store: Not Submitted Download: Download Auto-update: Not Available --- We are pleased to announce that Affinity Publisher Customer Beta 1.10.2.1187 is now available as a download from the link above. If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry. This beta is an incremental update to the 1.10.1 version recently released to all customers. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below. --- Fixed document with 'Save History' failing to save after promoting a Group to a Layer. Fixed PSD import of Linear Burn blend mode being imported as Multiply. Vector import (SVG, IDML etc) can be created at incorrect size. Space incorrectly gets added to text on clipboard if you double click a word to highlight. Fixed bug when deleting multiple pinned objects at the same time. Other assorted small fixes. Previous Beta Release Notes --- To be notified about all future Windows beta updates, please follow this notification thread To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

Status: Beta Purpose: Fixes Requirements: Purchased Affinity Publisher Mac App Store: Not Submitted Download: Download Auto-update: Not Available --- We are pleased to announce that Affinity Publisher Customer Beta 1.10.2.1187 is now available as a download from the link above. If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry. This beta is an incremental update to the 1.10.1 version recently released to all customers. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below. --- Fixes and Updates Fixed document with 'Save History' failing to save after promoting a Group to a Layer. Fixed PSD import of Linear Burn blend mode being imported as Multiply. Vector import (SVG, IDML etc) can be created at incorrect size. Space incorrectly gets added to text on clipboard if you double click a word to highlight. Fixed bug when deleting multiple pinned objects at the same time. Other assorted small fixes. Previous Beta Release Notes --- To be notified about all future Mac beta updates, please follow this notification thread To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

Click here to download the latest beta Status: Customer Beta Purpose: Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Changes Fixed document with 'Save History' failing to save after promoting a Group to a Layer Fixed vector import potentially importing with the wrong document size Fixed PSD import of Linear Burn blend mode being imported as Multiply Fixed some occassionally fonts failing to be recognised at startup Fixed Borderless printing having a border Fixed 'Preset Manager' > 'Shape Presets' being unable to click Fixed hang on My Account page Fixed crash when closing the application Fixed potential crash on launch when a sync'd asset references an unavailable font Fixed 'Convert to Curves' crash with underlined text, emoji etc. Previous release notes

Click here to download the latest beta Status: Customer Beta Purpose: Fixes Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum. Fixed Toggling 'Quick Mask' not updating until you toggle the mask off and on again Fixed 'Overlay Paint' and 'Overlay Erase' tools in Develop Persona not painting with correct spacing Fixed document with 'Save History' failing to save after promoting a Group to a Layer Fixed vector import potentially importing with the wrong document size Fixed 16-bit 'Saturation blend mode' displaying white pixels Fixed crash painting on empty pattern layer Fixed 'Levels' > 'Output black and white' using the same values when changing channels Fixed files losing quality after a merge or export Fixed potential crash opening an EXR document Fixed crash opening multiple FITS files at once Fixed DNG files not being displayed in Develop Persona with Hardware Acceleration enabled Fixed Astrophotography to cope with unicode file paths Fixed PSD import of Linear Burn blend mode being imported as Multiply Fixed some occassionally fonts failing to be recognised at startup Fixed Borderless printing having a border Improved 'Uninstall Pack' flow to auto-select the pack Fixed 'Preset Manager' > 'Shape Presets' being unable to click Fixed hang on My Account page Fixed 'Defringe' > 'Also remove complementary colour' Fixed crash when closing the application Fixed potential crash on launch when a sync'd asset references an unavailable font Fixed document pixel resolution being stored in the wrong format within XMP metadata (breaks later parsing of the same data; hides the values from the metadata panel's 'Detail' view) Increased maximum defringe radius Fixed 'Convert to Curves' crash with underlined text, emoji etc. Fixed Astrophotography Stack failing on some DNG's with no warning Improved Astrophotography 'Make Align Layers By Stars' to work for layers in transformed groups Previous release notes