Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Alt text: In the 60s, Marvin Minsky assigned a couple of undergrads to spend the summer programming a computer to use a camera to identify objects in a scene. He figured they'd have the problem solved by the end of the summer. Half a century later, we're still working on it.
Edit: seems I'm the third person to comment this! :')
I love how this is actually an example of progress. These days, ML can be used for this kinda thing and it's not too bad at it even.
https://code.flickr.net/2014/10/20/introducing-flickr-park-or-bird/
This page about it still exists, but I guess the identification site died with Flickr.
Only in 3D. In 2D, you slap some pixels on top and there's your scarf:
I tend to find it's the other way around. Once you've got a scarf modelled and rigged, it'll work* for all animations, but for animated 2D sprites you have a lot more things to do.
* May have visual artifacts like clipping
and add a couple of frames to the sprite sheet in order to animate the scarf if that's required.
Sure. Player character? No.
There’s already a codebase for bursting from the ground in an explosion of lava. Everyone wants that.
You’re the first person asking for a scarf, and our system doesn’t even know what a neck is.
Time for the old NPC-with-a-train-for-a-hat trick.
Player? Easy. Scarf? Easy. Wearing a scarf? That depends on a lot of factors such as which part of the body, how the models were made and rigged, etc.
And if it like blows in the wind that's a whole jigglebone system and wind simulation that's a lot of stuff going on
Way back in the 90s I did a contract job at MS Research on a project called "V-Worlds" - a world simulator similar to the Doom or Quake engine, but it was browser-based and everything was a script, so changing how the world worked didn't mean you had to restart a server, just change the scripts and new stuff would appear right in front of you.
Anyway the concept of adding accessories to the player's avatar and even having a pet follow you around came up, and I remember there was an involved discussion of how difficult/impossible that would be. The player's avatar was a special object class that represented a user, and didn't have the same capabilities as ordinary objects in the world. I remember asking, "Why isn't the avatar just a world object the player happens to control? Then you could do all kinds of cool stuff like let the player transform into something else just by switching objects, or let another player run your character." Dead silence. I was just a contractor, what did I know?
This feels like the kinda project that should have a 1hr YouTube indie doc about it
I wouldn't mind seeing that! After V-Worlds was declared "completed" MSR tried to find a product group to fold it into, but nobody wanted to own it. I don't remember if XBox existed then, but the code just sat there for a few years, then I heard they opensourced it. When my kids were playing ToonTown I found a bug that let you slide behind the background and move around, like you could see that a clerk behind a counter was just a legless floating torso. The method of getting there seemed to be exactly like a V-Worlds bug, so I wondered if Disney might have been using the code. But it could have just been a common graphics bug, I dunno.
I remember finding another bug while creating a demo with a snaky sea creature swimming around. To animate a multi-segmented object you had to animate each segment separately. After the animation ran for a minute or two, enough unrelated interrupts would happen in the computer that would throw the body parts out of sync, making body parts either merge into each other or move apart, and the whole thing would look like crap. Same thing if you had somebody ride in a car or on a train - the car and character were animated separately and you'd end up with the character floating along behind the car.
I asked the dev about making the animation itself an abstract object whose position would be moved around, and attaching in-world objects to it, with position offsets. Each animation step would be computed just once instead of for each body part (or for the person and the car), and all the parts would be rendered with offsets from that one position, guaranteeing them to stay in sync visually. He said yeah that's a good idea, but we're not working on that code anymore. Oh well.
Another bug involved moving from room to room. The engine only loaded graphics for the current room, so when you went through a doorway it would load the new room and dump the previous one, causing a very unnatural visual delay that looked like a glitch in the matrix. The way we coped with this was by putting an entire world in a single room, so all the world's graphics were loaded all at once. But this not only limited the world size, it meant we had to create our own version of the room system in script. To keep track of where players and objects were, we put invisible barriers in doorways and used event handlers when things passed through them. Then we used this to enforce which players could talk to each other or hear sounds made in a given "room".
I suggested loading a cluster of rooms at once - the current one and those that were one connection away. Then when an avatar passed into a doorway the new room's graphics would already be there, no glitch, and the graphics for nearby rooms could be loaded and unloaded in the background. Again, nice idea but we're done working on that code. Sigh. I really wish I had joined that project about 6 months sooner. Not like I'm a genius or anything but these seemed like really fundamental things that should have been addressed up front.
Okay, rant over. I haven't thought about this stuff in quite a while - I'm kind of amazed so many details are still in my head. I must have agonized over it a lot at the time lol.
Game director : we’re gonna add interact-able doors with proper door opening animations for the characters
The game designers:
The programmers and artists:
The producers:
Legend of Zelda did it well.
Honestly, I think a major issue with doors is that they just slow down gameplay.
It's like coming across a ladder only every building has one.
Almost all game-slowing doors are just hidden loading screen baked into the gameplay.
Now we need to decide in the case of collisions if:
The frustratingly comedic unintended results of any choice makes for great organic marketing though.
Gamedev is magical.
Aside: Know what did this really well though? Resident Evil games after RE:4.
The ability to "slowly quietly open", and then at any time decide to violently action-hero kick it open to send a zombie on the other side flying, was genius.
FROM Software: Fuck that, we're doing fog-walls.
There's an XKCD comic for that.
Well yeah, we have a character model for the giant demon and the giant demon has a huge use case.
A scarf? That's a model extension. Either you're asking me to create a whole new character with a scarf baked into the mesh that will deform weirdly as the character moves, or you're asking me to implement an accessory-anchor system all for the sake of a scarf (albeit other accessories might use this new framework) which will then need a physics/cloth sim to even look half good.
Always have to remind myself of this when managers ask me if something could be done. If it's easy, I naturally get a little annoyed that they're even asking. But knowing that is my job, not theirs, and it's good that they ask. There's lots of places where they assume and things go badly.
Remember the phrase "it's not in-pattern". Another one is "it's possible, but expensive"
I want dresses, and I don't care if they clip through literally everything!
My bg3 character is female. She was in slacks until act 3 where she could finally have a dress
We looted everything. I feel like there are two dresses in the game: the robe Gale wears and a white dress you find in a Balders Gate house near the end of the game