lastingMadness Posted March 5, 2022 Posted March 5, 2022 (edited) UPDATE 03\05/2022: I changed the undo limit as suggested by Bruce below. It looks like that gave me at least one more safe without closing. Thanks to Bruce and "Not My Fault" for helping resolve this. I will post additional updates if anything changes. Context: I have been working with the Affinity Suite for several years at this point and have not run into this issue consistently. Additionally, it will help to know that the project where this issue occurs features a lot of repetitive objects and that when I work on the next version of the object, I store the others outside of the frame. Issue Description: Now, on the project attached below when I move an object out of frame and attempt to save my project, Affinity Designer closes. It does this without freezing or becoming unresponsive. When it closes, there is no message to send a crash report to Serif or Microsoft. It simply closes. As you will be able to see, the designs in this project are not particularly complex. My computer fan is never audible while I work, and yet this continues to occur. Steps to Reproduce: 1. Open Attached Project 2. Drag element out of the work frame 3. Save project via Control + S command Computer Specs: Device name Uno-Machine Processor AMD Ryzen 5 3600 6-Core Processor 3.60 GHz Installed RAM 32.0 GB Device ID A9057042-055B-469F-8C7B-F1FBAB079136 Product ID 00326-00872-61387-AAOEM System type 64-bit operating system, x64-based processor Pen and touch No pen or touch input is available for this display Graphics: Nvidea Geforce GTX 1660 Operating System Specs: Edition Windows 11 Home Version 21H2 Installed on 8/19/2021 OS build 22000.527 Experience Windows Feature Experience Pack 1000.22000.527.0 DnD card factory.afdesign Edited March 6, 2022 by Kyle Gunderson Potential Resolution Quote Hardware: Processor AMD Ryzen 5 3600 6-Core Processor 3.60 GHz Installed RAM 32.0 GB Graphics: Nvidea 1660 8GB Art examples: http://MadMaker.redbubble.com
NotMyFault Posted March 5, 2022 Posted March 5, 2022 Can confirm the issue on iPad. Designer crashes even after deleting all layers. Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
lastingMadness Posted March 5, 2022 Author Posted March 5, 2022 That's interesting. If all of the layers can be deleted and the issue persists, maybe there's a defined limit for the size of a document's history? I want to preserve that if I can, but now I'm curious. Quote Hardware: Processor AMD Ryzen 5 3600 6-Core Processor 3.60 GHz Installed RAM 32.0 GB Graphics: Nvidea 1660 8GB Art examples: http://MadMaker.redbubble.com
Old Bruce Posted March 5, 2022 Posted March 5, 2022 2 hours ago, Kyle Gunderson said: ...a document's history? I want to preserve that if I can, .... I am always curious as to why people want the history saved. I can see it for people learning new software and or new techniques. It has an important place in tracking down bugs. But for regular production work, why do you want to save the history? And I am pretty sure there is a limit, check the Preferences. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that.
NotMyFault Posted March 5, 2022 Posted March 5, 2022 I tried to “save as” the file without history (on iPad), but the history was always preserved (on iPad). Maybe history got corrupted. Next try would be to copy all (or selected) layers into new file and check if issue gets resolved. lastingMadness 1 Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
NotMyFault Posted March 5, 2022 Posted March 5, 2022 2 hours ago, Old Bruce said: But for regular production work, why do you want to save the history? And I am pretty sure there is a limit, check the Preferences. As i run into new (or old) issues every day, this is my reason. Another reason is lock layer does not protect against unwanted changes, and often i move or resize layers unwontedly. Having the option to go back helps. Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
lastingMadness Posted March 6, 2022 Author Posted March 6, 2022 7 hours ago, Old Bruce said: I am always curious as to why people want the history saved. I can see it for people learning new software and or new techniques. It has an important place in tracking down bugs. But for regular production work, why do you want to save the history? And I am pretty sure there is a limit, check the Preferences. While tracking errors is probably the conventionally "better" answer, to be honest I think time-lapses are cool, and Serif is working on an "Export Timelapse" feature that I think would be cool if I do anything with these cards later. Also, thanks for the tip! Quote Hardware: Processor AMD Ryzen 5 3600 6-Core Processor 3.60 GHz Installed RAM 32.0 GB Graphics: Nvidea 1660 8GB Art examples: http://MadMaker.redbubble.com
Staff Lee D Posted March 7, 2022 Staff Posted March 7, 2022 @Kyle GundersonI've passed the file over to our developers along with a crash report to take a look as I got the same response. Quote
lastingMadness Posted March 9, 2022 Author Posted March 9, 2022 On 3/7/2022 at 9:00 AM, Lee D said: @Kyle GundersonI've passed the file over to our developers along with a crash report to take a look as I got the same response. Thank you for monitoring the situation and moving us towards a more widely-available solution Quote Hardware: Processor AMD Ryzen 5 3600 6-Core Processor 3.60 GHz Installed RAM 32.0 GB Graphics: Nvidea 1660 8GB Art examples: http://MadMaker.redbubble.com
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.