mark-h

If I use Infer LUT and select an 8 bit, RGB TIFF file, Photo almost always crashes and disappears. It's never done this when inferring from JPEG files. I've tested this a few times with different files to try and find a pattern but I can't determine it yet. I've tried this using ZIP compression and no compression in the files but it doesn't seem to make a difference.

I've since tried it in a different document and it didn't happen, but it's still happening in the attached file. Swings.afdesign

Something I've noticed when using round or square caps on dash line style strokes is that when you expand the stroke, the caps at the start and end are cut off. This doesn't happen with solid line style.

If everything is vector then not really, there are no dots/pixels to be concerned about. The only time you might want to consider DPI is if you're exporting to a PDF file where unsupported features might get rasterized.

I've been using the new Beta all morning and everything has been working perfectly 😁

I checked out your file and I don't think this is a problem. Points and pixels are different units. Your document resolution is 300 dpi, so are several pixels to each point. 1 px and 1 pt will only be the same size if your document is screen resolution (72 dpi). You can confirm this by working out the the point/pixel factor by dividing the resolutions—e.g. (72 / 300) × 130.2px = 31.2 pt. So at 300 dpi 31.2 pt = 130.2 px Of course you can still simply enter pixel values (e.g. "130.2 px") into the boxes and it will automatically convert to points and be the width you want. Just remember to enter the units you want after the value.

Brilliant, thank you. If I encounter any more problems I will share the file where possible. EDIT: Sorry, just realised the Beta is Mac-only and I'm on Windows.

Thank you. Is there any estimate on when a fix will be released? Are we talking days/weeks/months? I'm need Affinity for a lot of vector illustration at the moment and I want to know if it's worth backing up all my presets, uninstalling and putting in an earlier version (which also means I wouldn't be able to open any files edited in 1.8 presumably).

Yeah, the improvements to 'expand stroke' are most welcome indeed. As for this Add issue, sometimes modifying the geometry (with new nodes in places like the overlaps or where you can easily remove them after) before using the Add operation can stop the weird shapes forming. So you can try that as a stop-gap solution for now.

Since updating to 1.8 I've been having problems with the add/subtract geometry options. Sometimes it adds a lot more nodes in areas that weren't even overlapping and at other times when adding shapes some nodes get lost entirely and gives weird results. Needless to say this is a bit frustrating when building vector shapes. I've a attached screenshots of a few examples that have cropped up over the last few days when trying to add geometry. You can see shapes changing and seemingly pointless node changes.

Better than than nothing, although that does mean it also copies over the text style as well, so you have to get those matching first.

I'm not sure if this is a bug or a new feature of 1.7. If you draw a shape with a colour fill, and then use the text tool to put text in this shape, the fill colour stays—in previous versions it would make your shape transparent. And once it's a shape text object, I can't find any way to change or remove the colour. The only colour I can change is that of the text. I am using 1.7.0.367 on Windows 10.

Apologies if this feature already exists - I couldn't find it. It would be great if you could select a maximum value for a slider in a macro. Case in point, I've made a macro to add film grain, and one of the steps is a gaussian blur filter (called 'softness' in my macro - see attached). For this effect you're only going to want values like 0.1px, 0.2px... nothing over 1px. So it would be really good if the slider only went from 0px to 1px, rather than 0px to 1024px which just doesn't give the precision control needed... instead you have to type in values manually. This would be especially handy when offering macros to other people as it would save additional instructions on how to use them if you can just set a fixed range. Cheers, Mark

Also it should be noted that the displace filter in Affinity doesn't behave like Photoshop/After Effects. It doesn't displace things based on luminance, but rather it seems to look for edges/areas of contrast. If you have a smooth black to white gradient as your map you'll get next to no displacement at all.

I too would very much like the ability to display only in X or Y, and not just for 3D imagery. I've found it a very useful feature for creating certain effects, particularly reflections on uneven surfaces (like oceans for example).