Patrick Connor

Our official answer is here, so no this issue discussed will not appear in a 1.10.x fix

From the release notes, this thread benefitted from this change App crash upon startup caused by a deleted "Recently Used" file on Catalina

None, they're the same. 2.0.4.326 is the build number of the release codenamed 2.0.4 There is only ever one release called 2.0.3, one release called 2.0.4, one 2.0.5. However it takes a number of distinct internal beta builds of 2.0.4 till we get to the actual release. So betas called 2.0.4.xya .xyb .xyc are made and the final one is the release build. Then we start starting work on 2.0.5.xyd (or we could call it 2.1.0.xyd if we add new features too)

None, they're the same. 2.0.4.326 is the build number of the release codenamed 2.0.4 There is only ever one release called 2.0.3, one release called 2.0.4, one 2.0.5. However it takes a number of distinct internal beta builds of 2.0.4 till we get to the actual release. So betas called 2.0.4.xya .xyb .xyc are made and the final one is the release build. Then we start starting work on 2.0.5.xyd (or we could call it 2.1.0.xyd if we add new features too)

@sagar1412 Welcome to the Serif Affinity forums. Low resolution images are loaded initially, and this can happen on larger documents if exported shortly after opening the file. Have you tried viewing each page before export or even just leaving the computer for a few minutes first before export, as it allows the background task manager to import higher resolution images before export. If that doesn't work please show which export settings you are using

All builds before 2.0.3 treated the bottom field correctly. 2.0.4 has gone back to being correct. If you used 2.0.3 where the number was reversed and got the visual effect you wanted, then you will have to put the field back to a real value (like it should have been) sorry for the inconvenience

There are 2 problems reported in this thread. Sorry I was referring to the crash on startup, not the SVG import problem, which has not been addressed. Sorry for the confusion

I don't think this announcement post is the correct place to discuss specific, but please note 2.x will start a new round of customer betas where the developers are already fixing another tranch of reported issues. We're planning that will be with you soon

Serif will not make V1 apps unavailable to those who bought it. It's a real shame that their standard search is only for live products and doesn't produce different results for owners than non-owners because it looks like the apps have been deleted, but that is the decision that Apple have taken probably for speed and caching reasons. Searching purchased products seems to be the solution for most.

Try now It's 1 week currently for most members, as that is the average time a thread stays relevant and thus monitored for subsequent editting that introduces spam. It's not a science but that number has worked for us. (Also try now)

When you've made 500 posts you are (automatically) elevated to a group that allows a larger forum attachment limit. I made a decision that those people are unlikely to be spammers (or get cross and go back to trash all their old posts, as has been known) so that experienced group can edit any post they ever made with no time limit. The advantage is that I stopped getting personal requests to edit other forum users posts to correct information that had become out of date, (but in editing it did not make a mockery of subsequent historical replies) tldr; forum moderation is a delicate balance and you cannot please everyone and have little to no spam

Thanks I'll get that sorted

Because most people suffering from it are unwilling or unable to share their book with us to replicate the problems. The offer to investigate then delete the files is rarely taken up unfortunately

A customer has put together their thoughts on this here We don't believe there to be significant differences (though some are side by side performance testing at the moment). The main reason is for larger companies who cannot distribute MSIX yet, and have asked for traditional installs for their networks and processes. The software will function near identically with either.

@sansnom (and @Seneca) the announcement post is not the best place to discuss individual problems so I have branched your discussion into your original thread. I will have someone see if they have any suggestions for you next week. In the meantime, sorry for the difficulties you seem to be experiencing, they aren't generally true for all users in terms of having to load presets each time, so hopefully a solution can be found.

@wim Sorry, you are correct, the slider issue was not part of the crash fix that I posted about. I will notify the UI team

I will get this thread addressed again next week, sorry @sfriedberg

@kcbdr Welcome to the Serif Affinity forums Sorry but no, the V1 Affinity software is no longer sold on any platform

Sorry that you have experienced this problem with the 2.0.3 release of the Affinity Suite. We have now released 2.0.4 on all platforms, and using that build this problem no longer occurs.

That's thoughtful, but Tim Is the Senior Software Developer responsible for this feature, and he thought it may be worth his time ! I will get you a private upload link for us to look

You should have been asked when you started the application if you want to update, where you can say no, and will update quickly and smoothly if you press Update. Our applications do not update without you being asked UNLESS you bought from the Microsoft Store (and MS do not give you a choice about being on the latest version)

The 2.0.4 release notes answer this I think. What would you like to know ?

Sorry that you have experienced this problem with the Affinity Suite. We have now released 2.0.4 on all platforms, and using that build we believe this problem no longer occurs.

Sorry that you have experienced this problem with the Affinity Suite. We have now released 2.0.4 on all platforms, and using that build we believe this problem no longer occurs.

Sorry that you have experienced this problem with the Affinity Suite. We have now released 2.0.4 on all platforms, and using that build we believe we have made an improvement in that area that should have fixed the crash