Mark Ingram

This isn't the same crash as the others, unfortunately. I've had a look at the report, and I can't see what's crashing, as it crashes in Microsoft's code. Can you tell me what graphics card you have?

I think that the lag you're seeing is just the amount of time it takes to render the brush stroke into the document. I assume the brush strokes always catch up, and you never miss part of a stroke? What size document are you working on? I've just tried creating the same brush strokes in Photoshop, and we render the brush strokes faster than they do. Have you tried this with Photoshop no your machine?

There is only 1 category by default, "iOS 10", if you have another category that says "Assets", did you add this yourself?

Does your Assets panel not look like this?

Chances are, you've got a 64bit processor in your computer, you just don't have the 64bit operating system. You could always install the 64bit OS if this is an option?

What OS are you on? What are your printers? What version of Affinity? Which Affinity product (Designer or Photo)?

Hi, - The cursor should have black and white lines on it for contrast, I'll take a look to confirm. - Can you give me the names of a few fonts that don't render correctly? - Designer supports the Windows Scale / Zoom values. I use a 4K 24" monitor at work, and have 200% zoom set. My laptop is also 4K, but 15", so I use 250% zoom. Designer scales to each monitor accordingly.

Hi, it looks like your graphics card doesn't support Desktop Window Composition, as your window title bars aren't transparent. Unless you have disabled it somehow? What is your graphics card?

You can also enter any size as a pixel size and it will convert it. So even if you're displaying in points, or inches, etc, you can type in "100 px" and it will set it to 100 pixels size.

I've just done some analysis on our startup time, and I can see some areas which could be improved. I might not have time to fix them before release, but I will do it at some point. In theory it should make it over twice as fast to start up...

Thanks for the video. If you use the mouse, does it display the same lag?

AI is a closed / propriety format, as such the only thing we can read from it is an embedded PDF, if the exporting software writes it.

It's a bit hard to comment without seeing a video of the lag in action. What specs are your machine?

You probably have brush nozzle with 50% flow set, this will only put down half the ink per nozzle, which is why the preview is grey, and when you draw a stroke it appears black (that's because multiple grey nozzles have stacked). I'm assuming you're using a raster brush, not a vector brush. The video capture software you're using probably doesn't support capturing from a Direct3D surface, which is what we use to draw the document. There are applications out there that do support it, I use SnagIt which works fine.

Hi, it sounds like perhaps Aero hasn't been enabled properly. Can you attach a photo of your current theme in "Appearance and Personalization" in the control panel?

Hi, we've taken a look at the file, and the problem is caused by a dashed line style of 0.05 width which takes a long time to expand! If you change the offending line style, it will instantly export. We're going to add a fix which ignores small dashed styles like this, but in the mean time, just tweak the line style. Did you import the file from somewhere else?

Hi, we don't send an email when a new patch is released. Instead we give a notification via the application, and we keep a post stickied to the top of this forum. The latest beta version will always be available there. The latest version is 1.5.0.28.

Which cursor are you referring to? I just looked at the crosshair cursor (when brush nozzles get too small), and it does have black and white lines.

Like many of our controls, we use exponential ranges so there is a greater range. This shortcut won't change, as it would require a change on both platforms, the help, and the newly published Workbook (though feel free to change it if you prefer :)).

Hi, can you look in %APPDATA%\Affinity\Designer\1.0 (Beta)\CrashReports and see if there are any files in there? If there are, can you attach them to this post so I can take a look?

I agree, but we haven't got a method for reproducing this, and nothing about checking for a new beta has changed in RC3, and no other user has mentioned this, so chances are, this is caused by a change in the user's machine. Anti-virus / anti-malware are capable of bringing down an application as they inject themselves into the running process, so if there is a problem in that software, it can bring down our application. We've seen it before on this forum when someone had a piece of video capture software installed. There was nothing we could do to fix the issue, other than recommend that they uninstall the offending software. I also sent a bug report off to the manufacturers of the video capture software.

Hi, Welcome to the Affinity forums. This isn't an Affinity error message, it sounds like a networking error or something similar? We've not heard any similar reports.

This will be fixed in build 29. Thanks for your report.

Hi, thanks for that. Unfortunately it looks like your crash report was never received. I'm guessing it's the same problem a few others had been having with an ICC profile failing to load (that was one of the main fixes in build 28).

It looks like there will be some restrictions on using the Dial with non-Studio Surface products (https://msdn.microsoft.com/en-us/windows/uwp/input-and-devices/windows-wheel-interactions):