Jay1991

Looking at the application marker for the file, FF D8 FF E1, reveals it's actually an Exif file using the Motorola type byte align, MM.
"The Exif file format is the same as the JPEG file format. Exif inserts some image/digicam information data and a thumbnail image for JPEG conformity with the JPEG specification. Therefore you can view Exif format image files using JPEG-compliant Internet browser/Picture viewer/Photo retouching software etc., as usual, JPEG image files."
Exif uses the TIFF 6.0 format to store data which likely explains how the file contains multiple layers.

The problem was in the bottom mask. Turn that off and the picture shows correctly in Affinity. That is a renamed file that has layers which JPG files do not
So other simple viewers do not see the layers but Affinity does

Sure, here you go. Thanks
2024_TX_500h_FSPORT_Exterior_004.zip
Edit: I also noticed if you hover over the image in my previous message, you can see the source of it. Or better yet you can just right click and open the link to get it directly from the lexus website

Try this: Download it to your machine, as you did to load it into your Affinity app. Zip it. Upload the .zip file.

Interesting how there are masks in a JPEG file. Turn them off.

 

Version 1.8 of OpenType was released in 2016, it included Variable fonts. The feature is mature and widely used nowadays. 
It would be great to have support for variable fonts. 

I get that not every feature can be implemented. And there has to be concessions made in places, and that affinity isn't a huge company yet.
But the fact that there STILL isn't any sort of .dds support at this point is crazy considering just how common that file type is in 3d applications. I bought Photo 2, but still find myself using photoshop more purely because I can work with the format I need to work with in photoshop through a plugin.
 
There doesn't even need to be native support. If the intel or nvidia plugin for photoshop could be used on photo that would fix the issue perfectly. It's just the fact that there's NO support for .dds files that makes it very hard to actually switch.
 
This isn't a new request either, I've seen people asking for this since 2018. I get that it isn't a very glamorous or advertiser friendly feature. But Photoshop got its userbase by unfortunately being the best option available, and being the best option means working for as many people as possible in as many situations as possible.
 
Basically, in short. We need .dds support, it's necessary at this point, whether that be through supporting existing plugins or adding native support is irrelevant.

Hi All,
Well, it’s been a pretty crazy week since the launch of V2!
This has been a real labour of love for us over the last year or so, and I can’t even begin to describe how hard the development team have worked on it. Not only getting the V2 apps launched, but also of course finally bringing Publisher to iPad. 
With this being our first paid-for upgrade there has understandably been a lot of feedback / questions around future updates and our pricing policies. I thought it was worth addressing / clarifying our position on some of these personally...
Updates to V2 moving forward
Buying V2 not only gets you all the new features you have seen, but we have various updates planned – including many more new features and improvements – which you will get for free. This will continue until such a time that V3 is released. We’re not sure exactly when V3 will be, but I can confirm we are not going to move to anything as regular as an annual upgrade cycle as has been speculated.
It’s worth saying too that V2 does include many under-the-hood changes to our underlying technology, and we have also been investing in several new areas of research recently. Some of these haven’t manifested themselves into new features yet, but overall V2 does give us a better platform to develop on moving forward and I’m sure you will be pleased with the updates V2 will receive.
Updates to V1 moving forward
While we did say on the FAQ that V1 would no longer receive any updates, I want to clarify that was about new feature updates. We will be updating V1 to fix any critical problems caused by operating system updates in the future. So if the next version of macOS breaks V1 we will endeavour to fix it. There will be a point in time when continuing to maintain V1 in this way will not be tenable, but certainly for the foreseeable future we will continue to patch. In fact, we have an update to V1 queued up for release very shortly with some fixes for Ventura and issues caused by a recent Windows security / quality update. 
We will update our FAQ shortly to make that clearer for everyone.
Offer period
In case you didn’t see, I’m pleased to confirm we have decided to run this initial launch offer until 14th December to give everyone the best chance possible to get it if they wish / have a decent amount of time to trial it. 
Upgrade pricing
It’s been really hard to see some of the comments about us not looking after our existing customers – we’re pretty devasted that anyone feels like that to be honest. But the fact is we felt our hands were tied somewhat with being able to offer upgrade pricing in a fair way. The main reason for this was App Store customers (which make up around 35% of our userbase). The problems with that are two-fold: firstly, we didn’t have a way from within V1 to validate an App Store purchase receipt to reliably ensure customers who were entitled to an upgrade could get one; and secondly, we could not find a good way for people to get that discount via the App Store. Us pushing upgrade customers to go exclusively via our own site (including customers who were previously acquired via the app stores) may also have put us in violation of App Store Ts & Cs which we were obviously concerned about.
I’m not saying that these issues were completely insurmountable, but any solutions we came up with would be messy, and most importantly could have resulted in some bona fide V1 customers struggling to get validated and claim their discount. We certainly don’t have the support resource here if we ended up needing to manually validate tens of thousands of receipts for example.
The only option we felt was safe to move forward with was a general launch offer, which would guarantee that every V1 customer could get the discount, whether they purchased directly through us or the App Stores. We knew a side effect of that would mean some new customers would end up receiving that same discount – but we felt that was a better option than V1 customers missing out. It’s also worth saying that while there has been some good press about V2, all our main marketing has been via email and through social media to our followers. In other words, we felt ok about it because we knew the vast majority of people who would find out about it or take advantage of the offer would be existing customers. I would be surprised if over the offer period customers upgrading from V1 didn’t make up more than 90% of our sales.
Overall I do believe us giving a 40% discount, along with the addition of the new Universal Licence of course, is offering fantastic value for money for those who want to upgrade. 
However, taking on board some of the feedback there is something extra we can do – we will offer a new free bundle of content exclusively for V1 customers upgrading to V2 as an extra thank you for your support. I’ve seen this suggested by a number of customers and it’s a great idea as it does remove the App Store conflict entirely. 
We’ll need a little time to put something together, but all customers who previously registered or purchased V1 and have since upgraded to V2 will receive a voucher code for this via email as soon as we can.
A comment on no subscription
I do want to say that some of the points above are exactly the reason why software companies move to subscription. Whatever you do with upgrade pricing, you still have the issue of customers who bought the previous version 3 months ago vs. those who have had it 2+ years. Offering perpetual licences also gives the additional overhead of needing to maintain the previous version longer than you would if everyone was on subscription / generally always on the latest version.
We are a small team so some of these complications are not ideal — all we really want to do is focus on developing our latest codebase, push out regular updates and continue with our mission to make great creative software accessible to everyone. 
But it does need to be funded somehow. We know you love our no-subscription model, but there also needs to be a level of appreciation that the alternative is having paid-for upgrades from time to time. That unfortunately comes with its own problems.
All of that said, I have to say we have been blown away with the response to V2 - around 3 times as many people have upgraded in the last week than we expected - and we really can't thank you enough for the support you have shown. More than anything the success of this upgrade puts us in a great place to continue investing heavily in development which is ultimately what it's all about, and we’re super excited to crack on with some great updates coming next year!
All the best,
Ash

No, version 2 of the Affinity suite will be a one off purchase (perpetual license) and will not be sold as a subscription service (monthly or otherwise)

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
Added 'Select Parent', 'Select Top', and 'Select Bottom' to main menu Changed behaviour of Select All when Edit All Layers is disabled - if you’re inside a group, it will now Select All within the group Fixed PDF passthrough getting rasterised if vector cropped  Previous release notes

That statement does not seem true to me and certainly not fair to Serif.  It's perfectly reasonable for them to be extremely cautious in their decision-making with regard to possibly developing for another platform and then having to support it.  It would also be perfectly reasonable for them to say they won't make a Linux version because they simply don't want to.  That's their prerogative.   All we can do is continue to make it known that we want it and are willing to pay for it.

Ideological zealots are problematic regardless of subject, my point is the Linux community is not filled with zealots. We are pro Open Source of course but pro open source does not equal anti-commercial.
I don't see where there is a PR nightmare possibility. They get good PR from letting us prove ourselves and if it fails they get good PR for at least giving us the chance. It sounds like they are worried about having their software compared to the jank stuff that is on Kickstarter and other services that are just scammy nonsense. They don't want a guilty by association outcome is what I think creates the hesitation.
However, there have been thousands of successful campaigns from reputable companies, otherwise those sites would have never worked and wouldnt still exist.
Ultimately, the only people who are doing ANY RISK at all is me and the Linux community. I am risking my reputation to promote a crowdfunding campaign that I have hope that it would work but no evidence that it would or not. The Linux community would be risking future companies using a failed crowdfunding campaign as a metric for not considering a Linux port of their software.
Serif is at risk of basically nothing if they handle it well and especially if they partner with me to promote the campaign.
I am willing to risk my reputation for proving the Linux ecosystem is strong enough to justify it if the company is behind the effort to find out. . . I am not willing to risk my reputation on a "maybe if this then we might consider thinking about it".

Exactly that. And that's exactly why apps and games aren't flocking to the Linux desktop. Because we just don't know if we will make any money at all from it. Let alone cover the initial costs of development.
People need to realise that yes, FOSS can be great, but often these projects need massive sponsorship to be successful. Relying on 1 or 2 developers using their spare time in the evenings to make a competing app isn't going to deliver the kind of quality that you would expect from a piece of proprietary software. And then you have to consider product support, documentation etc...

I disagree, if anything what I got from that comment is that some people want to pay for things, as long as they're FOSS because when the company fails, at least people will be able to learn from the available code of the FOSS app, instead of starting from scratch. That doesn't mean that they represent the entire userbase. I think this is something that should be discussed with someone like Black Magic Design, who offers a paid studio version of DaVinci Resolve, and see what their numbers are in terms of people who pay for the studio version on linux, people who use the free version and how those numbers compare with the Windows numbers. They're probably in the best place in the market to give Serif advice on this, since video editing and graphic design are similar industries with a lot of crossover.
As far as gaming goes, it's an entirely different beast from a design app, there's way less stuff going on behind the scenes and to be fair, most game developers either use an in-house engine, which they spent years developing because it's such a huge beast to manage and they haven't planned for linux ahead of time, or they use one of the existing Unreal Engine & Unity engines and either don't know enough about the linux market or don't have the capacity to export to linux. Or I guess there could also be the case they just don't care about Linux, or are entirely reliant on steam's Proton development which makes most games playable on linux. Sadly, Affinity does not have that benefit, Proton doesn't work on Affinity and even this attempt to get Serif to work with CodeWeaver seems to be a "oh let them contact us first" as if it's CodeWeaver themselves who would benefit from this, not you who'd get access to an entirely new market at the price of... a few hours of e-mailing?
Also, Mark, for the same reasons you mentioned you could say "oh people use free browsers, play free games and use free apps like inkscape, figma, gimp, photoshop online and others on windows, we don't know if we will make any money at all from it." and yet you did. I hope you can see how this sort of statement can appear biased to someone like me when there are a multitude of other better reasons to make the jump.

Ever since I bought the three products, I noticed that I've been constantly updating Designer, Photo, and Publisher quite often when I open these programs, mainly because I seldom use these programs. This has become tedious for me to go to the download webpage and download the latest version, for each program. Hence, my recommendation.
Is it possible for you to create an updater that downloads and installs the programs automatically without having me go to the website each time an update is released? I wouldn't mind how this is implement as long as I don't need to go the website.
P.S. On that note, why is there a separate page for each program for these installers no less?

Click here to download the latest beta
Status: Customer Beta
Purpose: Features, Improvements, 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.
Fixes
Fixed crash when dragging items in the Layers control Improved performance of PDF import (~40% faster) Improved performance of text when rendering text Fixed vector export of text occasionally filling characters Fixed crash when closing floating document  Fixed New Document dialog previous document selection highlight not being remembered Fixed Ctrl+M with nodes selected to not bring up the curves dialog  Fixed crash when docking a panel with the Brushes panel Fixed crash with Appearance panel after using Ctrl+Z on vector brush input  Fixed PNG export not displaying the size warning if the export dialog was previously closed with a different preset  [Installer] Added MSI error strings to installer results page to help diagnose problems 1.8.3.641 release notes

We are pleased to announce an update for the Windows release of Affinity Designer, version 1.8.3
Changes in this Build
The changes in Affinity Designer for Windows 1.8.3 (over the last release Affinity Designer for Windows 1.8.2) are as follows:
Fixes & Improvements:
Fixed layers getting clipped to embedded documents would not get clipped Further boolean operation improvements  Tweaks to Alignment Fixed line caps on strokes with pressure profiles that have sharp pressure changes at the start getting incorrectly expanded Fixed loss of selection scope when deleting objects Improved boolean operations on large shapes Fixed PDF export failing due to colour profile being rejected wrongly Fixed rendering artefacts with small radius filter effects Fixed PDF export to honour gradient map's colour space Fix for autosave/recover not working on anything but new documents. Fixed crash opening empty (0 Kb) files Fixed PDF export failing with embedded LAB document Fixed PDF export of images to preserve their colour space Fixed PDF export failing when a document contains an empty clip Fixed cropped result when creating a selection from a mask Fixed sporadic selection failure when invert selecting with Move tool Fixed sporadic PSD import crash Fixed floating panels being clipped when collapsed  Help and Localisation improvements. Earlier changes and fixes in 1.8 since 1.7 (including the new 1.8 features) are listed in some detail in this 1.8.0 update announcement and this 1.8.2 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.

Hello,
I recently noticed that version 1.8 presents a user interface that is difficult to understand about (new) document formats.
Here I present a proposal about the user interface and would like your feedback.
Thanks

Thanks

I have designer friends that are using Illustrator, and upon showing them AF Designer, almost every one dismiss it due to the lack of Offset paths, Patterns, Blends and Gradient meshes (in that order!) 

Click here to download the latest beta
Status: Customer Beta
Purpose: Features, Improvements, 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.
Fixes
Fixed loss of selection scope when deleting objects Improved boolean operations on large shapes Fixed PDF export failing due to colour profile being rejected wrongly Fixed rendering artefacts with small radius filter effects 1.8.3.623 release notes

I'm afraid that there are still bugs in the expand stroke function.

Pentagon with stroke width 10pt expands correctly, but increase the stroke to 14pt and an extra node appears.
Have noticed other shapes generating unwanted nodes on perfectly straight edges… Star, trapezoid, diamond etc.
 

Click here to download the latest beta
Status: Customer Beta
Purpose: Features, Improvements, 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.
Fixes
Allow PSD smart object support  Fixed crash when switching between artboards with Appearance panel visible Fixed New Document dialog Presets bar incorrectly hidden when switching between Templates and Presets Fixed New Document dialog Template folders with a '.' cutting off subsequent characters  Fixed several boolean operations and expand stroke issues on simple geometry or compound objects Fixed unable to paste text into editors after receiving tab focus Fixed New Documents dialog allowing minus values in Document Size, Margins and Bleed  Improved performance of Layers Panel when updating previews of Artistic Text Fixed input lag (500ms) when drawing with a pen using Windows Ink Improved text responsiveness 1.8.1.595 release notes

I, too, did some testing of the 'new and improved' Expand Stroke feature and this seems to be a very big improvement. Congratulations! I am sure some of the glitches (see above @Aammppaa's post) can be ironed out.
Here are some of my test results (please note: under each of the blue objects there is an original unexpanded object in bright orange colour. Nowhere you see any of it bleed throug).

 

 

 

 
d.