Ryuuga

Updated to 2.3.0 recently. The issues in this thread has been fixed. Thank you!!

Yes, 169.png covers the entirety of the canvas from edge to edge. Thanks a lot for your help. I'm glad we were able to pin down the specific issue(s). Now I will wait patiently for the fix.

Here you go, Dan. Thank you for looking into this for me. This is the particular spread that happens consistently, but I have had it happen on other spreads (and other projects as well.) Occasionally I get it to the top of the Layer Stack but I couldn't get that to happen in this recording. I did do a little bit more here, by messing with the text in other layers, I realized it would be added directly to the top of that specific layer. Is that an intended function? My workflow is not as consistent as it should be so occasionally when I see errors in the other layers, I'm tempted to correct it on the spot heh. I found a temporary solution in this particular situation, by Locking 169.png layer, the assets do eventually get added to the top very consistently. unknown_2023.11.16-16.47.mp4

What Application are you using? [Publisher] Are you using the latest release version? [Yes 2.2.1] Can you reproduce it? [Yes] Does it happen for a new document? [Yes] DESCRIPTION OF ISSUE I have some assets made of Fonts placed in a specific order (in a group folder) I have some existing layers. Whenever I drag an asset onto the canvas, it doesn't always create a layer at the top. It doesn't even create a layer on top of the current selection. Sometimes it will be all the way on top of the layer list. Sometimes, the asset layer will be created in the middle of the layer list in between some other existing layers. I can drag the same asset twice. And both times it may appear in a different layer location. Attached is an example of my layers panel. highlighted in blue are my grouped assets. Sometimes assets will be added on top of the list. sometimes, it's sandwiched above 169.png and other layers. Expected outcome: When I drag asset onto canvas, asset layer is created on top of my current layer selection. OR IDEALLY in the same group folder.

I just had an Affinity Publisher file corrupt on me. Honestly I've been having quite frequent random crashes on this program and today, after one of the crash, I tried to reopen the program and restore the file, I got the corrupt file error (usually after the crash, it restores the file perfectly fine) I'm on Windows 10 Affinity Publisher v2 Error appears when trying to open the file. Saved to Local Drive can I upload to the dropbox for you to have a look see please? EDIT: Nevermind, I managed to find a workaround by opening a new document and using Document> Add Pages from file Selecting my "corrupted file" I managed to open it, save it as another name and now it works fine. After some research, turns out this is not the first time this has happened and it has been happening since version 1. Therefore, I still would like to lodge a report on this issue. Having a file randomly "corrupt" on me after hours of working on it is VERY demotivating and it's very hard for me to have confidence in using Affinity Publisher. From now on, there will always be anxiety on the back of my mind that the program might crash at any moment and possibly corrupt hours of my work. That is not a nice feeling to have while trying to work creatively, you know?

Hey Chris, thanks for the quick reply and help. I fiddled around with it a little more and manage to find a workaround. Turns out my ICC color profile was set to Gray/16 greyscale D50. When I changed that to Gray/8, the color fills works exactly as it should, filling out the selected areas. After that I tried saving, restarting program, reopening the document and it is still working fine with Gray/8 setting. I'll be honest, I'm not entirely sure what the differences or 8 vs 16 is yet at the moment, but I guess I'll be working with gray/8 for now. Hopefully that might give you some clue on reproducing the issue though.

Thank you for your reply. I have just installed 4.8.1 MSNET from the link you provided. Restarted the PC. The Issue is still there after installation and restart.

Windows 10 Affinity Photo version 2.0.0 Can you reproduce it? Have not tried, but I will attempt to retrace my steps to the best of my ability here. Does it happen for a new document? If not can you upload a document that shows the problem? Happened with a relatively new document that I started yesterday. Cannot provide sample doc. If you cannot provide a sample document then please give an accurate description of the problem Is hardware acceleration (in Preferences > Performance) ON or OFF ? (and have you tried the other setting?) OpenCL ON produces the image you see below. OpenCL OFF straight crashes Affinity Photo. What happened for you (and what you expected to happen) Made some freehand lasso selections and then attempted to fill them with color. Result: color filling in random spaces and even has some weird looking display glitch. (Photo attached below) Expected: color to fill within the selections. Provide a recipe for creating the problem (step-by-step what you did). - opened a new doc in Publisher, - added a master page with photo frame - added bunch of pages with said master page. - filled the pages with Place image. - Switched over to Affinity Photo for editing - DUPLICATED AND RASTERIZED IMAGES - DENOISED SOME 10% and added some black and white leveling (I'm working with blackand white comics) - Now I make my selections - once done, I tried to fill a few pages with color. Works okay so far. - Save doc and closed program. - Following day, I opened the same document, Gets an error about unlinked files(?) - Decides to ignore it and continue filling color for the remaining pages - BUG OCCURS Now it is worth mentioning that I have done this exact workflow on a previous separate document with no issues whatsoever. The issues above in UNDERLINE AND ITALICS are the only NEW steps I did for this document. Other than that all is the same. Screenshots (very handy) or a screen capture/video. Included below. I can't show the actual image itself, but this was done on an empty Pixel Layer within the document. Any unusual hardware (like tablets or external monitors or drives that may affect things) or relevant other applications like font managers or display managers. Not that I know of Did this same thing used to work and if so have you changed anything recently? (software or hardware) Did not change any hardware of software. Things I've done so far to try and fix the issue: - making a new layer(Bug Persists) - deleting old layers one by one to try and isolate the problem layer (Bug still persist) - Restart the Affinity Photo program (Bug still persists) - Restart Computer (Bug still persists) - Turn OFF OpenCL (Affinity Photo Crashes instantly) Hypothesis, Saved document is corrupted somehow. Might have to redo this entire piece again.