walt.farrell

For the page numbering discrepancy we will probably need to see more details from the Books panel, including the numbering options for the G Part 2 and 03 Modify the Plan chapters.

For your Heading 1 vs Heading 2 issue, you will need to examine the Layers panel on the relevant document page. On any specific page, the ToC order is determined by the order of layers (layer stack), with text objects that are lower in the layer stack assumed to have been created first, and thus they appear earlier in the ToC than text objects that are higher in the layer stack (and presumably created later). Thus, in the common situation, you would resolve that issue by moving the Heading 2 text object lower in the Layers panel. But without seeing further information I can't provide more than that.

@Valerios91: I suggest you visit https://affin.co/get-support and raise a Customer Service request. One of your options there will be to ask about Volume Licensing, and you can provide further details and get an answer specific to your situation.

Probably not, as Serif does not comment on future plans, generally. Even if they do comment, and favorably, it could be years given the many items they're working on and the relative priorities of those items.

I see an additional tag, AF-2305, has been added to this topic (presumably by a moderator), but we'll have to wait for further Serif comment to know any further details.

If you've found indications that it's a known issue, then probably you could supply the bug tag associated with the issue, which will look like AF-nnnn for a more recent report, or AFD-nnnn, AFB-nnnn, or AFP-nnnn for older reports. And if you've found a bug-tag, it would be useful to tell us what it is, so we don't also have to search. The tag, if one is assigned, can be found at the top of a topic discussing the issue (in the topic header, which has a tags list). I haven't personally noticed this problem, but I can look later. Your screenshot shows a Publisher document with Pages, and such documents do not have Artboards. Artboard is a term, in Affinity applications, for a specific kind of design container that can be created in Designer or Publisher, but in Publisher you can have either Pages or Artboards but not both. The area you are calling "Artboard" is just the workspace around the document, and is controlled by the Background Grey Level setting. The Affinity applications on iPad do not provide support for a Light UI; only for a Dark UI.

It might help to have iPadOS record the screen while you do this, @Art Bone, and then upload that video so we can see what you're seeing.

Sorry; It was hidden in my view of the video, but I figured out what I did wrong. No further ideas from me.

First, for issues in the Beta you need to post in the Beta section of the forums, not the general Bugs section. A Moderator can move this for you, but it helps everyone if you remember to post in the correct place originally. Next, you do not seem to have any items in the Resource Manager selected. If you select the item that has the Missing status, does the Replace button become available? I think this is probably what @stokerg was referring to:

Welcome to the Affinity forums, @Hina Gandhi. As you're new to the forums, I just wanted to mention that generally the Serif Staff will not comment in the Feedback part of the forums. And they almost never discuss future plans or potential dates for future activities. What you've asked for here is very difficult for them to resolve, and has been a long-standing issue requested by many users, but we've seen no sign of activity yet to resolve it and I doubt anything will happen soon.

Welcome to the Affinity forums, @MRJR. While you wait for a response from the Serirf Staff, who are often quite busy, I have a couple of suggestions (as another user) that may help. As a first attempt, I would click on "Switch to another account" and try providing your Affinity ID (email address) and Affinity Store password again. If that doesn't work, you can deactivate your application, which should get you to a sign-in dialog when you run it again. Then provide your Affinity ID and Affinity Store password there. For more details on this:

Yes, but I think that one was fixed in 2.0.3, at least by my interpretation of the Release Notes (though it is hard to be sure as the Notes at that time did not include the reference Tag numbers, and the @Affinity Info Bot did not yet post when bugs were fixed): Perhaps one of the Serif Staff, who can see the bugs database, will comment.

@Twazerty: Welcome to the Affinity forums. Crashes when trying to create a new document are often caused by downlevel graphics drivers. This FAQ has additional information: Being unable to set the Renderer can also be a symptom of graphics driver issues, I think. But it might be useful to see a screenshot to see a screenshot of the Settings dialog to illustrate the issue you're having trying to set the Renderer.

Thanks, but we need to be able to see the bottom of the application window, so we can see the Status Bar. From the recording you provided we can't confirm what the current page is at all times.

I haven't tried uninstalling and reinstalling it, but the V1 apps on my iPad (specs below) are working mostly fine.

It might help to have a screenshot showing the complete application window, but specifically showing the Pages panel and the Status Bar (with the Page Navigator) so we can confirm what Page you have selected when you do the Paste. It is very easy to mistake what page is actually active for operations on the page data. For example, in the Pages panel there are two kinds of highlights, blue and gray, for pages. Blue is a page that is active for Pages panel operations, and Gray is a page that is selected for data operations (i.e., the "current" page).

Does that mean that you successfully found the mru.dat file, and deleted it, without resolving the problem? What OS do you use? The earlier problem (AFB-7024) seems to have been experienced mostly on macOS. Also, at least on macOS, there's a specific option when you start the application with Ctrl pressed to clear the most-recently-used files list. That's easier to use than finding and deleting the mru.dat file.

@sawako: Welcome to the Affinity forums. You originally purchased version 1 (V1) of Affinity Designer, and that version is no longer available for purchase from the Apple Store. You should be able to find it in your Apple Account though. This FAQ provides additional information: The V1 applications should still run on the current iPadOS release, but there are some issues that will never be fixed by Serif as they have stopped supporting that version, so in the long run if you want to keep using Affinity it is better to purchase V2 instead. But you can try to reinstall V1 from your Apple Store account for now, and see how it works on your system.

It's better to install the MSI/EXE first, then uninstall the MSIX, in my opinion. When you first run the MSI/EXE version, if it finds that the MSIX version is also installed, the MSI/EXE program ensures that all your Settings, installed content (Styles, Text Styles, Assets, Macros, Brushes, etc.) from the MSIX program are made available so you don't lose anything and don't have to reinstall any content you've added. I'm not sure that will all work properly if you've uninstalled first, especially if you don't use the standard Windows Uninstall function.

It is possible to invoke a program that is installed under WindowsApps (an MSIX-based program) but most 3rd-party applications are still using older methods that won't support that. Some do support it, but generally you'll probably find that you need to use the MSI/EXE installer, rather than the MSIX installer, unless you are lucky with your choice of 3rd-party applications and choose one that knows how to deal with MSIX applications.

The capability is already provided. If you would prefer that each document start with a Layer, and with that Layer selected so new objects go into it automatically, you can accomplish that. Just make a Template, put it into the Templates folder you've configured in the application, and start new documents from the Template rather than using the New Document Presets.

Yes, it seems like a moderator should do that, and perhaps one will. Thanks for making the suggestion.

A couple of additional possibilities (or, at least, relevant points): One of your earlier screenshots shows that for "Followed Content" you have requested notifications via email, but not via the notifications list. That means that you would not see any sign of my reply (or other users' replies) to this topic when looking in the notifications list (the bell icon), as you would only get them via email. I have specified both forms of notification in my settings, so I always see them in the motivation list, too. One of the Serif staff mentioned to me that, as they understand the forum software, if you happen to have a browser window or tab open to the topic when a new post is made, you won't get an email. If that is correct, then if you had a tab/window open on that topic when I replied, you would not get an email. (However, this would not explain why @Alfred didn't get a notification for my post, without additional info/research.)

But just so you know: That Text Frame was on a document page, but it was inherited from a Master Page. The green-dotted line indicates that you've changed some aspects of the item, and hovering your mouse pointer over the name or object-type field in the Layers Panel should reveal what has been modified and unlinked from the parent. When working on a document page, to modify aspects of an item inherited from a Master Page (such as the item size or position) you need to use the Edit Detached function on the document page, or make the change on the Master Page (which would affect other document pages, too). Help for Edit Detached: https://affinity.help/publisher2/en-US.lproj/pages/Pages/detachLinkMasterPages.html

It's possible that you're Exporting in RGB-32 format when you really want to be exporting in RGB-8 format. If you're Developing RAW images that's especially easy to trigger accidentally, because prior to 2.4 Photo did not support 32-bit PNG files, and automatically exported them as 16- or 8-bit files. If that's happening to you, then you might want to take one of these approaches: Change your Develop Assistant Settings to Develop to RGB-16 rather than RGB-32 (In the Photo Settings, this will be under Assistant, then under Develop). or In the PNG Export options, change the Pixel Format setting from "Use Document Format" to RGB-8 or RGB-16 instead. You should be able to make your own Export Preset to do this, I think.