mark-h

This maybe isn't a bug but something that seems to be unnecessarily getting in the way none of the less. When I render Blender's freestyle line art as an SVG file Affinity Designer won't open it. It says the filetype isn't supported. The problem seems to be that the SVGs start with an <?xml> tag. If I remove that they open fine. So there's a workaround but it's a bit of a pain when working with many files. I don't know if this is a very unique scenario or if other SVG files may pose this problem as well. Either way it would be nice to not have this speed bump. Cheers, Mark

I'm having similar issues with v2.0.x. It tends to freeze after a couple of hours of working. And since I started paying attention to what I was doing when it freezes I've noticed it always happens while I'm panning. Disabling OpenCL doesn't fix it. I'm using a 5th generaton Microsoft Surface Pro. I'm going to try the 2.1 beta and will see if that's any better.

Screenshot attached. I've only got 4 crash reports and the most recent one is dated over a month ago. I wonder if because it freezes and I have to use the task mamnger to end it its not able to generate one? FYI it froze again today while panning.

Hi, I've disabled OpenCL but I'm still getting crashes. The last two times I noticed it happened as I was panning with the space key. This may have been the trigger the other times too but I can't be sure, I pan around my documents almost instinctively and without thinking. Where I'm noticing it the most is on my 5th-gen Microsoft Surface Pro running Windows 10 if that's of any help. Cheers, Mark

Has anyone else been having problems with Affinity v2 products regularly freezing? I use it daily, and almost daily (sometimes multiple times) Designer or Publisher will freeze when I'm trying to do something. I haven't been able to find a commonality, other than I think it happens when I'm manipulating shapes, even something as simple as adding round corners to a rectangle or resizing a shape. It happens in large, complex documents that I've been working on for hours and it happens with simple documents I just started working on minutes after starting the app. I can't figure out what's causing it. I don't recall the app freezing nearly as often in v1. I've noticed this happening on a beefy Windows 11 desktop machine and my Windows 10 Microsoft Surface Pro. I'm currently running v2.0.4 of the apps. Presumably because it freezes and I have to use Windows to force close it, it doesn't count as a crash s no crash reports are generated. I'm sorry that I can't narrow it down further than this.

Ah great, thank you! Maybe I'd hit the sync button next to it at some point. I've been using this app for years and never paid attention to those buttons.

Hi all, I've got a problem with an Affinity Designer document where any frame or artistic text box I draw comes with a coloured background and I can't find a way to get rid of it. It's not the text highlight colour. It doesn't happen in all documents but It has happened at least once before in a v1 release of Designer. The blue gradient that is applied is a colour I've used elsewhere in the document so it seems like I've somehow set that as the 'default' fill for any shape. Is this a bug or is there something obvious I'm missing? Can anyone help? 2023-02-13 09;14;24.mp4

That equation is really handy, thanks! Not being great at maths myself, does anyone know what would the equation be if I wanted the opposite effect (i.e. Mercator to equirectangular) as in the original post?

I've seen this problem before and it's happened again today so I've experimented and saved the file. When I have shapes and text with the exact same colour, the opacity slider (either in layers or in colour) doesn't affect the two objects the same. The text seems to be less opaque, unless there's nothing but empty canvas behind it. Even once the text as been converted to curves the problem remains. One way to make sure everything is the same is to use Copy/Paste Style but this isn't ideal when some objects are fills and others are strokes. Plus, I can't determine which one has the 'correct' opacity. And basically I'd like to change the opacity of objects without having to make sure none of them look different. I've checked RGB and CMYK colour values and they all seem the same, and It's an 8-bit, sRGB file so I can't think what else could be causing this. Can anyone help? I've attached a screen recording to demonstrate what's happening, and I've included the project file. Cheers, Mark example.mp4 Opacity problem 2.afdesign

For this specific case I have found a less cumbersome work-around. Inkscape and Adobe Ilustrator weren't showing the symbols at all but if I do a find every instance of <use href and replace it with <use xlink:href in the SVG file then they display in those apps fine. I've yet to find a solution the szie being ignored in Affinity but at least now I can do away with the PDF method and all the icons will stay in their own groups.

Ah, dang. This is exactly what already I did for the project I'm working on just now 😅. Well hopefully a simpler solution will present itself soon.

Hi. Thank you for this. This was just a sample map so I don't need the files. It's the 'how' I'm more interested in. How were able to get everything the right scale?

Hi, I'm not sure if this qualifies as a bug or a feature request but when I import an SVG file that uses <symbol> tags Affinity seems to ignore the width and height attributes of each <use> element so all instances of the symbol are imported at the wrong size. At least with the file I'm trying to work with. I've attached an example here where you can see what's happening. Not only are the icons too big, they're all the same size (e.g. some mountain icons should be smaller than others.) The positioning seems to be off as well but I have a hard time telling if that's not just because of the size/transformation anchor point. Does anyone know of a quick fix for this? Can I reformat this SVG so that Affinity can read it properly? Cheers, Mark P.S. It would be an absolute joy if Affinity could import the symbols in an SVG file as Affinity symbols for easy editing. Roryia 2021-05-25-13-08 (imported into Affinity).afdesign Roryia 2021-05-25-13-08.svg

Great, thanks. If anyone else is suffering from this issue, my work-around was to go to File > Export, set up the PDF options there and then save those as a present. You can then apply that present in the Export persona. M

I'm trying to add two PDF export formats for an artboard, however the 'Convert image colour spaces' box won't stay selected. If I tick it, then go to edit another format, the tick will be gone when I return to it (see attached GIF). I've tried unticking 'Embed ICC profile' but that doesn't fix it.

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.