GarryP

From what I can understand of what has been said above, the problem seems to be one which could be unique to your machine/set-up/configuration (I can’t remember hearing about it happening for anyone else, with V1 or V2). If that is the case then I think it might be difficult for anyone else to replicate it and, as such, it might be difficult for anyone to be able to come up with a ‘fix’ for it beyond making a lot of guesses and hoping that something ‘sticks’. I wish you luck in finding a fix, not being able to use the software as expected must be frustrating, but, in my experience, very few people in the forums seem to be interested in finding fixes for software which is no longer supported by Serif.

The V1 applications are no longer getting updates, except for maybe some updates which help to keep the applications running due to operating system changes. Because of this, I think it is unlikely that this problem will be fixed in the V1 applications. Someone might be able to come up with a ‘work-around’, but if Serif couldn’t come up with an answer above then there might be nothing that you can do about it. (The last update to the V1 applications was, as far as I know, in November 2023 for some macOS start-up problems. I don’t know when the last update to the Windows versions was but I’m pretty sure it was before November 2023 because of the latest V1 application version numbers.)

Some Photoshop functionalities, for example various types of warp/fill, which are used in some PSD templates will not work in the Affinity applications when the Affinity applications don’t have the same functionalities. Opening a PSD in an Affinity application can be a case of ‘pot luck’ – it might work, but it cannot be guaranteed. P.S. The thread title “Template for a book” might give the wrong impression when people are searching for Affinity templates for a book. It might be better to rename the thread as “Book PSD mock-up doesn’t open as expected”, or something similar.

Searching the forums for external application reading file leads me to this thread: https://forum.affinity.serif.com/index.php?/topic/82148-constant-repeated-updating-file-message/ It is generally recommended that the documents that you open in the Affinity applications, and the resources which they use, are all stored on local drives.

Latest updates to what? What script? How does it "do" more fonts? You said you were having trouble with a “certain font” and “that font”. Are you having trouble with a particular font, or many fonts? The clearer the description of the problem, the better we can (hopefully) help you with it.

When you are having trouble with a particular font it’s a good idea to tell us what it’s called. (And when you know the name of the font you can search the forums for that font name to see if anyone else has already reported problems with it.) People who don’t have the necessary fonts installed will not be able to test the problem with your document because fonts aren’t included in Affinity documents. I’ve attached an image showing a list of the fonts which are used in the document, in case it helps anyone who can assist with this.

Related postings about the UI text size can be found here (and elsewhere in the forums):

I haven’t seen any evidence that the current situation regarding this will change any time soon, but I think Serif will need to do something about it at some point as more people move to higher resolution screens.

Once a thread has an official tag there’s no need to ‘bump’ it as it’s already acknowledged by Serif as an issue and they will (hopefully) get round to it as their priorities allow. I’ve seen no evidence that ‘bumping’ a thread makes any difference to Serif’s priorities so it’s probably not worth doing. Repeated ‘bumping’ could be interpreted as going against the forum guidelines, which could have 'consequences'.

Since the 2.6.3 commercial release is the same as the 2.6.3 beta you are probably better-off using the commercial release until a new beta comes out as the beta might expire at any time. If you have the same problem with the beta as with the commercial release then the problem should be reported in a non-beta section of the forums. The beta sections of the forums are for issues which only happen with the beta software and nowhere else. As for the answer to your question, have you tried to enter a value manually instead of using the slider? (I don’t use macOS, or have more than 16GB of RAM, so I can’t try this myself.) There’s a chance that the software might not be able to use more than 64GB for some technical reason but I can’t say either way.

You have posted this in a section of the forums related to the beta software only. If you are still using the latest beta software then you should look at upgrading the commercial software (already at V2.6.3) as the older beta software might expire soon. If you are not using the beta software then this should have been posted in the relevant non-beta section of the forums. No harm has been done, and a moderator can move this thread for you (if necessary) when you tell us which you are using.

I can see that having the Fields Panel might be useful in Designer, maybe not so much in Photo but I don’t use Fields enough to have a strong opinion about them. However, I don’t understand what the utility would be of having the Metadata Panel available in either Designer or Publisher, especially when a document has multiple Artboards or Pages. For instance, if I have multiple Artboards or Pages, what will the metadata refer to? How would the Title, Description, Keywords, etc. in that panel apply to different Artboards/Pages which could be used for different things? I think that would need way more thought put into it than I have done to get it to work reasonably well for most people. I’m not looking for a discussion about it, I don’t use either enough to care much about it, I just thought I’d mention a possible ‘speed bump’.

It doesn’t hurt to have many different ways to test things, but having some kind of ‘test plan’, as you say, would be useful on occasion. I would expect Serif to have these for their own testing purposes, so this isn’t the first time that I’m wondering if these could be made available in some (possibly cut-down) form for external testers to use. The information for beta testers has improved over time but there’s still not enough ‘meat on the bones’ in my opinion. Testers are getting more information about what can be done with new functionalities but there’s still not enough information about how they should be testing it or, just as importantly, what should/shouldn’t be happening under testing. Also, simply testing whether doing the right thing works as expected isn’t ‘proper’ testing in my opinion. Testers should have enough information to be able to know where the ‘fraying edges’ are so they can try and break things before commercial-release users get their hands on it. (I used to work somewhere – a large multi-national organisation – where the official ‘testing’ methodology consisted of running a sub-set copy of the live data through the modified system, and if the modified system didn’t break then it was good to release. This, of course, led to a somewhat sub-optimal experience for the users.)

Welcome to the forums @StrichcodeDE The small size of some text in the UI is something that has been reported as a problem for some people, especially those with high-resolution screens, and various suggestions have been made about it. See, for example:

Each new functionality or major change has its own thread in the “New Features and Improvements in X.Y Beta” section of the forums, with extra information being posted in the pinned threads in that section. The “Other New Bugs and Issues in the Betas” contains other issues that have arisen from testing and other things that testers might want to know about. Unfortunately however, there isn’t always much information for testers about how new functionalities should be used or what testers should expect by using them. If testers don’t know what should happen then it’s difficult to know if what’s happening should be happening, or whether they’re just not using it correctly. If this information were to be improved then the testing could be improved as people would know what they should be doing/seeing rather than guessing/assuming.

I don’t really know what you mean by that. You can switch it ON or OFF whenever you want to without waiting for anyone to tell you that it’s okay to do so. Hardware acceleration makes some functionalities faster but it’s not a requirement for using the software and plenty of people use the software without it. If you search the forums for RTX 4060 you will find various threads related to that card. One of those threads might give you the advice you need.

Have you tried switching it OFF? If so, did that make a difference? Which graphics card(s) do you have installed and are the drivers up-to-date?

Welcome to the forums @Snorlaxhk You have an Image Layer selected and you cannot paint directly onto an Image Layer. Two, of the various, things you can do are: rasterise the Image Layer to a Pixel Layer, or; create a new Pixel Layer to draw on (the Assistant can help you to do this automatically).

Welcome to the forums @zigger Can you explain what you think is wrong with it? You can enter a value including the unit of measure – e.g. 15pt or 10mm – in the numerical fields and the unit of measure can be independent of the document units.

Welcome to the forums @dwnylen This seems to be working as expected for me on Windows with 2.6.3. Your blue rectangle layer has its Visibility set to OFF in the Photo Persona Layers Panel. Setting “Make item visible” to ON for that layer in the Export Persona Layers Panel gives me a magenta result when exported (and also sets the Visibility to ON in the Photo Persona Layers Panel). If that’s not happening for you, or I have misunderstood the problem, would you be able to record and share a full-screen (whole application UI) video showing us what you are doing and what happens when you do it?

Problems with the Recent Files have been reported by various people using Sequoia. If you search the forums for recent sequoia you will find some threads which might help you to figure out what you can do. If none of the known ‘fixes’ work then, if you stay with V1, you might never see it fixed.

By “keywords”, do you mean the keywords in the image Metadata as can be seen in my attached image, or something else?

It is often better to show us a situation by giving us a document which contains the thing you are having a problem with. By doing so we are less dependent upon assumptions and language/description issues. If we are all working with exactly the same thing, rather than different individual interpretations of the situation, there should be fewer misunderstandings. (And, the act of creating an example document can often give a clue as to how the problem came about in the first place.)

I think it could be something to do with the PDF import process but it might be difficult to know for sure without having the PDF to try importing for ourselves.

You’re welcome. I couldn't replicate the problem you were having with “Copy items as SVG” switched ON but I’m glad that switching it OFF has got things working for you.