ashf

Tell me about it! It drives me nuts! And no, it works the same way in version 2. At least they could give us an option in the settings to disable this stupid thing. Not sure why the developers are so hardheaded!?

This should now be fixed in the latest update which we pushed last night (2.0.3) - you can get that from the App Store now...

If you are on iPad, bring the artwork to Vectornator with a PDF or SVG, then export it to the Adobe CC Cloud as an AI using its CC Cloud integration.
Though the artwork might be changed more or less depending on how you designed.

Sorry for the delayed reply. Issue logged. 

The color is off on PSD export preview of the CMYK doc.

Totally agree that this behavior should be removed.
Or at least Serif should give us an option to remove it.
 

When I am adjusting the layout, there are often times I need to see the layout without the selection boxes... this is fine until I need to make a few comparisons. I use the Undo/Redo actions for a before and after comparison but I can't because for some reason it was thought to be a good idea to include De/Selections into the Undo History. This makes it so if I Undo, and then select something, I've lost all my history I may have wanted to keep.

Can you remove this "feature" from the product. It's not great and makes me want to go back to Adobe pretty quickly out of frustration.

But even if the font exists on both systems, and has the same name so it's recognized, it can have different characteristics (kerning, letter heights, and various others) that can throw off the layout. We've seen that before, I think, with fonts that Windows and Mac have in "common".
If you're sharing with sharing with someone else, Packaging prevents problems.

Typo, right? Auto-correct going crazy, maybe? 😃

@ashf: the easiest approach may be to Package the file and transfer the complete Package to the other system. When you Open the Package (.afpackage) file the fonts in the Package will be temporarily installed for use in Publisher, ensuring the same fonts are used for that project on both systems.

I think you mean no longer works, right?

Longer or no longer?

"No longer".

Attention: it is necessary that the user has the right to do so. This is not always the case. Very often, only an extract of the collection is provided free of charge and with various authorisations.
On Windows, Yu Gothic and Yu Mincho are excerpts provided free of charge for Windows users.
According to the reference software MainType from the company High-Logic:
On Windows, Yu Gothic is a True Type TTC collection that includes 9 fonts divided into the following 4 files:
YuGothL.ttc: Yu Gothic Light, Yu Gotghic UI Light; YuGothR.ttc: Yu Gothic Regular, Yu Gothic UI Semilight; YugothM.ttc: Yu Gothic Medium, Yu Gothic UI Regular; YuGothB.ttc: Yu Gothic Bold, Yu Gothic UI Bold, Yu Gothic UI Semibold. On Windows, Yu Mincho is a set of True Type TTF fonts that includes 3 fonts distributed in the following 3 files:
yuminl.ttf: Yu Mincho Light; yumin.ttf: Yu Mincho Regular; yumindb.ttf: Yu Mincho Demibold.

Apple appears to have changed the name to delete the space when they added it to macOS.
They are listed on the Fonts Included with Ventura page without the space.
Apple and advanced applications such as Affinity use the Typographic Family name (Name16).
Since these are different on each OS they are properly seen as two different font families.
Word and LibreOffice use the style group / Family Name (Name 1).
These should be consistent with how Name 16 is configured.
Given Apple's history of sabotaging the style groups it would not be a surprise if they left this field with the space - which could create a name conflict.
I doubt this is an Affinity issue.
But I do not have the Ventura fonts to check them for sure.
 

Copied SVG from Adobe Illustrator, XD and Microsoft Office can not be pasted to Affinity.
Affinity should be compatible with those.
 
 

Hi @ashf,
Thanks for your report and our sincerest apologies for the delayed response here.
I can confirm I've been able to replicate this issue here and I've logged it with our developers now for you

@ashf
I have spoken to the developers about this and we think it will be possible to add both WebP and JPEG XL into the Export Persona on iPad to match Desktop, as well as being available in Export (already) . This is unlikely to be in 2.0.3 whose fixes are reasonably settled, but it is likely to appear in a subsequent 2.x update on iPad

Don’t know any way through the actual Export Persona (i.e. Slices etc)…but can workaround by Exporting to a Folder so everything is is same location, then through Files app…just Share > Save Image, will put it into Photos.
BUT…Export from Context Toolbar (Hamburger) has the Share button on bottom left… to choose Share Area > Whole Document/Selection Area/Selection Only. 
 

I can confirm that in one of last updates for AMD drivers (22.11.2) they did something with OpenCL 🤔

@Mark Ingram I see you are now ex-serif (all the best in new job), nonetheless want to let you know that your OpenCL test from GitHub, have now better results on my 6800XT
6800XT 22.11.1 Compiling kernel for device AMD Radeon RX 6800 XT (OpenCL 2.0 AMD-APP (3444.0)): Run 1: 513.386ms Run 2: 142.812ms Run 3: 140.732ms Run 4: 141.156ms Run 5: 143.655ms Run 6: 140.524ms Run 7: 140.218ms Run 8: 139.633ms Run 9: 140.573ms Run 10: 140.306ms Average: 178.299ms So still no Average ~50-60ms like on Nvidia, but ~180 is way better than ~1400, unfortunately benchmark results in V2 are the same as they were before, so I don't know 😂

I agree, please make this clearer. In v1.x the state was obvious from the icon. IMO it's way too subtle in v2.

Thanks for that.
So I downloaded a new Eye Candy installer. My original was 32 bit.
Reinstalled and now it works! The preview is a little glitchy but usable.
I noticed that the name in the filter plugins list is now Exposure software. Previously, Alien Skin.

Yes
before merge

after merge

@jellybeanFEIND
Welcome to the Serif Affinity forums  
Thanks for your report. The warping of contents like gradient fills is not currently attempted by the Vector warp code, sorry.
There are plans for Vector warp to be worked on more in the future, so I would expect this to change as the feature matures.

Early benchmarks on the new Radeon cards suggest they perform slower on OpenCL compared against their Nvidia direct competitor(s) (in this case, 4080). With Intel improving their ARC drivers and the clamoring about Nvidia's predatory pricing, maybe that will push AMD to put more care into their drivers... to be seen, hopefully.