Sean P

It could well be that - I would suggest keeping it in mind and go through the same steps in the next build and see if still crashes! :)

We have recreated the issue with the shakey layers and have passed it onto the developers, however I'm unable to get it to crash.

There is currently a crash in the app that will occur if you double click a Recent colour swatch. Could it be that you've accidentally double clicked the colour swatch?

No worries - these can be easily missed :)

Unfortunately Petar, I'm unable to reproduce this crash. Have you been able to reproduce it anymore?

The Opacity on your Stroke colour is set to 0% So you are switching around the colours of the Stroke and Fill (which are quite similar) however it appears as there is no stroke colour because opacity is set to 0%. (See your screenshot).

Hi KoBu, Good spot! I can reproduce this so I shall get it reported to the developers!

Hi Timbo59, I've just been following through this tutorial and the application is certainly not behaving correctly. I'll get this reported to the developers! EDIT: Just to add that if you initially place the nodes roughly in the correct place using the mouse and then type the values in it should allow you to work around it. The problem occurs if a typed value will move a node beyond an existing node, however using the mouse to move the node beyond an existing one does not cause a problem.

Hi JET, I believe this is a bug/oversight than intended - I will get it reported to the developers.

Hi af-user, What version of the nVidia drivers are you using? Have you tried updating them at all?

Thanks for the file! I've been able to reproduce the issue - it seems as though it is related to the Alignment of the stroke. If it is set to Centre - you don't get the issue, however if it is set to Inside or Outside you get the issue. I'll get it reported to the developers.

As this is a beta each iteration should gradually improve the stability of the software. The issue mentioned is fixed in the upcoming 1.5.0.6 build which should be out later this week.

Hi KoBu, This is now possible using the new Symbols panel (View > Studios > Symbols).

Hi Woodkopf, This is a known issue and is caused by the dual monitor setup with different resolutions. It is already logged with the developers so hopefully we will see a fix come through soon!

Hi Beta-Tester I've tried this with German language set and Mark's translation DLLs and unfortunately I can't reproduce it. Does this only happen in 1 document for you, or have you had it happen in a newly created document? When you add the new layer and it doesn't appear - have you noticed any triangles in circles appearing on layers inside the Layers panel (to indicate there are objects inside that layer)?

Hi Jonopen, This is a known issue and affects both the Mac and PC. However it is currently with the developers to look into.

To expand on Alfred's answer, Affinity allows you (by default) to snap to a maximum of 6 objects at any time - these 6 objects are known as 'Snapping Candidates'. The reason for this is with many objects on a page it can get very tiresome trying to align your objects to others when it is snapping to all other objects on a page - therefore we came up with the idea of snapping candidates. To let users know what the current 6 snapping candidates are it will highlight them with the purple line you've described. To change a snapping candidate simply hover your mouse cursor over an object and it will then highlight purple to show it is a snapping candidate. As Alfred has mentioned these can be hidden by disabling the 'Show snapping candidates option', however if you don't like this method then we have also allow you snap to all objects in the immediate layer, all objects and their children in the immediate layer and all layers.

Hi Willernest, Unfortunately these seemingly random crashes can be quite hard to diagnose and repeat. I've tried using the Selection Brush tool on a pixel layer, however it is not crashing for me. Do you remember any specific steps you were doing that lead to the crash? If so try and repeat those and see if you can reproduce the crash.

Hi thatFloozie, Unfortunately I've been unable to recreate this from scratch. I've tried using a Ellipse with a red fill and white stroke and when I create a palette I still only get the two colours. I've also tried it in both Draw (with and without pixel drawing mode on) and Pixel persona and still no luck. Would you be able to attach the document that is giving you a problem please?

Hi Svero, We've just tried the GTX 960 on my Windows 8.1 machine (Intel Core i7 2600, 8GB RAM) and unfortunately still not able to reproduce the issue. As well as posting the contents of the Event Viewer that Chris B has asked for could you try and answer the following questions for me please? 1. Have you tried running any kind of 3d game or application at all? If not would it be possible for you to try installing and running the 3DMark Basic Edition (it is free - their should be a download link to several different sites) and see if that gives you the same behaviour 2. Are the beeps coming out of your PC speaker, or do they sound more like they are coming out of your PC case? 3. Would you be able to give a bit more information on the hardware you have such as the CPU, Motherboard and RAM. CPU-Z should be able to give you this information if you're unaware of it (you'll want the CPU tab, Mainboard tab and Memory tab). Thanks!

Hi Matej, This is a known issue and has already been reported to the developers! :)

Hi Mick, Sorry to be a pain, would you be able to zip those and link them? As there are a lot of files and I can't see a way in Google Drive's site to download an entire folder at once. I'm glad clearing the data has worked. Hopefully with this appdata I'll be able to reproduce the issue.

Hi Robert, 1. I can reproduce the issue mentioned with a single View Point so i'll get it reported. You mentioned about keyboard shortcuts what were you using? And was they only applied to Move to Previous View Point and Move To Next View Point? 2. I am also able to reproduce this, so i'll get it reported to the developers! 3. Any chance you could post a screenshot of this? Also what size and orientation of document are you using? As for the View Commands we are currently trying to keep parity with the Mac version. If you do wish to see these please make a post about it in the Feature Request forum.

Hi Matej Junk, I'm able to reproduce this so I shall get it reported to the developers!

Thanks Alfred, I'll take a look into that and get it reported!