Novus
patreon
Please Excuse the Following Profanity
🕑 Added 2020-01-29 11:26:33 +0000 UTCNo, seriously. Please excuse the following profanity. Most of you probably long since realized that, despite being an adult game maker, I'm actually a rather polite fellow and don't curse much. Heck, I don't even write much crude/obscene language into my games, save for where it REALLY fits. However, if I do not get the following rant out somewhere, I am going to explode and likely murder someone. My apologies, if you skip the bit separated out by -----, you'll skip the worst of it.
---------------------
OH MY FUCKING MORONIC GANDHI RIDING AN ELEPHANT DICK. THE PEOPLE WHO MADE THE NEW ENGINE I'M USING NEED TO BE REPEATEDLY PUNCHED IN THE ANUS BY AN ENRAGED GIANT WITH A CLUB MADE FROM DEFECTIVE FAKE WOODEN DICKS FILLED WITH SPLINTERS. THEN TOSSED INTO A BURNING VAT OF ECSTASY, IN THE MIDDLE OF A GAY TENTACLE MONSTER RAVE.
--------------------
Okay. Okay. I feel slightly better. Just a little. Seriously, typing that actually helped slightly. Very slightly.
Soooooooooo, I started the testing/debugging process for Chastity Quest. 5 minutes in, I realized that, for some god-awful unknown reason of stupid-fuckery, THE STUFF I HAD ALREADY TESTED WAS SPONTANEOUSLY BROKEN, WITHOUT ME CHANGING ANYTHING. Five long, painful, hair-rippingly frustrating hours later, I still don't understand why what I did worked the first time...but now doesn't. I think I found the problem. Maybe. I hope. Please God I hope I did. Unfortunately, it's really hard to tell, since whatever-the-fuck is going on seems to somehow corrupt the entire project whenever it happens. Meaning I would think I had fixed it, put like 2 lines of code I'd stripped out back in, and the whole thing would fucking break again and break in such a way that I had to REDO the previous fix for NO APPARENT REASON. And, why I want horrible things to happen to the developers, has entirely to do with the fact that their debugging tools are NOT user friendly and their documentation was GROSSLY insufficient for me to manually track down the issue.
This left me with a brutal slog of trial and error. I THINK I finally have it figured out. But:
A) If it is the problem I think it is, the developers are FUCKING MORONS for building their engine that way, then NOT DOCUMENTING it in their fucking tutorials.
B) If it is the problem...that I have to fix a GOD AWFUL HORRIBLE number of iterations of the same damn issue through ALL the scenes I've done so far.
FUCK!
Sigh...suffice it to say, that I'm unlikely to add anything else to the build at this point. Not even a couple of extra bit-scenes that I really wanted to squeeze in and figured I'd have time for :-(. This is going to take ALL of tomorrow, easily, just to sort out this one issue. And that was a major bug I found in the first 5 minutes of gameplay, which had already been tested previously and hadn't had a problem. Fuck. This is bringing into question whether I even left myself enough time to get the testing, bug fixing, and grammar check in before the end of the month. I thought I had deliberately given myself wwwwaaaaaayyyy more time than I would need, as a buffer against major issues. Now...well, we'll see >_<. Either way, this is now my primary focus and will be until the first build releases. I do NOT make idle promises and, if I can't get the build out by end of month, it will damn bloody fucking well be out in as few days as possible after that. Even if that means pushing DoL back a few days.
***************
On perhaps the only GOOD news from the day, I've actually gotten a solid start on the Story Reward for the month. I knocked out the first 1,500 words or so before all this exploded in my face. Was planning to do a bit more but now I'm waayyy too pissed. I'm going to go have a strong drink and try to bring my blood pressure back down before I crash for the night/day.
Comments
Novus
:-p yep, that sounds like just about every programming course I took. As the classes got more complex the errors just got weirder...
PaleFlyer
In college for comp sci (not what I ended up finishing in), we were supposed to write a program to write a small file to the drive. We did not intentionally loop it. At first... Yet we created a very large file before we realized what we had created... Then I saw the TA trying to do something with it.
Novus
*shudder* I've never had to actually work on the programming for a debugger. Well, not beyond a basic error-catching system at least. Thank God for that. Best of luck to you, I suspect you'll need it even more than me :-p.
Novus
Yeah. That's part of why, despite having a degree in software design, I HATE programming. I remember a particularly spectacular one in college. We'd been assigned to build an engine from scratch and somehow ended up with an error where removing two BLANK lines from the top of the main cpp resulted in a crash...and putting them back fixed it. Since whitespace characters like that shouldn't affect the code at all, EVERYONE was baffled, even the instructor when we showed him -_-. We never did figure it out, just left the blank spaces there...
Pyros51
I feel your pain... currently trying to get a debugger up and running in work. While we know it is possible (my boss managed it once in one of three test projects 6 months ago...) it is stupidly fiddly and requires small changes to be made in a number of different files throughout the project to actually work even after you configure the debugger itself correctly...
PaleFlyer
As a programmer, all I can say to the "removed 2 lines, it worked, put them back, it died again"... Welcome to being a programmer. Working on code for a customer, works fine, they want something changed. Move one thing, half the code fucking breaks. Move it back, STILL BROKEN.
