walt.farrell

I think what you are doing is Previewing the result. Now try and Generate the document. You should see the expected result. Preview only uses the first, or chosen 'record' to preview it.

Yes, but it's not flagging it as an incorrect font regardless. Also, as folks move their existing documents from static fonts to variable fonts, no doubt this 'user error in configuration' will come into consideration.

Thank you very much Walt. I am using latest Affinity.

You should be able to, but you may need to be using 2.4 or higher.

No. It will find about 352 references to related questions. It will not find "the answer", but only lead one into doing a bunch of research to find which (if any) of those results are actually relevant.

Yep, completely missed it...

Hi @ChasS,
What format are you exporting to?  I'm finding if exporting to PDF, then it defaults to Whole Document but exporting to a PNG or JPG allows me to export the selected artboard and I've gone right back to the first version of 2.0 and it was the same then.  Could you have been exporting to an image format before and now you are exporting to PDF?  For the preview issue, can you attach one of your files?
Mac is defaulting to the selected Artboard, so there is a difference.  This will need logging as it doesn't appear it already is.

Did you miss Ash's comment toward the end of the first post in this topic?
 

This is as good as it gets, when I lower the contrast, doesn't matter whether the lid is closed or internal display active. It's ok, but other apps are doing better. I switched now to dark UI.
Don't know why, can't add the image (error -200) I placed it here: https://www.100pro.ch/custom/APUI.png

Variable fonts
Apps: Affinity Designer, Affinity Photo, Affinity Publisher
Platforms: All
You're now able to use variable fonts in all Affinity apps, providing a plethora of new typographic design possibilities.
As well as providing predefined font styles, such as light, bold and condensed, variable fonts give you fine control of specific design aspects known as axes of variation, or just axes for short.
To try out variable fonts in Affinity, apply one to some text and then:
- On desktop, click the Font Variations button on the context toolbar (or on the Character Panel).
- On iPad, tap the arrow to the right of Bold/Italic/Underline/Strikethrough on the Text Panel and then tap Variations.
Variation settings on desktop.

 
 
Variation settings on iPad.

 
You'll see settings for each axis that the font designer has made individually adjustable.

Axis' slider being dragged.
Many variable fonts allow you to adjust their width and weight axes, and possibly italic, optical size and slant. These five axes are common enough that they're defined by the OpenType specification.
All manner of other axes may also be adjustable, such as:
- the height of ascenders and depth of descenders to better fit your chosen line spacing.
- the stem terminals, to choose between straight and swelling.
- the width of counters, which are enclosed and partially enclosed spaces within glyphs.
For examples of other possible axes, check out the axis definitions that are available for variable fonts at Google Fonts.
You may see fewer axes in Affinity than are mentioned by a font provider's marketing. For example, Google Fonts lists 13 axes for Roboto Flex and Affinity exposes five of them. This is because we respect font designers' ability to specify that an axis should be hidden. This is part of the OpenType specification and means that software isn't meant to provide an interface for such axes.
Why would a designer do this? Well, a variable font might adjust an axis internally based on your choices for other axes that you can directly adjust. For example, observe how counter widths change when the weight axis is adjusted in the animation above.

Variable fonts and PDFs
PDF doesn't support variable fonts. So, when you export a PDF of an Affinity document that uses a variable font, we create a static instance of the font with fixed settings.
We've taken steps to ensure static instances of fonts are well named. You should find this minimises the need to identify the original variable fonts if you later import or place the resulting PDFs.

I tried that a couple of days ago, and found weird behavior on. Windows in V1 and V2.
I drew a curve with the Pencil Tool, then drew a second curve with the Pencil Tool. While drawing that second curve I pressed Ctrl to make the nodes visible so I could adjust them, and the nodes of the first curve highlighted. I haven't finished experimenting with that yet, nor posted it as a bug, but it seems weird.

My experience is that there will always be intermediate tones besides those specified in the Gradient Map adjustment. The stray tones can especially be seen when using color images. In context of black and white images this does not normally show, so if exact number of levels is not important (and it often is not, as images are normally not viewed at pixel level), the shown methods would be fine (though setting up a kind of accurate stepwise gradient is rather tedious). In low-resolution images, sporadic intermediate tones, even grayscale, are of course more easily discernible.

intermediatetones.mp4  

The first thing I would do is open Task Manager and confirm there are no instances of Affinity V2 apps stuck in the background. 
If there are none, and if a Windows Restart doesn't resolve it, then I would check this post from the FAQ: 
 
 

Welcome to the forums, Kristy.
These forums are solely for discussions about the Affinity software suite, so inquiries about other topics are not appropriate here. I'm afraid you'll need to find another place for your question, one more related to AI usage in general.
A moderator will probably lock this topic soon.

OK, I did some more indepth investigation on this.
1) it only seems to be visible with certain "Moiree" (in this case the jacket garment)
2) Using the same picture in the same area ist does happen with 2.4.1 as well.
3) Performance settings are the same in both versions
4) And it seems to be a redraw issue. Hovering on the same spot for a little longer makes this effect disappear again
Therefor I assume it's not an Beta issue - I just got aware of this under the given "unlucky" circumstances ...

Thanks for the added details.
That is probably due to the 1.7 bug that forces resampling, combined with the macro-processors by-design behavior that records the final height & width from the image you're using to record the macro. That means you have to use Filters > Distort > Equations to perform image resizing in a macro.

A little smaller for me (using 2.5 beta), but interesting. Thanks.

Sorry, there was a problem launching the application.
 
Cannot communicate with other Affinity apps. Please ensure the app is up-to-date and that your firewall isn't blocking local network traffic. 
 
I disabled the firewall and still got the same message on all 3 programs.

If you look back at the 2nd post in this topic you'll see a list of the bugs they've logged for it, which will give you some information:
 

I'm curious why you're sharing it as a .psd rather than an Affinity format such as .afphoto.
But for an exported format, "TIFF with Affinity Layers" or PSD may be the only choices.

walt.farrell, you are my hero of the day, no, of the week! How blind was I to miss the delimiter selection option?!?!?!?!?

Well, Windows updates are known to cause problems on occasion, so that could be it I suppose.
If you're getting crash reports Serif may want to see them. They can provide an upload link or you could post them here if you're comfortable doing that.

Can you create/share a sample .afpub file that does this, and a PDF exported from it, that we could examine?

Yep…same issue in OneDrive.

In the Data Merge Manager you can specify the separator you want to use:

 
But using LibreOffice Calc, I have no problem generating a CSV file whose fields contain the "," character, and which uses the ";" as the separator. And as mentioned above, any fields that contain a "," are automatically quoted. And the file works properly for Data Merge.
Samples (using Publisher 2.5.0.2402, but should open in Publisher 2.4):
data-merge-test.afpub Untitled 2.csv