FA+
Shop
Ok.... 2 weeks needed an asterix....
10 years ago
Baron: "Ladies, I shall require your assistance."
Lady 1: "Of Course!"
Lady 2: "Anything!"
Lady 3: " Just tell us what to do!"
Baron: "Kindly, be so good, as to remove your knickers."
Lady 1: "Of Course!"
Lady 2: "Anything!"
Lady 3: " Just tell us what to do!"
Baron: "Kindly, be so good, as to remove your knickers."
That game thing I've been working on is *technically* in a working state... in Unity. The problem? Upon building the game to test outside of a development environment, and doing something that is possible, but not required to finish a round of the game, the game locks up and my computer blue screens.
Crap....
Worst part about it is that I have absolutely zero idea what is wrong. I remove the offending part, another bit, that was working perfectly fine by the way, starts causing the same issue. I remove that other piece and bring the original back in, and we get a nice screen full of blue yet again. The weirdest part to me is that when playing it IN unity and not building it, it all works fine. No bugs, no issues, no errors, nothing. I build for PC and test, blue-screen. Build for web-browser and test, blue-screen. It's semi-maddening the way that it is consistently doing this without producing a single error. Especially since the code is almost 1 for 1 with a piece of scripting from the Udemy course I've been taking, and that one has no issues whatsoever in Unity and post-build. The only real differences are a few variable names and the order of where some of the functions are, and that would be mostly due to me trying to code it from near-scratch and memory to reinforce the lessons.
I'm kinda at a loss at the moment over it. About ready to redo the scripts that appear to be causing the issue from scratch. Perhaps round 2 will be better? Or would it be round 3 since this was done in the course? Eh, I'll figure it out. Just wanted to vent some frustrations for a moment and put out a small update.
Crap....
Worst part about it is that I have absolutely zero idea what is wrong. I remove the offending part, another bit, that was working perfectly fine by the way, starts causing the same issue. I remove that other piece and bring the original back in, and we get a nice screen full of blue yet again. The weirdest part to me is that when playing it IN unity and not building it, it all works fine. No bugs, no issues, no errors, nothing. I build for PC and test, blue-screen. Build for web-browser and test, blue-screen. It's semi-maddening the way that it is consistently doing this without producing a single error. Especially since the code is almost 1 for 1 with a piece of scripting from the Udemy course I've been taking, and that one has no issues whatsoever in Unity and post-build. The only real differences are a few variable names and the order of where some of the functions are, and that would be mostly due to me trying to code it from near-scratch and memory to reinforce the lessons.
I'm kinda at a loss at the moment over it. About ready to redo the scripts that appear to be causing the issue from scratch. Perhaps round 2 will be better? Or would it be round 3 since this was done in the course? Eh, I'll figure it out. Just wanted to vent some frustrations for a moment and put out a small update.
