Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs

Okay, I sent a zip of that folder to that email address. 

FWIW I couldn't actually get the game to crash on that stage (5x5 1-07), I tried a few dozen times and nothing happened.  Crashing it intentionally seems tricky as just doing one or two move fails repeatedly seems to take a bit longer, although it seems quicker on the bigger, more complicated levels. I had the most luck with 9x9 2-3 doing right turn then forward, on subsequent loads it took 6 tries, 3 tries, 9 tries then first try before crashing.

(1 edit)

Thank you very much!

Unfortunately there does not seem to be any crash data available. 9x9-2-3 is also not yielding a crash for me, and I'm not seeing any evidence that there may be a memory leak.

I will be continuing to look into this, but could you also try out the new [Experimental] Bewildebots_1.4_Windows_x86.zip to see if that fixes the issue? It seems unlikely, but I had seen this was a fix for a Windows 7 crash with an older Radeon GPU in at least one instance.

I've also seen some mention that the AMD Radeon HD 5570 was moved to legacy status and the last driver released for it was Catalyst 15.7.1 (from July 2015) or the beta Crimson 16.2.1 (from Feb 2016). As a result, it's possible the crashes are a result of a driver issue, but that there are no new available drivers due to the GPU's legacy status.

Tried the new experimental build and loaded up 9x9 2-3 and the crashes still persist.

Thank you again for taking the time to try and fix this. That card is old but I've only once previously ran into a legit problem with it, but I would not be surprised if it is the culprit.

Thanks for giving it a try! I'm going to see if I can get Windows 7 and Bewildebots running on an old desktop I have lying around to see if I can at least reproduce the crash and determine whether any useful information is being logged. Once again, I am so sorry you've had to deal with these crashes; I truly feel terrible that this is the experience you've had! Nonetheless I greatly appreciate that you chose to play the game and that you've been able to enjoy what it has to offer!

I had recently started to work on a sequel, though this issue and some insight from a game development podcast I listen to have me strongly considering using some time to work on a mass rewrite of Bewildebots to improve maintainability. I can't make any guarantees about the timeline should I move forward with that decision, or that it would solve the issue, but I would be more than happy to send you an early build to try once the core loop is functional if you would favor potential stability/ability to play without crashes over visual polish. If the issue is tied to Unity 2017.4 or to the specific implementation of the game's logic, then I presume the rewrite should fix the issue.

That is a very generous offer, but as I've generally been knocking out ten puzzles a day as part of my gaming routine (it's like brain exercise, but fun!) if I don't get completely stuck near the end I have about five days left before I finish the full three hundred. Given how close I am to the finish I'd rather not put it on hold for an indefinite period of time, and I'm sure you'd rather potentially take on that level of rewrite without any additional bits of pressure as small as they might be.

That said, if you do get around to that level of rewrite and are curious if this particular crashing issue is resolved or not feel free to reach out to me as I'd be willing to go run into a wall repeatedly for a few minutes to check :)

Sounds great! Just wanted to throw that out there since I wasn't sure what your pacing was. Thank you once again for being so understanding, and best of luck with the rest of those 9x9 puzzles! =)

If you'd be willing, I'd really love to hear your completely unfiltered, brutally honest feedback regarding what you believe the game does well, where you think it falls flat, and anything you'd like to see improved upon or included in a sequel! While I have a lot in mind for the follow-up, I love gathering as much feedback as possible and I don't believe I've been able to pick the brains of any of the few players who have completed all 300 puzzles. I'd also be very interested to know what the time to complete the game was in your stats page if you're open to sharing it, since I've been quite curious to find how accurate or inaccurate my estimate for overall length of the game was.

Sure thing, I'll make sure to collect my thoughts and share them once I finish the remainder of the puzzles!

Thank you! =) 

Okay so ten puzzles a day was a bit of an overestimation on my part as they got rather tricky by the end, but I finally managed to complete all 300 puzzles! The final stats page said it took me 23h: 18m: 17s with an average time/puzzle of 4m:39s, total attempts of 1509 and average attempts/puzzle of 5.03. I have no idea if the freezes I experienced affected that, I tested a few times and it seemed to not affect the time tracking but I didn't really keep close tabs on it.

I started to jot down some thoughts and it was getting rather long, so would you mind if I were to just email it to the address that you listed earlier (or a different one if you'd like) rather than post it all here? It feels like a bit much for a comment thread, but if that is where you'd prefer it I don't really have an issue with it.

I did like it, I can fit that in here easily :) If I didn't I wouldn't have put almost a full day into it.

Congratulations on beating the game! I'm really glad that you enjoyed playing it! Those 9x9 puzzles definitely gave me a fair amount of grief during development, so it's good to hear they weren't a complete cakewalk! 

I had estimated it would take somewhere in the range of 25-35 hours to beat all 300 puzzles, so I'd say that's a great time! 

And email is absolutely fine! =)