Just loaded successfully the monomer in my Mac client devprev hot fixed version… am letting it run and will see what happens if I "push" it with something that has recently been crashing. Opportunity for a "yay" or at least a preliminary "woohoo"? We shall see. Amusingly, game_dynamic still showing in finder bar.
Still running (but my Mac "conveniently" slept last night instead of running, sigh, the oh so "helpful" default energy saver was on. I need to find an old all.macro file because in devprev I can't load recipes, and the recipes that loaded with the all.macro aren't all the problematic ones that crashed in the old main client.. (unable to load recipes in devprev…feature or bug?) But so far, so good.
(recipes "problem" fixed, I just copied the all.macro file from my "BOOTCAMP" drive foldit files over into the devprev Mac folder resources folder.)
I got the same message as Susume and Bertro when I tried to load puzzle 1350 in the hotfixed devprev client just now. But the monomer works now that the hotfix is in place
(The above on my Mac client, Sierra 10.12.3)
Have been running Mac client with one of the DRemixW scripts on the monomer all day… these were crashing at some point early on in the previous Mac main client and are apparently working fine now. No crashes on either client so far through the day with anything I've tried. So on the monomer, so far this is testing well.
Not an unexpected one, but a first crash for one of the monomer clients running devprev. Actually got farther than expected before it crashed on a group recipe (that often crashes badly on the monomers).
Thread 4 crash
Log (mac log) attached, but "highlight"
Thread 4 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x00000003 ecx: 0xb09df1dc edx: 0x00000000
edi: 0xb09e2000 esi: 0x00000006 ebp: 0xb09df208 esp: 0xb09df1dc
ss: 0x00000023 efl: 0x00000296 eip: 0x9f8b749a cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000023 gs: 0x0000000f
cr2: 0xa5326320
Logical CPU: 0
Error Code: 0x00080148
Trap Number: 132
Addendum to the above…Just noting that all other recipes (that you would run on a no rebuild monomer puzzle) are working fine and no other crashing. So for me, the monomer puzzles issue is apparently fixed by the hotfixed update.
Thanks for the feedback, actiasluna.
It sounds like maybe the recent update has at least helped matters, then?
Yes, fewer if any crashes just running the monomer without recipes… that said, though, still crashy on recipes it shouldn't have problems with. Thread 4 (a thread that crashed very frequently when things were at their worst) again. Better, but not yet "better enough."