next »

[kiddRaddical]

Using raycasts, caching results in variables of the format [prefix]Out. Must've made a typo, cause my debug log just said:

" 'dOubt' Does not exist in the current context."

Getting personal advice from your debug logs: priceless 

[Eendhoorn]

Just wrote this regular expression to search for lua functions in middleclass classes. It totally looks like zoidberg or some crab guy. I am way too exited about this 

Code:

(\w)+:+(\w*)

[justinfic]

A loooooong time ago (like 2008?ish) I wrote a collision detection system in C++ that takes any two Shape objects, then depending on their subclass, executes a function that checks against those two shapes. It's pretty tight, but I didn't bother implementing every function at the time. Especially the reeeeeally complex ones. Years passed, deeds became legend, legend became myth, blah blah, and I forgot about them.

While trying to debug why two objects with complex shapes weren't hitting each other, I eventually figured maybe my collision detection function was incorrect, and found this as the entire body of the function:

Code:

// HAVE FUN WITH THIS ONE FUCKER AHAHAHAHAHA
return false;

 

[Evan Balster]

That is absolutely glorious, Fic. 

[JobLeonard]

:D

Highly relevant comic

[AlexStv]

Not my code but the Jedi Academy source code was just released and it's full of great comments.

jediAcademy/codemp/qcommon/stringed_ingame.cpp:41:// Yeah, it's hardcoded. I don't give a shit.

jediAcademy/tools/ModView/modviewdoc.cpp:88:void FuckingWellSetTheDocumentNameAndDontBloodyIgnoreMeYouCunt(LPCSTR psDocName)

jediOutcast/codemp/ghoul2/G2_bones.cpp:326:             // why I should need do this Fuck alone knows. But I do.

[Klaim]

A loooooong time ago (like 2008?ish) I wrote a collision detection system in C++ that takes any two Shape objects, then depending on their subclass, executes a function that checks against those two shapes. It's pretty tight, but I didn't bother implementing every function at the time. Especially the reeeeeally complex ones. Years passed, deeds became legend, legend became myth, blah blah, and I forgot about them.

While trying to debug why two objects with complex shapes weren't hitting each other, I eventually figured maybe my collision detection function was incorrect, and found this as the entire body of the function:

Code:

// HAVE FUN WITH THIS ONE FUCKER AHAHAHAHAHA
return false;

 

Hahaha that one is good.

I use a macro for this kind of stuff (UCX_NOT_IMPLMENTED_YET), it generate a debug-break (which generate a crash in release) with the message "NOT IMPLEMENTED YET!!! DO IT NOW!!!!!!!".

I also have a macro for remembering to write a function before compiling:

Code:

/// Use this macro when you just want to remember to implement a function before compiling
#define UCX_DO_IT_NOW       static_assert( false, "NOT IMPLEMENTED : DO IT NOW!" );

[kamac]

Not my code but the Jedi Academy source code was just released and it's full of great comments.

jediAcademy/codemp/qcommon/stringed_ingame.cpp:41:// Yeah, it's hardcoded. I don't give a shit.

jediAcademy/tools/ModView/modviewdoc.cpp:88:void FuckingWellSetTheDocumentNameAndDontBloodyIgnoreMeYouCunt(LPCSTR psDocName)

jediOutcast/codemp/ghoul2/G2_bones.cpp:326:             // why I should need do this Fuck alone knows. But I do.

I downloaded that source to look for a weird bug I had when I was younger and I had been playing JKA. It occured when you:
-Jumped up slightly
-In the air you had to kick in any direction with staff lightsaber
-Then, in the same moment you hit the ground, you had to jump & kick at the same time. That made you jump skyyyy high.

Didn't really find any answer to that 
I guess it's just a dirty bug.

[JobLeonard]

I downloaded that source to look for a weird bug I had when I was younger and I had been playing JKA. It occured when you:
-Jumped up slightly
-In the air you had to kick in any direction with staff lightsaber
-Then, in the same moment you hit the ground, you had to jump & kick at the same time. That made you jump skyyyy high.

Didn't really find any answer to that 
I guess it's just a dirty bug.

Sounds like a floating point divide by near-zero error.

EDIT: The paging, it burnssss!

[kamac]

I downloaded that source to look for a weird bug I had when I was younger and I had been playing JKA. It occured when you:
-Jumped up slightly
-In the air you had to kick in any direction with staff lightsaber
-Then, in the same moment you hit the ground, you had to jump & kick at the same time. That made you jump skyyyy high.

Didn't really find any answer to that 
I guess it's just a dirty bug.

Sounds like a floating point divide by near-zero error.

EDIT: The paging, it burnssss!

Yeah, I thought that the cause might be some division fail.. Namely, there's a division by forceJumpCharge and a timer - by guess I think that when you land and jump right away, one of these is very, very little.

[JobLeonard]

So if you time it correctly you jump sky high, and the suspects are forceJumpCharge and a timer?

Book 'm Danno

[Postmita]

I have laughed at my own code a few time. Recently I discovered that "if" statements only seem to work if you are checking the right variables. Gave me a little relief that I wasn't losing my mind, but also planted some doubt that maybe I was.

[Eigen]

Code:

// Divide into 256 x 256 pieces

int pieceSize = 128;

[BleakProspects]

I just made the most retarded programming decision in my life.

here's the problem:
I have a bunch of different kind of ramps. Basically, each "ramp type" is a combination of whether or not each top vertex of a cube is lowered into a ramp. So there are ~16 ramp types.

Supposing I have a bunch of these ramps all next to each other, how can I efficiently render them without rendering any non-visible faces? Basically, I needed a function that, given two ramps next to each other and a face, returned whether or not the face should be drawn.

After spending a lot of time trying to derive the solution to this problem and running into a bunch of corner cases, I got frustrated, gave up and decided to do it all by brute force. It turns out that combinatorically, this blows up to 784 cases.

So I just made an array that was 784 large. Then I wrote a script to loop through all the cases and prompt me on whether or not to draw the face in that situation. Looks something like this:



The red face is the face in question, and I press "t" or "f" to decide whether or not to draw it. It then loops through every case. The program spits out C# code which then runs in my game and fills the giant array.

After a few runs of this program, I finally made no mistakes and the thing works perfectly.

WTF was I thinking?

[Geti]

Bahahaha awesome Hope it didn't take longer than an hour.

[_Tommo_]

WTF was I thinking?

I... I... Master, please teach us

(but on the other hand it's better than wasting a day to have a "real" solution!)

[JobLeonard]

Quite often, "real" solutions are for when you need general solutions, which kind of misses the point of optimisations.

Like the name of the Processing sketch

[Muz]

I was rushing through testing a file output function. Not wanting to bother finding the folder of my app, I just copied it from another function. Also copied the file name too.

Turns out that I just overriden my main database file with some dummy text. It killed the whole app, but thankfully, it's recoverable. Would've been more amusing if the database was located in the root directory, since I overrode all the root protection stuff to debug faster.

[2DArray]

My line ended with "List.<int[,]>();" and suddenly I feel like I'm typing in Wingdings.

[Belimoth]

If keyboards had wingdings instead of a numpad or something I would enjoy coding with them.
ZODIAC SYMBOLS EVERYWHERE