Search the Community
Showing results for tags 'corrupt'.
Found 15 results
-
- in multiple export formats file is corrupted. Only happens in 1.9, never experienced this since 1.6. & usually doesn't show in thumbnails. _DSC11159 was originally a tiff, too big to send. Has happened 10 times maybe in 300 photos. Re export has worked but definitely something going on here?
-
I have a logo I've been working on for a client and was almost finished, just waiting on some more feedback. I received feedback today and went to open the file and it says that it's corrupted on my mac hdd and the same for the backup copy on my usb drive. I even tried opening it on a windows machine and same issue. Please help, I really don't want to have to start from scratch. Is there any way to recover my work? Yukon Leatherwork Logo.afphoto
-
"This document appears to be corrupted.\n\nThe document must now be closed" I worked on this document last night, saved everything and closed. Logged in today only to find out my file is properly loading in background but affinity is displaying an error message and the document shall be closed. all of my work is lost! here is a video and i am providing the file too for developers to take a took. ScreenRecorderProject2.mp4 Template1.afpub
-
Hi, so recently I have reset my widows, meaning completely removed all files. I backed-up most of my .asdesign files. My problem is that every time I try to save a file, (even a completely blank one) it does let me save it, but after I have saved it, a pop-up saying: And then I click close. It does this with every .asdesign file i save. I can't open the file afterwards either. Then it's just corrupted. I use sRGB btw. I can still open old documents (The ones that I backed-up from before the reset) I've seen 2 other posts about the same message/pop-up, but it didn't match my problem: they tried to open a file. I've reinstalled Designer 3 times and made sure it didn't leave any files. I've tried many things. It really sucks. Here is an example of a file: example.afdesign, but as i said it happens to all files. And this is the 2 pop-ups i get when trying to open fx. example.afdesign Pls help me:) Many thanks. DouVI PS. feel free to ask for any more information, cause I'm desperate and really need this to be solved;)
- 3 replies
-
- affinity designer
- error
-
(and 3 more)
Tagged with:
-
Unfortunately all of my Affinity Publisher files are all becoming corrupt, I can fine a common link, is there a limited files that affinity Pub can handle? I love this product but this is making it impossible to use because when i make a document it becomes corrupt a few days or weeks later.
- 5 replies
-
- affinity publisher
- corrupt
-
(and 1 more)
Tagged with:
-
Affinity Photo 1.6.6 macOS High Sierra 10.13.1 After adding a bunch of images of the same photo session to a batch job in order to resize them, Affinity Photo corrupts/destroys some images by adding solid white almost throughout the whole image, while other images are OK. Attached is an archive containing the same 4 images - before and after a batch resize. The 2 get corrupted every time after a batch job, while the other 2 are OK. Affinity Batch Bug.zip
-
Can any you fine folk direct me on how to delete a file which has not been Saved-As yet? This is the file I was working with that froze the UI on my AD app as reported in my previous post ('Frozen Functions - most menu items disabled'). Regarding my 'frozen screen' in Affinity Designer - it appears to be a corrupted file, if possible it is probably self-induced. Attached are a couple of screenshots, one showing the screen BEFORE and the other showing the name of the file that I can now see after Force-Quitting AD and getting things moving again. The file name is now visible to me and reads 'CVlogoStockholm(currupt:pixelates).svg' as seen on screenshot-1. My question has now shifted from how to unfreeze, to how I can get rid of/delete this file. I don't want to go near it for obvious reasons. So far I've only tried dragging it into Trash from this 'Open Recent File' drop-down but having never been Save-As'd, it doesn't move. Suggestions? Thanks as always folks. I appreciate your time and instruction. -Christo *working on a 2017 MacBook Pro with Affinity Designer 1.5.4*
-
Hi, i exported an EPS file and it breaks the path strangely. Attached the original file and the exported eps version. Anyone experienced the same? Thanks Alberto ExportEps.afdesign ExportEps.eps
-
Here's my problem. I've been editing a lot of photos in Designer, basically just adjusting the levels and highlighting. However, recently a lot of my files have been turning up corrupted once I try to reopen them. The adjustment layers remain intact, but the image layer is scrambled. Just a bunch of lines. I have the most up-to-date version of Designer (1.4.2) and I'm running Mac OS X Yosemite 10.10.5. Any thoughts on what might be causing the problem, or how I can fix it? Thanks all.
-
First off, I'm not sure if this is the right place to post so I apologize if this is the wrong forum. I'm a college student in the early stages of a big final project. I've been diagramming a section of my city with Affinity Designer. I'm using the trail at the moment to see if I can switch over from Illustrator. Until now it's been a glorious experience. However, I when I opened my Macbook Pro this morning, Affinity Designer (1.2) was unresponsive and my cursor was the dreaded spinning beach ball. I ended up having to force quit out. I figured it wasn't a big deal as I had saved my work last night. However, when I tried to open my file back up I got this error: At this point I panicked a little. However, I figured there were a few things I could try before freaking out for real. Interestingly, I discovered that I could open it no problem in Affinity Photo Beta (1.1.2.24443) I then tried saving it as a .afphoto file and opening it in Affinity Designer. Sure enough, it opens just fine! All is not lost! I was then able to save my work as a .afdesign file and voila! I'm back in business! This episode was a bit nerve wracking as you can imagine. I figured I should probably post about it here so that Affinity could look into it and hopefully prevent this from happening to someone else.