NathanC

No worries, On export to PDF there is the option to export to 'Convert Image Colour Spaces' under the advanced export options, this will convert all images within your document to your document profile, it's worth noting that this is a conversion and not a colour profile assignment so this can result is colour values being shifted as a result. If you wanted to do this within the app prior to exporting, then it would likely need to be done by editing the image layer within the app to assign it to a different profile. You can choose to export to PDF without embedding an ICC profile but this can cause the final document to appear incorrectly if the appropriate profile is not installed on the device it's being viewed on, there isn't an option to export with no profile whatsoever, however.

Hi @coa47976 welcome to the forums, This is a known issue in 2.1 when changing advanced settings causes the matte to change to white and lose transparency, there are workarounds to this issue outlined in the FAQ post below.

Hi @JohnWGa welcome to the forums, In 2.1 if you Right click the quick mask button in the layers panel, the luminosity range mask along with the other mask types are still available. Alternatively, the mask can be added by going to Layer > New Live Mask Layer > Luminosity range.

Hi @globalMIND welcome to the forums, There appears to be a colour profile mismatch between your .afpub document which uses eciCMYK v2 and your placed .TIFF which is using Coated FOGRA39. In your publisher doc under Document Setup > Colour, If I change the profile to Coated FOGRA39, set it to 'assign' and then press Ok, delete and then place the tiff again and use the colour picker to sample, this then gives me the expected values. Updated document is attached. I could also do this the opposite way round in Photo, If I open your TIFF file in Photo > Document > Assign ICC profile > Change to 'eciCMYK v2' > Ok > Save and then update the resource in Publisher, it will then show the correct picked values. test updated profile.afpub

Hi @NotMyFault, Could you provide little more detail on this? It has always been possible to duplicate linked objects via Edit > Duplicate linked or just by duplicating the object in the layers panel, if you're duplicating an already linked object with the transform property linked, it will add the duplicated layer below you current layer, meaning you would have to temporarily unlink the transform attribute so that you could move the dupe layer out from underneath (tested with a pixel layer). However, based on what you've advised below with the crucial 'show links' function missing it wouldn't be possible to do this in Pub's Photo persona currently. I'll get this logged, thanks for letting us know. This is working as expected for me, In the Photo persona if I create a curve > Edit > Duplicate linked and them move the location of my duplicated curve and then using the node tool edit the nodes this then works even in the Publisher persona, this requires that the curve layers be linked on then 'Vector Curves' attribute and annoyingly this can't really be checked in the Photo persona as a result of the missing 'show links' function in the layers panel.

Hi @Sharkatana, Sorry to hear that, this could indicate there's a problem with your local brushes file. I would initially suggest factory resetting the local brushes file to default within the app by following the below (Note, this will default both vector and pixel brushes across all three apps): Close down all affinity apps Hold down CTRL and launch Designer 2 whilst still holding CTRL A 'Clear user data' menu will appear, tick 'Reset brushes' and then press 'Clear' Try editing any of the pixel brushes again. If it's still crashing, could you send me a few recent crash reports after encountering the issue? The FAQ linked below details how to find these. Many thanks!

Not that I'm aware of, if this is a function you would like to see implemented feel free to make a post over on the feedback & suggestions section 🙂

Hi @Sj_offl welcome to the forums, The Affinity apps don't officially support stage manager currently, which can result in certain issues when using the feature, I've linked the FAQ thread below for more information on this. 🙂

Hi @Mainecoon364, With no active selection in the layers panel and with the vector brush tool selected you can reset to the default brush by going to the Document menu > Defaults > Factory Reset which should switch the tool back to a basic round brush, however if you're actively working in a document would be easier just to create a basic round brush in your existing brush category and then switch to that if required.

Hi @Mainecoon364, Designer doesn't currently have a auto vector trace tool, this is something that might be made available in a future update, if you wanted to do this within the app currently, you would have to manually trace over your image using the existing tools. I've linked a post below where v_kyr has listed out a range of third party vectorization apps and websites where this can be done externally. 🙂

Hi @inkblank welcome to the forums, This is the Command controller, it allows you to use modifier keys on your current tool, similar to the keyboard modifiers for tools available on desktop. You can find out more about how it works in the help guide article I've linked below. 🙂 https://affinity.help/designer2ipad/English.lproj/pages/Workspace/wheel.html

Hi @Kyoge, I've now logged this issue with your file with the developers for further investigation. 🙂

Hi @Jerry W welcome to the forums, If the files contain linked/embedded resources this could possibly be (in part) the issue, could you possibly send us a copy of one of the files so we can investigate? If you could save it as a packaged file by going to file > save as package > select an empty folder > save > compress the folder to a ZIP and upload it the dropbox link below. https://www.dropbox.com/request/igYnnB82ycSUdw1dmGgS Many thanks!

Thanks for checking, it is certainly unusual that it only affects printing directly from V2, just to rule it out being an issue with the preset itself prior to sending it to the printer, could you try setting your preset to 'none' and then re-create your custom paper size within V2 print dialog (in the print dialog under paper size > manage custom sizes) and then try printing again without using a custom preset and just the assigned paper? I'll also see if I can replicate this on a different laser printer.

To my knowledge this has always been the case, back in V1 Panning/rotating the canvas are not recorded as events in the history panel, since these aren't edits to the document and just your visual perspective, so it would perhaps be better put through as a feature request rather than a bug (maybe as a changeable setting?) In my own opinion I would rather it didn't log any rotation/zoom events in the history panel since these are purely visual changes to how i'm viewing the document, and if I needed to undo/revert some changes made and had to reverse every small rotation/zoom change in my doc's history it would be quite frustrating.

That's a fair point, the notes could better reflect the colour picker's current behaviour in the colour panel. I'll log this with the docs team.

Hi @JeremyTankard, I see, thanks for following up and clarifying, this will be a bit of a tough one to test/replicate on my side as the issue you have described occurs during the physical printing getting jammed and I don't have that specific printer to replicate on. The apps use the same general Mac framework for the print dialog so the same preset should be available, but if you were to repeat your workflow using the same preset and document setup and print from V1, does it then work? If it does work, back in V2 if you were to re-create the same Print preset within the V2 print dialog and then print, does this make any difference?

Hi @Hangman, It could be made a bit more obvious, but to remove the sampler in the 'Info' panel, click anywhere on the colour values of that sampler (Not the 'Sample from location' button) so that the entire sample within the panel is highlighted in blue, and then within the preferences menu, select 'Remove Selected Sampler', like shown in my attached recording. Screen Recording 2023-06-06 at 14.06.37.mov

Hi @RBeci, I've moved this thread over to Bugs. I've replicated this issue and it has now been logged with the developers, many thanks 🙂

Hi @Thomas Neumann welcome to the forums, Looks like an issue with the location the image is being opened from, there is known issue with Sony A7iv raw files causing a similar error when imported from apple photos, however i've just downloaded a sample RAW file from your Camera, saved it to Apple Photos and then used the 'import from Photos' function within Affinity Photo and it has opened the file as expected. Could you clarify how you're opening the RAW file in affinity (E.G 'Open Document', 'Import from Photos') and what location the files are being opened from? If you could capture the process on a screen recording that would also help, i've linked a guide below. 🙂 https://support.apple.com/en-gb/guide/ipad/ipad08a40f3b/ipados Many thanks

Hi @NotMyFault, Looks like this is because the colour picker in the colour panel doesn't allow you to set a custom radius (nor does it follow the radius set on the colour picker tool), and instead samples from a 3x3 area, resulting in the desaturation shown in your recording due to multiple colours being sampled in a 3x3 radius. If you set and use the dedicated colour picker tool to Average (3x3) and then repeat this, the same desaturation can be observed due to the radius and minimal pixel distance between the colours. The ability to change the radius on the colour panels picker would be a good feature request. 🙂

Hi @SoapMaster, I can see you created the thread below in relation to this problem, where I have now replied. 🙂

Willkommen in den Foren, @SoapMaster Wie Hangman oben erwähnte, scheint dies ein Fehler zu sein, der mit der Fehlausrichtung zweier horizontaler/vertikaler Knotenstriche zusammenhängt, wenn das Dokument auf gegenüberliegende Seiten eingestellt ist. Durch Deaktivieren der gegenüberliegenden Seiten wird das Problem vermieden. Ich konnte das Problem in einem separaten Dokument reproduzieren und habe es nun bei den Entwicklern protokolliert, vielen Dank für die Meldung. --- As Hangman mentioned above, this appears to be a bug in relation to two node horizontal/vertical strokes being offset when the document is set to facing pages, disabling it prevents the issue. I’ve been able to replicate the issue on a separate document and have now logged it with the developers, thanks for your report. @Hangman thanks for looking into this 🙂

Hi @gemmi welcome to the forums, With your curve selected, try changing the fill mode to 'Winding (Non-Zero)' Under Layer > Fill Mode. 🙂 https://affinity.help/designer2/English.lproj/pages/CurvesShapes/fillMode.html

Hi @MarekGFX, We do have an issue currently logged in relation to the app hang occuring when opening a document whilst another file is exporting, but as you've described the exact same issue can occur when opening another file whilst the app is still trying to save another. I'll update the logged issue to reflect this issue, thanks for your report.