BenDingus
-
Posts
3 -
Joined
-
Last visited
Posts posted by BenDingus
-
-
I can only get a crash report when it randomly crashes after starting a new file. This is the memory dump file. If I get one from the adjustment layer crashes I'll post. Haven't so far.
-
It just flat out closes with no error. It's doing this with a lot of things but the adjustment layers are the only ones I can produce regularly. Sometimes it's just closing right after it opens and I make a new project. It didn't do this when I first started using Affinity Photo at 1.10.0 until I updated to1.10.1, but uninstalled-reinstalled 1.10.0 is now randomly crashing and always crashing when trying to make an adjustment layer as well. Even after uninstall and reinstall I cannot use either version, even if I was using 1.10.0 before just fine.
I'm running Windows 10, have two regular monitors and a tablet monitor. I haven't made any recent major changes in hardware or software.
Photo 1.10.1 and now 1.10.0 after reinstall hard crashing when I try to make an adjustment layer. Among other random crashes.
in V1 Bugs found on Windows
Posted · Edited by BenDingus
So that got me to thinking, I do both overclock my CPU and GPU because I want my hardware to die and early death... but that's generally what causes GPU and CPU crashes. So I lowered the clock rates and it's stable even with acceleration on. But that begs the question, what thing is broken in Serifs software that they cause problems when even Prime95 suggests a stable overclock? In my experience it's usually not a supported problem if it only happens to overclocked systems. But out of a library of 50 GPU intensive games (some severely under optimized), 3 DAWs, 2 Video editing programs, and Blender to name a few, nothing has had this problem save for certain file types rendered in Sony Vegas. That said my solution for now is to deal with a slight rise in render times I guess. I may have faulty hardware as well, so It's not easy to pin down with custom hardware settings. If Affinity was open source I could probably track down the problem and then be able to verify what might be wrong with my hardware if that's the case. Either way, it kinda works... but it's very slow, and that's just something it's always been. It'll never be Photoshop... but it'll be affordable and mine.