tag:blogger.com,1999:blog-3341941751324943000.post6287642572644051642..comments2024-03-25T14:53:54.413+00:00Comments on PuzzleMad: Jerry McFarland's Quadlock 1Kevinhttp://www.blogger.com/profile/05649523779226834414noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-3341941751324943000.post-23924817293264628392011-07-06T06:53:50.783+01:002011-07-06T06:53:50.783+01:00You are right, George. It will work with the coars...You are right, George. It will work with the coarser grid but then the 2 asymmetric lock picking pieces become symetrical or very offset indeed. This is due to having far more limited choices about where a notch goes.<br /><br />I haven't properly explored the alternative solutions. Some are due to order but it des appear that the position changes too (the heights of the lock tumblers is slightly different in some). It is hard to really tell because my computer struggles with the file.Kevinhttps://www.blogger.com/profile/05649523779226834414noreply@blogger.comtag:blogger.com,1999:blog-3341941751324943000.post-84208357870881894332011-07-06T06:17:19.502+01:002011-07-06T06:17:19.502+01:00Actually, I think you should be fine defining this...Actually, I think you should be fine defining this puzzle on a 16x16x12 grid. It is true that two of the lock picking pieces are on a finer grid, but because of how the solution works, the coarse grid should capture the workings of the puzzle. Also, I think the "extra 12 solutions" are just the same solution with the lock picking pieces moving in a different order, so really just the same solution.<br /><br />By the way I purchased this puzzle for myself and it is fantastic. Excellent workmanship!!Georgehttps://www.blogger.com/profile/10140920751826036814noreply@blogger.comtag:blogger.com,1999:blog-3341941751324943000.post-79123384195520522632011-06-18T18:08:51.241+01:002011-06-18T18:08:51.241+01:00That's OK, I have 4GB as well and I'm sure...That's OK, I have 4GB as well and I'm sure Andreas knows best ...Georgehttps://www.blogger.com/profile/10140920751826036814noreply@blogger.comtag:blogger.com,1999:blog-3341941751324943000.post-6139574136227973542011-06-18T17:25:04.587+01:002011-06-18T17:25:04.587+01:00I'm not sure whether that's the case, Geor...I'm not sure whether that's the case, George. I would expect that the size of the solve tree only causes a very long duration of solution. The app actually falls over before getting that far - it crashes during the "optimising pieces" stage. Andreas said it was a problem with available memory - I onl have 2Gig. He struggled with 4! I will email you a copy to try for yourself if you like.Kevinhttps://www.blogger.com/profile/05649523779226834414noreply@blogger.comtag:blogger.com,1999:blog-3341941751324943000.post-55764367434523696732011-06-18T17:05:29.402+01:002011-06-18T17:05:29.402+01:00I'm surprised, as BT has worked for me on some...I'm surprised, as BT has worked for me on some quite large files. I have one here on a 51x51x21 grid. Bur I suppose memory consumption is related to the size of the solve tree, not necessarily the grid size.Georgehttps://www.blogger.com/profile/10140920751826036814noreply@blogger.com