Jump to content

Affinity Publisher Customer Beta - 1.10.0.1115 (RC)


Recommended Posts

  • Moderators

Status: Release Candidate
Purpose: Fixes and Improvements
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.0.1115 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.

Due to current and anticipated changes to help with performance issues this version is now 1.10.0 and replaces the previous 1.9.4 beta. All previous changes from 1.9.4 have been rolled into this beta.

As such, we strongly recommend that you do not use this beta for real work as data could be lost and the files you save are not guaranteed to open in previous / future versions of Affinity Designer.

---

  • Prevented unnecessary duplication of placed documents on IDML import
  • Fixed issues with documents that have large numbers of embedded documents failing to load
    • (The maximum number of allowed open file handles was being exceeded leading to erroneous 'Future Version Error')
  • Improved OpenAsset support
  • Localisation updates
  • Help updates

Previous 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

Link to comment
Share on other sites

1 hour ago, AdamW said:
  • Localisation updates

 

The numerous and appalling misinterpretations of French translations, repeatedly pointed out here by many contributors, have not been rectified at all.

6 cœurs, 12 processus - Windows 11 pro - 4K - DirectX 12 - Suite universelle Affinity (Affinity  Publisher, Affinity Designer, Affinity Photo).

Mais je vous le demande, peut-on imaginer une police sans sérifs ?

Link to comment
Share on other sites

19 minutes ago, GarryP said:

That issue was only reported on Sunday and a crash report was given less than 24 hours ago.
How long do you think it takes to bug-fix complex applications?

I only inform that there is a problem. If you think that better release a stable version with this bug, please.

Link to comment
Share on other sites

That problem was officially logged with the developers a few minutes ago so they now know about it.
Until then it wasn’t definite that it was an Affinity software problem.
They can’t do anything about it until they know it’s really a problem with the software.
They will either fix it before the next commercial release or they won’t. All we can do is wait and see.

Link to comment
Share on other sites

On latest Window 11 version, when you open a file via menu File => Open, there is no way you can click and choose the file to open, it is there but you can do nothing except  click the X button - the only available Click-able item on the open dialog- to close the Open-Window. The only way to open file to use is drag it directly from the Window  explorer to open it, very annoying but it works. Both official and beta version have the same problem on Window 11 (exactly 11, not 10).

Link to comment
Share on other sites

20 hours ago, Tuan Tran Anh said:

On latest Window 11 version

 

From Tech Specs:
Screenshot_2021-07-22-23-39-46.png.6edd284e9733ac27c6cbee7f5732613c.png

Affinity Store: Affinity Suite (ADe, APh, APu) 1.10.5.1342, 2.0.0.
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 22H2, Build 22621.1105.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 10 Pro, Version 21H1, Build 19043.2130.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

@GarryP If you developer why you only saw this my message and did not see the other 10, to which I am waiting for a response. They may also contain errors. And I've been waiting for weeks. You should be thankful that I spend my time helping to find bugs and make the program better, not blaming me for finding a bug.

Link to comment
Share on other sites

1 hour ago, anto said:

If you developer

@GarryP is a user, like you and I. If he were an Affinity Developer then you would see a "Staff" badge and a "Moderators" notation next to his postings (if you're using a wide-enough browser screen) as you can see in Adam's post at the top of this topic, or his username in red if your screen is not wide enough.

image.png.b209b278ce711d1721260d7ab7ed8f3e.png
 

Garry knows that the bug he mentioned was registered with the Developers by reading the forums, and seeing what the Staff members have said.

-- Walt

Desktop:  Windows 11 Home, version 21H2 (22000.613) 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 
Laptop:  Windows 10 Home, version 21H2 (19044.1706) 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
        Affinity Photo 1.10.6 (.1665) and 2.0.4  and 2.1.0.1709 beta/ Affinity Designer 1.10.6 (.1665)  and 2.0.4  and 2.1.0.1709 beta / Affinity Publisher 1.10.6 (.1665)  and 2.0.4  and 2.1.0.1709 beta
iPad Pro M1, 12.9", iPadOS 16.3.1, Apple Pencil 2, Magic Keyboard

      Affinity Photo 1.10.7 and 2.0.4 and 2.1.0.1713 beta/ Affinity Designer 1.10.7 and 2.0.4 and 2.1.0.1713 beta/ Affinity Publisher 2.0.4 and 2.1.0.1709 beta

Link to comment
Share on other sites

12 minutes ago, walt.farrell said:

@GarryP is a user, like you and I. If he were an Affinity Developer then you would see a "Staff" badge and a "Moderators" notation next to his postings (if you're using a wide-enough browser screen) as you can see in Adam's post at the top of this topic, or his username in red if your screen is not wide enough.

image.png.b209b278ce711d1721260d7ab7ed8f3e.png
 

Garry knows that the bug he mentioned was registered with the Developers by reading the forums, and seeing what the Staff members have said.

@walt.farrell you are great man, always ready to answer and help)

Link to comment
Share on other sites

2 hours ago, anto said:

not blaming me for finding a bug.

I don't know what your problem is, but Garry just points out that reminding and "urging" the unrepaired bug that was reported a few days ago is relatively unnecessary - it simply couldn't be fixed in such a short period of time.

Affinity Store: Affinity Suite (ADe, APh, APu) 1.10.5.1342, 2.0.0.
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 22H2, Build 22621.1105.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 10 Pro, Version 21H1, Build 19043.2130.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

52 minutes ago, Pšenda said:

I don't know what your problem is, but Garry just points out that reminding and "urging" the unrepaired bug that was reported a few days ago is relatively unnecessary - it simply couldn't be fixed in such a short period of time.

If he is not a developer, he has no right to write such comments:

 

On 7/21/2021 at 2:59 PM, GarryP said:

They will either fix it before the next commercial release or they won’t.

If the error is really grave and leads to program's crash, you can not release a stable version. Otherwise, the program will turn into a continuous bugs. See how many mistakes (well, not so serious) still haven't been fixed for years. But that's another story.

Sorry for offtopic.

Link to comment
Share on other sites

21 hours ago, Tuan Tran Anh said:

On latest Window 11 version, when you open a file via menu File => Open, there is no way you can click and choose the file to open, it is there but you can do nothing except  click the X button - the only available Click-able item on the open dialog- to close the Open-Window. The only way to open file to use is drag it directly from the Window  explorer to open it, very annoying but it works. Both official and beta version have the same problem on Window 11 (exactly 11, not 10).

I'm using the latest version of Windows 11 and everything works fine so far, including opening files.

-- Window 11 - 32 gb - Intel I7 - 8700 - NVIDIA GeForce GTX 1060
-- iPad Pro 2020 - 12,9 - 256 gb - Apple Pencil 2 -- iPad 9th gen 256 gb - Apple Pencil 1

Link to comment
Share on other sites

44 minutes ago, anto said:

If he is not a developer, he has no right to write such comments:

I don’t believe that I made any false statements and I think I was being quite reasonable in asking the question I asked.
What is it that you were particularly offended by? Maybe I accidentally said something the wrong way.

45 minutes ago, anto said:

If the error is really grave and leads to program's crash, you can not release a stable version.

Pretty much all software ships with some known bugs in it – sometimes you just have to get stuff ‘out of the door’.

45 minutes ago, anto said:

See how many mistakes (well, not so serious) still haven't been fixed for years.

Since you were aware of the other bugs, why did you not also mention these when you mentioned the bug you reported?
Is there something about the bug you reported which makes it more important than the other bugs?

Link to comment
Share on other sites

51 minutes ago, GarryP said:

Is there something about the bug you reported which makes it more important than the other bugs?

You can see all my posts. You did not write any answer there.

Other errors do not lead to program's crash and can still be tolerated for several years. I remind about it periodically.

I want the program be high quality as soon as possible.

 

51 minutes ago, GarryP said:

Pretty much all software ships with some known bugs in it

What are we talking about? I have already read this phrase somewhere in forum. This is not a solution, this is an excuse. That's why so many testers (exclude me, i do it only from time to time) works and inform about bugs to prevent errors.

.

Link to comment
Share on other sites

14 minutes ago, anto said:

You can see all my posts. You did not write any answer there.

No one is obligated (except possibly Serif Staff) to answer your posts. Those of us who are not Serif Staff will answer when we know an answer, or want to be helpful by soliciting more information to clarify a problem, or have a suggestion for a workaround that might work.

Serif Staff try to respond to all the problem reports and questions, unless they've been adequately answered by the community, but they are very busy and many users (not just you, or I, or Garry) are asking questions and reporting problems. Serif uses a tracking system to track and prioritize which topics they respond to, though only they know all the details of that process. They also prioritize which bugs they fix, and only they have the details for that.

It will help if you have some patience, both in how fast you expect answers and how fast you expect fixes. That, of course, applies to all of us: it's good for each of us to remember that we are are just one user among many, and Serif is trying to (first) deal with the issues that impact the largest number of users when fixing bugs.

34 minutes ago, anto said:

I want the program be high quality as soon as possible.

So do all of us, including Serif. But there are many factors that influence how fast each bug can be fixed, and which contribute to Serif's decisions on when to fix each one.

-- Walt

Desktop:  Windows 11 Home, version 21H2 (22000.613) 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 
Laptop:  Windows 10 Home, version 21H2 (19044.1706) 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
        Affinity Photo 1.10.6 (.1665) and 2.0.4  and 2.1.0.1709 beta/ Affinity Designer 1.10.6 (.1665)  and 2.0.4  and 2.1.0.1709 beta / Affinity Publisher 1.10.6 (.1665)  and 2.0.4  and 2.1.0.1709 beta
iPad Pro M1, 12.9", iPadOS 16.3.1, Apple Pencil 2, Magic Keyboard

      Affinity Photo 1.10.7 and 2.0.4 and 2.1.0.1713 beta/ Affinity Designer 1.10.7 and 2.0.4 and 2.1.0.1713 beta/ Affinity Publisher 2.0.4 and 2.1.0.1709 beta

Link to comment
Share on other sites

19 minutes ago, walt.farrell said:

So do all of us, including Serif. But there are many factors that influence how fast each bug can be fixed, and which contribute to Serif's decisions on when to fix each one.

That's why no GarryP, no you and I do not have any rights and permission to make any predictions instead of Serif. Not knowing who Garry was, I attributed this answer to Serif. And it affects their reputation. Each negative comment.

Link to comment
Share on other sites

50 minutes ago, anto said:

I want the program be high quality as soon as possible.

Yes, that's perfectly fine, I think most user want it.
But I don't think it's okay to feel offended and concerned that the bug, that was reported 3 hours after the beta release, was "still" not fixed. And that's what Garry mentioned - nothing else.

Repeating and constantly reminding you of already reported errors will certainly not help to eliminate them.
A different situation would occur if the beta release stated that the bug had already been fixed - then, of course, re-reporting the bug is justified.

Affinity Store: Affinity Suite (ADe, APh, APu) 1.10.5.1342, 2.0.0.
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 22H2, Build 22621.1105.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 10 Pro, Version 21H1, Build 19043.2130.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

Please see  attached screenshot of how weird  get the fonts even using Arial font, please help.. I'm using Mac computer 

this in on Affinity design , already uninstalled and reinstalled the programs and still do it .. please help   

Screen Shot 2021-07-23 at 2.56.33 PM.png

Link to comment
Share on other sites

5 minutes ago, Sam18 said:

 

Please see  attached screenshot of how weird  get the fonts even using Arial font, please help.. I'm using Mac computer 

this in on Affinity design , already uninstalled and reinstalled the programs and still do it .. please help   

Screen Shot 2021-07-23 at 2.56.33 PM.png

Answered in the other topic you posted.

 

-- Walt

Desktop:  Windows 11 Home, version 21H2 (22000.613) 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 
Laptop:  Windows 10 Home, version 21H2 (19044.1706) 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
        Affinity Photo 1.10.6 (.1665) and 2.0.4  and 2.1.0.1709 beta/ Affinity Designer 1.10.6 (.1665)  and 2.0.4  and 2.1.0.1709 beta / Affinity Publisher 1.10.6 (.1665)  and 2.0.4  and 2.1.0.1709 beta
iPad Pro M1, 12.9", iPadOS 16.3.1, Apple Pencil 2, Magic Keyboard

      Affinity Photo 1.10.7 and 2.0.4 and 2.1.0.1713 beta/ Affinity Designer 1.10.7 and 2.0.4 and 2.1.0.1713 beta/ Affinity Publisher 2.0.4 and 2.1.0.1709 beta

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.