DarkClown Posted November 27, 2016 Share Posted November 27, 2016 If you get to see theses crash reports every 20 Minutes when you're trying to get to know the prodoct ... it starts asking those questions as "will this ever be a serious competitor" ... is this "really" a beta(!)-release ... it just happens far too often... an no, it's not even that you can repeat the reason for it (that's why it's not mentioned under "bug" ... it just happens ... in between ... while rsizing, while adjusting a filter, selecting a brush ... while saving (love that one) .... sometime wacom pressure workes ... for no known reason many times it doesn't ... (no, I would have pointed it out as a bug, if it would have happend reproductively) .. but it just happens ... for no reason .. By the looks of it, i'm still stuck with PS6 ... bummer ... i7-12700KF, 3.60 GHz, 32GB RAM, SSD, NVIDIA GeForce RTX 3070, Wacom Intuos 4 Tablet, Windows 11 Pro - AP, AD and APublisher V1 and V2https://www.timobierbaum.com Link to comment Share on other sites More sharing options...
verysame Posted November 27, 2016 Share Posted November 27, 2016 DarkClown, I hear you, the latest beta is less more stable for me as well (with the first beta I hardly noticed any crash at all). Still, some users' feedback it's actually the opposite, as it seems for them it's got more stable. That said, I think that considering it "just" a beta is a little deceptive. From my understanding, the work that needs to be done is more than just making Photo a stable app. I read requests on this very forum every day, and I add mine too ;) That means the developers on their end have to deal with adjusting current features, possibly adding new ones, and of course, make the app more stable. To me, that sounds like more than the common work for a beta product. When at work we switched from CS6 to CC, I couldn't use PS at all. From CC to CC2014 I couldn't use AE. And that's Adobe, the big company with money, resources, and people. And CC wasn't sold as a "beta", but as a final, ready for production, software (imagine what that means for a pipeline in a company with daily jobs to tackle and deliver). And on their list whoever in charge of the relations with the users had the ungrateful task to deal with people complaining, reporting crashes, bugs, requests, and so on so forth. At least was personally a good test because I decided I would never switch to CC for my personal use at home (and in fact, I'm still on CS6). As for the crash message in your screenshot, although it seems you can't track down what's causing it, when you re-open Photo it should automatically send the log to Affinity which, from my understanding, somehow should be helpful on their end. Despite I'm getting more crashes myself, what makes me *stick* to Affinity is the philosophy behind their product (which is the reason why I bought Designer, even if some features are missing though some already on the roadmap). After 20 years of graphic design, I can finally breath some fresh air. The approach in the workflow is similar, yet different and much more interesting. Just my 2 c. SrPx and Rusty Arrow 2 Andrew - Win10 x64 AMD Threadripper 1950x, 64GB, 512GB M.2 PCIe NVMe SSD + 2TB, dual GTX 1080ti Dual Monitor Dell Ultra HD 4k P2715Q 27-Inch Link to comment Share on other sites More sharing options...
PaulAffinity Posted November 27, 2016 Share Posted November 27, 2016 Hi, for me each beta gets better and better. The WHOLE point of betas are to iron out bugs. Crashes are to be expected. This is particularly true of Windows where no 2 system configurations are the same! My beta test philosophy (I had 30 years in IT) is to load my machine, do a clean, switch off malware/antivirus software, disconnect extraneous hardware (wacom, special input devices, added screens, TVs on laptops etc..) THEN do a clean installation (without plugins). I then go through most of my basic workflow to check function, process, speed. I may run PS in parallel. I have AP video tutorials ready to run in a browser. After my basic test I then go through every menu item and test. Then on to multi level complex layer based workflow. When happy I add my input/output devices 1 at a time! Then restart the loop. I find this methodical approach identified either; 1. That AP does a function differently from PS. 2. A bug 3. A feature. 4. My input errors. 5. Windows component issues. 6. Hardware/Driver issues. AP is a breath of fresh air. For me it works. I am process driven so adaptation from PS to AP is easy for me. Cheers ,Paul Rusty Arrow, Patrick Connor and SrPx 3 Link to comment Share on other sites More sharing options...
harrym Posted November 27, 2016 Share Posted November 27, 2016 Great post Paul, everyone on beta should understand and sign up to those six points. I admire your discipline I'll bet 99.99% of us (me included) don't but should do this, windows open ecosystem is a nightmare for devs but it's also what's great about it. SrPx and PaulAffinity 2 Link to comment Share on other sites More sharing options...
SrPx Posted November 27, 2016 Share Posted November 27, 2016 I myself not having crashes...The OP described matter sounds a lot like some hardware problem, or high compatibility problem with a driver and the A. application, somehow... If you send them the crash dumps / info, that would help them remove you problems with it, indeed. :) AD, AP and APub V2.5.x. Windows 10 and Windows 11. Link to comment Share on other sites More sharing options...
Recommended Posts