Solanaar

Okay, thanks, all the files are on my main internal hdd and my software runs from an PCIe ssd. Though I never before seemed to have issues with connectivity.

Might be. Could it also be related to an external hdd? I have one connected, though, I don't have any of the used files stored there.

I work a lot with linked documents. In one document I have several other documents linked and those documents also have linked docs in them. Often, when I save one of those the message in the title pops up. Additionally sometimes the linked docs do not update. Any idea what's going on here?

Scenario: Create two shapes (tested it with circle and rectangle tool). Both have to be closed initially. Convert both to curve. Use break curve on one shape, then select both shapes, select all nodes of one shape, then drag those nodes onto one node of the other shape (tested with snapping on only) leads to a crash. Reproducable.

Scenario: Create two shapes (tested it with circle and rectangle tool). Both have to be closed initially. Convert both to curve. Use break curve on one shape, then select both shapes, select all nodes of one shape, then drag those nodes onto one node of the other shape (tested with snapping on only) leads to a crash. Reproducable.

Hello, I noticed the beta crashing less with actions that would crash the release version constantly. Do you have any idea, why that might be? I detailed the crash behaviour in this post: I tested it this morning and the same actions that crashed the retail version quite reliable (opening and closing layer-groups, adjusting global colours in the colour-window) didn't crash the beta. Any idea, why it seems more stable now?

Sorry for the late reply, had 2 busy work days. Actually no, I didn't even know SSDs can be updated. I will look into that! Thanks Edit 1: I had the most recent firmware, and updated the nvme ssd driver. I also went ahead and updated my chipset driver and bios, but sadly it still crashes on my machine, still no reports Edit 2: I downloaded the 1.9.4 beta cause I'm desperate and so far no crashes. I will report soon if any crashes happen with the beta

@GabeI attached a CPU-Z log to this reply. Here is a summary, if the file can't be opened: OS: Win 10 Pro-N 64 bit (Build 19042) Motherboard: Gigabyte X470 Aorus Gaming 5 WIFI (Bios is Version F3) CPU: AMD Ryzen 7 2700 8-Core @3.2GHz Memory: 2x8GB Corsair DDR4 3.2GHz Graphics: MSI NVIDIA GeForce GTX 1060 6GB PC CPU-Z Log.txt

I did some testing on my partners pc and voilá: zero crashes. So this narrows it down a lot. It has to be my machine, either hardware, drivers or some software running in the background. But this means it doesn't belong here anymore, since it probably isn't related to AD... Which sucks for me, but at least the software isn't at fault. I also noticed my bios is massively outdated (version dates back 3 years), so I will check that first and hope it'll fix it. Thanks so much for your help, @Komatös. Really appreciate it!!!

I looked through the list, but have none of the apps, or, in the case of the nvidia solution, I don't have the mentioned option. I attached the log.txt to this reply. I tried working after a restart with all the apps disabled, sadly, it still keeps crashing Log.txt

That's some great advice! I don't. I use Windows Security, but I do have a few other apps running in the background. I will try to close as many as possible, Though it feels weird, how consistent the crashes are.

I had it disabled previously, I actually turned it on to try, if it crashes less. Thanks for the suggestion, though. I will disable it again and hope it will at least stop crashing every 3 clicks (as it does right now).

Hello, I am working on Win 10 on the recent version (1.9.2). I am converting a rgb file to a cmyk file right now and it's permanentely crashing (sometimes seconds after starting the files, sometimes after minutes). Informations: - the file that was sent to me was a .ai-file - I converted it to cmyk and saved it as .afdesign - I reference the original rgb-version - I saved the original rgb-version as .afdesign and only use that one - I open both in AD. I have the cmyk-working file embedded in AD, while I seperated the rgb-one and placed both windows side-by-side for easy comparison - the crashes happen when I switch windows, click on layers, click on color swatches, move sliders, etc. I can't pin point any crash triggers. - I can't share the file, since it's contract work - I couldn't reproduce it on new files or other files (tested with two .afdesign-files) - The crash happens with OpenCL enabled and disabled - The crash happens with updated craphics drivers - The crash happens with increased memory, too The real issue is, that the crash reports folder @ appdata/affinity/designer/1.0 is empty. There are zero chrash reports and I couldn't find a setting in the preferences. Any help? Work takes insanely long and I lose a lot of progress even though I save constantly. It's hard to get a workflow going when I spend half the time reopening and rearranging the files.

Oh, yeah, that makes sense! I found out about variable fonts just today. This is also good to know. I think I already did install some variable + static ones, now I know what to do, when I come across such a conflict! thank you!

Ok, so this is a weird one: I tried to edit the font of my "body" paragraph text style, after I installed a bunch of google fonts. The bug didn't happen before, as far as I know. The bug happens only, when I scroll towards a specific point in the list (fonts starting with "al"). It doesn't matter if I drag the scroll bar, scroll with the wheel or hover over the lower part of the list (autoscroll). It will crash. It crashes not, when I change fonts in the normal character-window. I downloaded the fonts from here: https://www.typewolf.com/google-fonts It does happen on a new document. It happens with OpenCL enabled or disabled. I will try to find and delete these specific fonts and see, if this helps, but I wanted to report it anyways. Version is 1.9.2. EDIT: Alright, found the culprit: It was Alegreya, probably because in the folder provided by the site the font was named alegreya[wght].ttf. I downloaded it through google fonts and now it works. Leaving this post up, to help people having this issue. The solution was checking the installation files, because they had something weird in their name.

It's a template I copied over from a .psd-file I opened in AP. I will upload it to the dropbox.

Hi, sorry for the late reply. I uploaded the complete file. The mentioned group is on the second last page. I opened it today to check if the issue persists and had another (new) display bug: One of the other images (a cropped duplication of another image in the same document) being very blurred. It displayed in the document and the page viewer. A close and reopen solved this. Edit: I should mention it doesn't "Fail to render" completely. Rather the images in question become a clump of pixels as if the image has been "compressed" Thanks for the support!

Hey, I've discovered something weird with pictures I placed inside my pages while viewing it inside AP as well as on exporting. It appears, when I zoom in on the pictures (see attached file). It looks like the zoomed in version on export as well. The pictures are pixel layers inside a group. Also I had other visual bugs that seem to be resolved after I closed and re-opened the file (which is why I don't have any screenshots). Inside the page viewer the thumbnails of pages with only a big image inside displayed colored rectangles (blue, green, brown, etc.). A picture I layed some effect layers over appeared glitched when zoomed out (the further out the bigger and heavier the glitches). Glitches were chunks of image from other projects (really, really strange) and text symbols (I think they were light blue?). This one was really weird... Not related to images but appeared when I tried to save the file as a new one (in fear I corrupted something): It told me it was unable to save the file (displaying the old file name instead of the new one, though) because of an error What is going on? The document has a lot of large image files and around 25 pages.

Greetings, I hope, this is actually a missing feature and not just a feature I missed. I find myself often wanting to readjust a previously created artboard to fit an object (shape, image, etc.) but without snapping this becomes messy everytime. Being able to make artboards snap would make this kind of work way smoother. Until this feature will be available I'll have to live with the workaround of moving the object outside the artboards and then creating a new artboard (funny enough when creating a new artboard snapping to object works fine, so why doesn't it work when readjusting?) Actually this feature would be a request for every affinity product that features artboards and snapping Thanks for reading!

Greetings, while researching another issue I came across an issue I've been struggling with in the stable release for quite a while: When selecting a shape tool (pen tool, rectangle tool, circle tool, etc.) and immediately changing the colors and then drawing a shape, the colors (and stroke settings) will actually apply to the previously selected object instead of the newly drawn. This goes even further for the pen tool whereas you have to at least draw two nodes to be able to adjust color and stroke for the current shape. In my mind when I have a shape tool selected the context sensitive bar (which is actually changing depending on the selected tool, NOT the selected object, so there's an ergonomical issue, as well). should reflect settings to the shapes I am ABOUT TO DRAW. If, on the other hand, I select either the object selection (V) or the node selection (A) tool, I would expect the context sensitive bar to reflect options and functions corresponding to the SELECTED object. For me it is important to pre-set color and stroke to accurately visualize the design I am making. Right now I am forced to painstakingly readjust the shape (sometimes each node in a complex shape seperately ) if something doesn't fit. I hope I could bring my point across, and why I think this should be adressed from an ergonomical point of view. I attached a video illustrating the issue both in the beta (where I'd expect the change to be more reasonable than in the stable release), as well as in the release version (where the affected object even is the artboard which I very, very rarely change settings like color or stroke, if at all - do artboards even have a stroke?) I wonder, if other people found this to be an issue in their workflow. I am also aware, that this is a matter of workflow and taste, so I would suggest adding an option rather than changing it completely. Thank you for reading! Shape Tools Color.mov

Greetings, I've found an issue in the recent AD Beta build 1.7.0.209 When drawing a shape with the pen tool, in the release build you could adjust any node in a selected shape with the pen tool to have the effect of the left click, meaning readjusting both node handles equally. In the current build this is not possible, instead left clicking a node with the pen tool starts a new shape at that point. Is this an issue, a new sub mode I don't know of or did this functionality got moved to another node? I hope I could illustrate the issue sufficently and I hope this function will not be removed entirely, because it is incredibly useful, especially for symmetrical designs. AD_Pen_Tool_Issue.mov