MattP

Awesome!

Hi Cap'n, Welcome to the forums :) This may sound daft, but the best person to ask is the one who you will be sending the designs to... Once they've told you the physical size and DPI then enter that into the Document Setup. I'd also query the fact that you were going to make it CMYK... Ask the printer what they would prefer to receive - certain printers will prefer RGB input, others will prefer CMYK. If they've said you need to provide a PNG then the chances are that they're expecting RGB data, so use an RGB document format or you'll miss out on a large part of the colour gamut that's just not available for CMYK documents. Thanks! Matt

Maybe it's because we also offer the other formats on the clipboard, that Hype is choosing the wrong one? (or maybe something else is broken - I'll investigate further!) :)

Just for your info, you can go to Affinity Designer -> Preferences -> General and choose 'Copy items as SVG'. That should do what you want - I hope! :)

But as you have said yourself, saving the file (i.e. pressing Save in our native file format) takes less than a second. Exporting the file (i.e. explicitly generating a non-native result) is the bit that's slow. Export is based on what you intended to achieve with the program and in this case you have told the program to generate a vast amount of data, so it takes a while. This is true in any other vector software - and none of the other software will warn you about your document setup at the time when you create the document because it's not a problem until you do something that you may not intend to do, so why warn the user. If I had a piece of software that continually told me "Are you sure? This could generate lots of data if you use some raster effects and then export it" then I simply wouldn't use it as it would be far too nannying... I hope I'm not coming across in the wrong way, I'm simply trying to explain why our software (and none of its competitors) would warn a user about something which is completely valid to do, just because they may do something that would cause it to export slowly if they used certain features in certain ways... If I was making a document of huge proportions and high DPI, I would be very aware that I needed to export as a vector and avoid layer effects or anything else which would cause rasterisation - if I did this, the export would be instant... I know this because I have researched the subject area and created the document this large for a specific purpose. Thanks again, Matt

If you didn't use Layer Effects in your vector document and exported to a vector format, the size and DPI would be of no consequence, hence everything would be instant so there is nothing to warn the user about... The problem is simply because the document was created at an inappropriate size/DPI and pixel-based effects were used. Is it reasonable to warn the user whenever they select a very high DPI or size that if they use certain effects then the experience will be slow? Or should it be the user's responsibility to understand what they're pressing and what it means? You can do the same in other software and it will also be slow and will not warn you why. If I drive a car, it doesn't warn me that driving on pavements is dangerous, that animals may run out in front of me or anything else that I know in advance because I have studied how to drive and thought about the process before getting in and starting the engine... (I know that's by no means a great analogy, but you get the point I'm trying to make, I'm sure?) Thanks in advance, Matt

There are no plans at all to move to a subscription. The free updates will happen for as long as version 1.x is in active development and at the moment we have a long way to go with both Designer and Photo before we are even going to start writing version 2.x, so I don't think you should be too concerned about not getting value for money at this point :) Hope that eases some of your concerns, Matt

Hi Malcolm, Hmmm... well, choosing anti-aliasing ramps is always one of those 'this is better', 'no, this is better' things and I'm sure there are scenarios where you can provoke any engine to produce better/worse results... but that's not to say that we got it right. I think that perhaps the best solution here would be if I could make our renderer default to a customisable ramp until such time as it was overridden by the object settings you choose. That way, the user can change the default ramp at any point and the whole document would redraw with that new ramp. It could also be saved as the document default for future documents. Would that be okay? :) Matt

Hi Lojza, This sounds crazy, but select 'Convert' before you choose the new colour format... I think we have a logic error on our dialog... Hopefully that works for you now? Thanks, Matt

Hi Josue, Welcome to the forums :) I don't have VLC player on my Mac so can't view the .webm file you've uploaded, but I did just take a look at wilcom's software to see what you might be talking about... Have you tried changing the 'Pen Mode' in Affinity Designer's Pen tool? If you set it to 'Smart' mode you should get the curve behaviour you're talking about (it auto-generates splines between points) and if you simply click in the normal mode (or Option/Alt+Click in the Smart mode) you'll put down line segments. Is that what you're looking for, or is there something more to it? :) Thanks, Matt

It was actually quite confusing when the default behaviour was to apply the top-level constraints - you'd get objects which didn't seem to be dragging out to anywhere that made sense, especially for the default assets that shipped with the product as the user has no idea ahead of time which constraints are applied to which assets, so the results seemed unpredictable.

Hi everyone :) I explained before that there are certain critical issues that are actually causing crashes for users and we wanted to concentrate on getting everyone up and running first before looking into other things - I think we're there now (with the exception of one Mountain Lion issue with the Export Persona) so hopefully we can look into the other bugs that have been brought to our attention. Thanks again for everyone's patience - there are always wrinkles at every major version launch, and all we can try to do is learn from it and change some of our methods... Hope that makes sense? :) Matt

Status: Beta Purpose: Stability & Critical fixes Requirements: Purchased Affinity Designer Mac App Store: Not Submitted Download: 1.5.2 Beta 3 Here This beta is intended to fix any critical issues found in the current App Store version and should be considered to be more stable than the App Store product. To use this beta, simply download the file from the link given above and double-click on the file to open the installer. Follow the instructions to install the beta version. The beta sits alongside the Mac App Store version and will not interfere with it. Fixes: Resolved Font enumeration crashes at startup, including utterly broken fonts that trigger a system refresh of the font list when enumerated! Fix for Mavericks issue with the new Export Persona Fix for Assets being dropped into the Asset Panel even when it is collapsed - which explains why some people are seeing an inability to move objects to certain areas of the screen (it's because the panel is still getting tested as though it was not collapsed and you're creating assets every time you move!) Fix for crash seen when creating Assets from objects like Masks that perhaps have no dimensions by themselves Fix for renaming Assets causing a crash Fix for inability to change paragraph leading

Very nicely done! :)

I'm also running a MacBook Pro 15" Retina (2015 model) and mine is running fine too - but I've seen a few people with issues when they have their display profile (in the OS itself) set to Adobe RGB, Display DCI-P3, or some other Wide Gamut profile... we looked into it and found that the next Beta of macOS Sierra actually fixed the slowness, so it seemed to be an OS issue. There's no incompatibility I'm aware of, I just think that there's something about the graphics drivers on macOS Sierra and some machines that seems to not be quite right - and that's utterly out of our control - but Apple already seems to be on the case with fixing it for their next update, I think :) Matt

Hi andykanu, Assets can only be dragged into the Assets panel from the document itself, not from the Layers panel. I totally agree that they should also work when dragged from the Layers panel so we will add this, but it's working as currently intended :) Thanks, Matt

Ben has just put in a fix for this - I will hopefully be able to include it in a build I create either today or tomorrow. Sorry for the inconvenience in the meantime :( Matt

I got my response about 10 seconds after I entered my details, so that's a bit confusing? :( I'll PM you the link in a second :) Matt

I'm just not seeing this - mine seems to be working very reliably? It might be a particular 'thing' you're doing or a problem with a particular type of object/command that you perform? Is there any chance you might send me a document that is 'broken' like the one above and I can see if there's anything obviously wrong? Send anything to support@seriflabs.com Thanks! Matt

Could I ask you a strange question... you don't happen to be running macOS Sierra and have a DCI-P3 display profile (or Wide-gamut/Adobe RGB screen profile set)? If so... it *might* be the case that you're falling foul of something strange we've seen on the current version of Sierra that seemed better for us in the next beta version of Sierra...

This sounds very odd indeed - the software has no code in it to delete a file from the file system, it only has code that can create new files and add to other files... :S

That looks great! Could definitely imagine this as part of a game! :D

Hi Vlad, I spotted the video the other day, which was why I was asking about constraints - I'm guessing those items have constraints on them and it's a specific set of constraints that cause the issue? Thanks again, Matt

Hi Tristan, If it's what I think you're talking about, it's an issue in macOS Sierra initial release that I think is fixed in the macOS Sierra Beta Thanks, Matt

Are we talking about copy/paste with constraints onto different artboards? If so, is it just a subset of constraints that are showing the problem? Could you tell me which combination of constraints aren't moving for you? I'm trying to stabilise any critical (crashing) issues at this point so that's where the focus is, then I can move on to usability/bugs :)