Things that make you want to smash the keyboard

Into little pieces.

Haha
So as I just spent 4 hours sifting through the scripting reference(this is how it goes for me so far don't know enough yet to write off the top of my head) to try and write something for a sort of prototype level I'm working on. I finally get it so Unity and Visual Studio aren't having a hissy fit only to find out it another script doesn't like it.

So time to toss it out and start all over . UGH!!!

Not so bad really because this is probably a good way to learn what not to do and Im not really all that mad because I made myself look at it that way.
Sort of made me laugh since it has happened before


/end rant

Really don't know what the point to this post was other than to vent to others that might understand since my girlfriend and daughter wouldn't have the slightest clue what I was talking about.

 

Bugs. Other people's bugs.

Not to say that I don't make them myself, but you have to rely on someone else to fix them.

 

Haha... I don't even want to get started.

But thanks for sharing the rant. The community is here to listen and make you feel better

 

When you can't test run your program when there is an error in a script that you are not using, because it happen to come with something you got from the asset store!

 

When unity crash

 

When it works fine in the editor but not in the build.

 

I don't actually get angry with game development. Seems like I would be some sort of idiot incapable of doing my job if I did. It's a machine, I'm responsible for what goes in that machine. Why would I smash keyboard over that as opposed to googling for some answers?

In any case if you're getting angry with game dev, try a different hobby

 

Speaking on my behalf, I face palm myself when the error lays in something so simple, yet I over looked it because I am an idiot... or that's how the machine makes me feel.

 

Having to work on a horribly architectured project and not fix the horrible architecture.

So many people just want to fix what's visible to the end-user and could care less how bad things are under the hood. I was once brought onto a project for a medium-sized game where almost the entirety of the game logic, GUI, input, everything was in a single C# file that was thousands of lines long. Ugh.

 

The thing that drives me crazy is when I'm tired and not thinking and I add a Debug.Log to my code which I thought might throw up one or two messages and instead attempts to print ten million messages to the screen, thereby crashing Unity and losing my work. I just wish Unity had a way of saying 'Please stop printing Debug messages once you've written 1000'...

The other thing that drives me crazy is when I stupidly drag the wrong GameObject to a Prefab, thereby overwriting something that took me ages to get right.

 

Ugh I'm not calling you an idiot or trying to make you feel like one - more trying to express how I feel when I'm doing that and the attitude I use to overcome it... so yeah while I would feel annoyed when I started out, I picture it as just being something logical instead.

(Plus is cheaper on keyboards)

 

Don't take it the wrong way, I'm not saying you're calling me an idiot, I'm just saying that's the way I feel when I was the one who created the problem and the machine is just doing it's job by showing me or telling me I'm an idiot. haha!

 

I don't really understand the tossing it out and starting again comment...

I can get... frustrated with code, but never enough to smash the innocent hardware (which I know will cost me money to replace).

I've heard swearing at the code is free

 

I give my hardest bugs pet names. Shakin' stevens for example pops up to dance whenever there's a movement glitch.

 

your bug names are much more polite than mine... mine usually rhyme with mucking trunt

 

There's a swift and dexterous ducking banker in my game.

 

hate those ducking bankers!

 

Whenever ADB stops Unity from closing, I call it the "all done bug". Well, I actually use a rude b-word and do my best Jesse Pinkman imitation.

 

I think I reserve whispered swearing for the forum more than any actual code.

 

which is worse, programming and working out a bug you've written yourself, or... trying to figure out for an hour why no one can connect to the internet on WIFI... only to find out, you forgot you unplugged the WIFI.

.. that's me.

 

Things that make me want to smash my Keyboard, well actually MOUSE.

This morning I unhooked my mouse and smashed it accrossed the floor - reasoning, a script that was supposed to work, just didn't point blank work.

How does in the update function this not work

if(Input.GetKey(KeyCode.W)){
transform.Translate(Vector3.forward * 12 * Time.deltaTime);

beats me, so i smashed my mouse after an hour and stole my brothers mouse lol.

 

Might help if you make a thread for it, this isn't the place though

 

He needs to get a new mouse, first.

 

oh no I got it working, like 5 minutes after breaking it lol.
I wasn't trying to get help for it, I was just giving off my example to what made me *smash* my mouse instead of Keyboard lol.

 

When a giant spider is on my keyboard.

 

All those spiders are met with deadly force where I live.

 

I was so lost it was ridiculous and I just couldn't figure it out is why I deleted it and started over.

Didn't actually get that mad that I want to break things that will only cause me more problems LOL.
Just annoyed and mostly laughing at myself when I figured out what was wrong.

Turns out starting over is helped since I re did it last night and it works now.
I still have a lot to learn so it actually does help to just start over again sometimes.
Especially when along the way I figure out what was wrong and sometimes find a better way to get it done.


Anyway this thread went way farther than I thought it would thanks for all the reply's.

 

Attempting to do artwork (I'm a programmer).
Creating UIs
Finding that your newly purchased asset has the worst code you've ever seen.

 

re-writing scripts often results in better scripts as you have a better idea what you're doing and what you want the script to do, ending up with cleaner, more structured and concise code.

 

One time, I downloaded this looping audio creation program and attempted to make some background music for my game. I have absolutely no musical ability, and after a few hours I had only succeeded in giving myself a headache. Not handling failure well at all, and with a painful pulse running through my temples, I fell into a terrible rage and passed out. The next thing I remember was waking uncertainly amongst the ruin of my cheap motel room. Where was I? What had I done? My head still hurt, my vision a blur. I closed my eyes and attempted to gain some kind of focus. I reopened my eyes, and as the world began to regain clarity, I noticed the shadows in the periphery of my vision moving and jittering...even though the light from the old battered lamp bolted to the wall above me was steady. Full consciousness returned then, and to my horror, I found myself surrounded by small, leafy humanoids. The were chittering noisily and spattering my still prostrate body with vile amber sap during their careless machinations. Confused, I reached out a tentative finger, hoping it would pass through one of the creatures and confirm that I was still dreaming. I recoiled in pain as the foul creature bit my finger violently. Forcing myself to my feet, I stumbled feebly out of my room and down the hall to a maintenance closet that had been left open. Retrieving a shovel from within, I returned to my room and proceeded to destroy the bothersome creatures, spattering their gooey black innards across the already filthy carpet.

Not sure if that counts.

 

You had me at terrible rage.

 

Lol, slow day at work.

 

One time I went to the chicken shop and they forgot my BBQ sauce, it was rage city... Had to go to the shop and everything, came back my chicken was cold, then had to microwave it and it didn't taste right after.

That was one of the darkest days ever...

 

I think the one main annoying thing I have encountered over and over again is performance... not enough performance to pull of the artistic/creative vision. The usual result is the project has to be scrapped.

 

Incorrect, incomplete, badly written, unstructured or hard to navigate documentation.

Also, user interfaces that seem to guide you away from what you're trying to do.

Finally, third party code which is written, designed (or not designed) such that it's difficult to modify to suit your needs.

None of these make me genuinely want to smash things but groaning, excessive coffee drinking and additional breaks are distinct possibilities.

 

I normally don't smash things, but the other day I had enough.

It bolstered down on two things.

A mouse that had a bad wire and kept cutting off and reloading(for MONTHS DEALING WITH IT) Well it randomly started working GREAT, no problems, finally I thought it was not brain dead, well one morning I wake up, and BOOM, the mouse starts messing up again, I deal with it at first, then when I get on Unity and a basic code that normally works didn't work, I slammed the mouse down quite hard, still didn't fix it, I Ignored it for a moment, tried to deal with code again, still didn't work, so I unplugged it and grabbed the wire and slammed it as hard as I could and watched pieces go everywhere, then went and stole my brothers mouse lol...

The mouse had a good life until the sad end, a good 14 year life lol.
Don't worry it got the proper burial lol.

 

14 years LOL
Sounds like it was time for a new one anyway.

 

One time, I tried to write a shader far beyond my abilities. I turned to the documentation for help.

It didn't end well.

 

Haha I know, I just hate buying something new if I don't need to. It would work, but the second I started dragging the mouse around the wire would come loose I guess (not visually) but it would just cut on and off. lol.