markw

I wonder that too for a bit but then why dose Exporting from File > Export , which is basically @ x1, give image sizes of, in this example, 34x60px at 144 and 192 dpi? As I say I'm only encountering this discrepancy in the Export Persona.

Hello all, I noticed yesterday that both the current MAS and Beta versions of Affinity Designer will under some conditions output files of half the expected pixel dimensions than intended when using the Export persona. This only seams to happen if the documents dpi is set to 144 or 192. The attached test document is 34x60px (and contains 1 free chilli!) Set the document's dpi to 144 or 192. In the Export Persona, I set slice output options for x1 and x2 png. The x1 output is 17x30px : expected size 34x60px The x2 output is 34x60px : expected size 68x120px Export Size Test v1.6MAS.afdesign

Hi Alfred, yes it was fixed some time back. Are you seeing it happening again?

Well that's a bit strange as the Affinity products are all 64bit already. But I can't say I know why it's triggering the 32bit warning for you...

I’ve run into this problem too. See my post here: https://forum.affinity.serif.com/index.php?/topic/75973-pixel-brush-stroke-gets-cropped-in-bleed-area/&do=findComment&comment=396295

Yes I’m finding this too. It’s not just that the pixel strokes aren’t visible in the bleed area, they are actually being cut off at the point when they go into the bleed area. I also see in the ‘Export Persona’ that the option ‘Include Bleed’ is missing from the PDF export options in the current beta. As Simon bd say’s this dose kind of render the whole Bleed setup redundant at the moment. I would also note when in the Export Persona of the current beta, that when attempting to paste a file name into the appropriate field in the Export destination window (as generated by the OS), the Export button would instantly “Grey” out and be unavailable. Only typing in a file name directly would allow me to finally export. In both exports I used a red Rectangle which slightly extended beyond the document's set Bleed area. Current MAS v1.6.pdf Current beta v1.7.pdf

I started a test document in CMYK, entered your RGB values and get the dull green as you show. Changed the documents colour space to sRGB, bright green! But not spot on so then re- enter the RGB values and all is well. Again I would say do check your documents colour space.

I wonder what colour space you’r document is in? If it’s setup for CMYK then although you can access RGB sliders you will still only be able to generate colours within the limitations of the CMYK colour space. Which generally excludes zingy bright colours such as your wanted green. If the document is not for print you could change it’s colour space to RGB and have the green you want.

If you are on a Mac you could also “Check” the ‘Stationery Pad’ box in the file’s Info window. Every time you then open that file the OS will automatically duplicate it and it will be in the duplicated document that you will actually be working, leaving the original untouched.

Hello Quarter. Well I too have no idea what’s happening here but after doing the Subtract operation, as you found, there’s no hole punched through, just a lot of nodes in the shape of the N Interesting thing is though if you zoom right in and start moving nodes it soon becomes apparent that you now have two spines forming the letter N, The top one has a black fill thus obscuring the N shaped hole under it.

Ah, I see. Thank’s owner. To clarify the first post then, if I may be so bold; In Affinity Photo & Designer, using the MBP's Touch Bar to adjust a tools Opacity setting will in fact adjust the tool’s Opacity correctly as desired but the number indicating that Opacity change (top Left of screen) always says 100% regardless. This is a bug.

Colour opacity slider or Layer opacity slider? Either way I've never had a problem with either using the track-pad. Could you maybe supply a bit more detail regarding your issue...

Basically while the text box was still active, i.e. the blinking, vertical line indicating cursor position within the text is active. A fast double click anywhere outside the text box brought back the move tool. This I used to find supper convenient and fast. Now I get the Shape Text tool which I confess I’ve never needed quick access to. Perhaps what I’ve been used to doing was the bug and now it’s working as intended? But I hope not!

Hello all, It used to be that after using a text tool I could double click anywhere outside the text bounding box I was typing in and get the Move tool back. That no longer seems possible now in the current MAS version? Now the double click changes the cursor ready to make a Shaped Frame Text out of whatever is underneath it at the time. Is this intended behaviour now? Or a bug?

Have you tried making randomly shaped vector objects to build the gas clouds? Lowering their opacity and/or applying large amounts of Gaussian Blur to them. The blend modes of the shapes could also be played with for more interaction between cloud shapes.