Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by GlueFactoryBJJ

  1. +1 (Ditto!) Remembering last use would be great. Every time I go in to change a color after a restart of the app, I have to switch my "color selector" from Tint to HSL Color Wheel (MY preferred starting point). UGH! Scott
  2. I'd like to thank the fellow users who have posted to try to solve this problem. I just wish that there was a Serif presence here to respond... Anyway, I have good news. I tried reinstalling 1.9.1 and disabled OpenCL in the Edit, Preferences, Performance settings. When I opened the "Problem" files, Designer crashed immediately. Then I tried using "WARP" rather than the "NVIDIA Geforce GTX 1080ti" option. It still crashed. Frustrated, I started to recreate the work I had done previously. I was able to complete the project without problem. From what I can see at this time, it looks like the earliercrashes during save corrupted the "saved" files. That is why they were crashing on opening them. IMO, Serif needs to handle the crashes better. However, disabling OpenCL does seem to have fixed the problem... at least as far as I have tested it right now. I'll know more once I work on additional projects. v_kyr - thanks for the great post on how to resolve the problem. FWIW, at least in my experience, OpenCL has been problematic on Windows machines for over 10 years. Because of this, I'm going to skip OpenCL for at least the foreseeable future... until I can see a notable performance boost and/or Serif requires it to run the program. Thanks! Scott
  3. Sure, anything is possible. However, I don't (knowingly) use OpenCL (unless Designer is using them) and I'm using the latest Nvidia GPU drivers. I update the drivers monthly. Just before updating, I was using 1.8.5 just fine on the same files that 1.9.x crashes on.
  4. walt.farrell, Well, I'll add some context to this... at least in my situation. With Affinity Designer. I purchased both Designer and Photo directly from Serif and started with 1.8.0(?). When I was running 1.8.5, I would OCCASIONALLY run into situations where the design just appeared to be too complex (too many elements) and it would crash. Often this would happen if I combined (grouped) elements of two or more designs and/or pulling in a large number of elements from .EPS files. I kind of assumed it was a memory leak issue because it would usually work after either restarting the app or restarting my PC. However, if I could load it, I could save it (it didn't crash when I did the Save As). Usually, I'd get most of my changes back through the "auto save" function. When I would start 1.8.5, it would say there was a saved version and ask if I would like to use it. Once I "upgraded" to 1.9.x (.0 and .1), whenever I would open one of these complicated files, it would either crash outright (no error messages), or crash when I was trying to Save As, the file. It SEEMS to work OK on a plain File, Save. Also, the "limit" of number of elements in a design (e.g. combining two or more designs) seems to be pretty dramatically reduced. When combining designs with a large number of elements (e.g. curved pieces, say in the 100++ range) the app crash with a lower number than with 1.8.5. Also, EVERY attempt to Save As these files, assuming I can get them to open, results in an immediate crash. And when I try to open the file again, it will not give me the prompt to open the recovery file, but will just open the original. So, this is the "crashing" problem I have. I can't say it is the same as Sinforiano's, but it is the one I'm having. To make matters worse, the few files I have changed since "upgrading" to 1.9.x can't be opened with 1.8.5. That would have been a nice thing to point out in the update. So I'm stuck with not being able to do any work with these (fortunately few) files until this gets resolved. To be clear, there are NO error message when the app crashes. It is just gone, so I don't have any information to send or post. This has happened on the three projects I have tried working on since upgrading to 1.9.0 and the exact same thing still happens on 1.9.1. I have even tried uninstalling 1.9.1 and reinstalling it to see if that resolved the problem. It didn't. My system configuration is as follows: AMD 3950X on ASUS Crosshair VIII motherboard Gigabyte GTX 1080Ti (11GB) 64GB RAM 2TB M.2 NVME SSD Boot 2TB (4x500GB SATA Raid SSDs) Video/Photo/Illustration drive Misc bulk storage (internal and external HDD) Win 10 Pro I hope this helps because I've become rather dependent on Designer (and use Photo on occasion) and I'd really like to get this problem fixed. FWIW, the reason I haven't posted about this before is (1) that other things have come up and (2) I figured that since it was a .0 release that there would still be a couple bugs hanging around that would be handled in a .1 release. In my case, THIS problem wasn't fixed. Now I'm at the point where I need to use Designer again and I've uninstalled 1.9.1 and reinstalled 1.8.5. Scott PS. On a similar note, could Affinity (Serif), PLEASE make a back up copy of the working file on saves so that if we made changes, we wouldn't inadvertently save over the original when we meant to save it to another name (e.g. File, Save rather than File, Save As). I just lost all of my work on a file because I "auto piloted" a File, Save rather than a File, Save As (I started with a more complete file and deleted a bunch of it and then was going to click File, Save As, but hit Save instead (through habit).
  5. Wow! Thanks for all of that work! A great illustration (no pun intended) of why this is a bug and not an, as you said, "Adobe proprietary format" issue. I'll download Inkscape and use it to output a .svg file and see if Designer can read it then. Again, thanks for your work/time! Scott
  6. Did you even read what I said? If this were an Illustrator export/import issue, then why is MOST of the data there, but not all? Why would only some text be visible, but the rest behind some Illustrator barrier? Also, again, if this were an Illustrator export/import issue, then why can other software apparently "get around" this .ai file barrier? I've been working with computers, software, and IT since the late 1970s and have been a beta tester for more software than I care to recall and this problem has all the earmarks of a BUG, not a mystical locked file format incompatibility problem. Postscript is a "Page Description Language" (PDL). The first, in fact. To be able to read/write it is a pretty straight forward process (it's text that can be read by anyone with a programmer text editor), especially since it has been around since the mid-1980s and the current version (3.0) since 1992. What is it that the other (free) programs on the internet know that Affinity doesn't? This is readily available technology and there is nothing in the format that is still under patent (the patent expired at least 8 years ago, 1984 + 20 years = 2004 or 1992 + 20 years = 2012). You should be careful when you say "cannot", when the answer is probably "isn't a priority". Anyway, my $.02... Scott
  7. I guess I should have included this pic to show what it looks like when I disable ONE group of the many layers in the .eps file. As you can see, there is A LOT of information available in this file. The problem is that I cannot get the word "SEAL" and "TED STATES" to appear. I can find all of the other letters, but nowhere can I find the missing letters. Also, if the .eps files were so locked down, then how is it that a free web site can create its own .eps file reader to accurately display the .eps file and allow you to download it? The "correct" version (the .jpg file) above was created from this .eps file with the website I linked to. I can see every layer except for that with the missing letters. In the "screen capture" of the problem in Designer/Photo's display of the file, you can see that the reflection of the seal is mostly complete. At least it displays all of the letters surrounding the seal. Are you saying that the only part of the .eps file that is in a .ai file is the part with the missing letters? Perhaps you could clarify this? I have also attached a screen capture where I have resized the Layers panel and show the individual layers where all of the letters that surround the seal are located and displayed. I cannot find the layers with the "missing" letters. But the free website can... Any help would be appreciated, but I still think this is a bug that Affinity should fix. Scott
  8. This is the first time I've run across this problem (note that this is a licensed image and cannot be reused). Designer will not display this image correctly. I know it is good because it will display correctly with online .eps file viewers (specifically: https://epsviewer.org/onlineviewer.aspx ). I am using Designer and Photo version Both display the file exactly the same (at least as far as I can see). I can't upload the file because it is 17+MB in size. Even zipped, it is 3.3MB. Using 7zip I can get it down to 2.1MB. Arrrgh! If an Affinity developer would like me to, I could email it to them. Below is a .jpg file of what it is supposed to look like. It looks nothing like this in Designer or Photo. I have the .jpg file (as you can see) and it is working for now, but I would prefer to have the .eps so that I can easily edit it. Anyway, while I have a work-around, I wanted to let the devs know there is a problem with, at least, this .eps file. I have not run into any problems with other .eps files that I license. Any help/fixes would be appreciated. Scott
  9. Hmm, I just realized something. I had been working on the projects I had "suddenly" been having problems with for a few weeks now. And no problems. Then I just started having problems saving yesterday... My realization is that I had just moved the files to the Documents folder the night before, just before going to sleep. Then I started working with the files yesterday from the Documents folder. And I realized I couldn't save there. As I noted, other applications had no problems saving to the project folders (I tested). Just the Affinity apps (anywhere in the Documents) folder. My point is that this problem didn't suddenly appear. It was probably there all along, I just didn't notice because I was using an "unprotected" drive/folder up to that point. So this problem has probably existed since I installed the Affinity apps last year, I just didn't notice it since I have only recently gotten back to doing photo/illustration work. Anyway, thanks for your time and help! Scott
  10. Ok, first I tried running the app with Administrator privileges, but no luck. Then I looked up the Controlled Folder Access from the search bar and added both Affinity apps to the allowed list. And, yes, you were correct, that appears to have fixed the problem. Then again, for a brief time last night Designer was allowed to write to the Documents folder (as I noted in my last post), but this morning, before adding the apps to the allowed list, Designer was blocked again. Go figure... My question is why are the Affinity apps the ONLY ones that are being caught by the CFA (on my system, a problem that hasn't appeared in the 8 years I've had this system and two years I've been using Win10 Pro)? My guess is that, perhaps, they are not signed correctly and Microsoft is putting them in the "dangerous apps bucket" because of that. I have not done ANYTHING to my file structure that would cause ONLY those two apps to have this problem. And I have many "freebee" apps installed that would seem to be far more likely to tick the "unsecure/watch out for randsomware" check list than only the two Affinity apps. I ran across this thread on answers.microsoft.com in which this observation was made: -- https://bit.ly/2WYgWLG If the Affinity apps are kicking off warnings in Microsoft Defender, then it is up to Affinity to find out why (in collaboration with MS) and fix the problem. Then again, as the OP noted, this also appears to be a problem with MacOS, so, again, the fingers keep pointing to this being a problem with Affinity, whether a signing/install issue or application behavior problem. IF Affinity is doing everything perfectly, then they need to contact the Microsoft Defender people to get them to fix the issue on their end, even if it is something as simple as automatically adding the two Affinity apps to their "whitelist". Don't get me wrong, I LOVE both apps! I completely dropped Adobe because of these two Affinity apps (and DaVinci Resolve). My objection is that the appearance is for the customer to be blamed for something they have apparently done to incur this problem, when it is most likely an Affinity issue (in one way or another). Frankly, most users just don't have the patience to try to work through an issue like this, much less to find a helpful forum like this to find a work-around for their problem. Scott
  11. I have a generic install. Literally every other application other than Designer and (I just tested) Photo can write to any of the folders in the Documents folder. Only my two Affinity apps (Designer and Photo) cannot write to that folder. Because if this, I'm standing by my assertion that it is something to do with Affinity's installation. It probably isn't setting the correct permissions. I've worked in IT for decades and have never seen something this specific to one software publisher. An app maybe (I've used to do a lot of beta testing), but not all said from a specific publisher. The specific error in Photo is: (while trying to SAVE a file) "C:\Users\Scott\Documents\temp.afphoto File not found. Check the file name and try again." I just checked to see the exact wording is for Designer, but now I can save to the folders I literally could not have to this time last night. Argh! Designer appears to somehow have fixed itself, but now Photo is broken. I can save with Photo to anywhere else (that doesn't have expected access restrictions), but not to the Documents folder. Sigh... Scott
  12. Especially with the "default" being to become transparent where overlapped. I would think that the vast majority of the time the user would want to have it remain solid and, therefore, for that to be the default. Scott
  13. I have this same problem, but with Windows 10 Pro. I am using Designer I can save to any other directory (and other drives), but not the Documents folder. All of my other apps can save to the Documents folder, but Designer can't/won't. Could this be a problem in the Install not setting up the application's permissions correctly? Other applications ask if the app should be installed for the current user or all users. I generally install for all users, if given the chance, but the Designer install doesn't give that option. I don't know if that is part of the issue. FWIW, I have tried uninstalling and reinstalling Designer. No change. Still won't save to any folder in the Documents folder. It will read the files, but not save to it. I have even copied the Designer folders that are in the Documents folder to another drive/folder and Designer will both read and save the files in that folder. Just not in the Documents folder. This appears to be a specific problem between Designer and the Documents folder on Windows 10 (and, apparently, MacOS). Scott
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.