catwin @wallhackio@cat.family

i think a lot about the cutscenes in this game and how uncanny the procedural animations look. it's something you just have to get over quickly if you're going to invest in the narrative.

which is a shame because the technology here is impressive and clearly took enormous work to make functional (any character you can make in the character creator works in any cutscene with any armor or clothing! there are cutscenes where the characters models flex their eye muscles to get smiling eyes!!!!)

i wonder if it was really worth it though. it's hard not to compare bg3 to disco elysium (which is more or less this generation's planescape torment). disco elysium sticks to the isometric perspective completely and doesn't really have cutscenes. and it's not distracting, there is much less uncanniness, and it will age spectacularly.

i can't help but feel that it would have been a better use of resources if most dialogue occurred in dialogue trees (keep the voice acting though!!!!!) and then particularly important moments have hand-animated cutscenes

Which of my textbooks should I read next?

I need to finish season 2 of severance now that the finale is out

WHERE. IS THE HOUSE OF GRIEF.

see content warning

you will never, even in a billion years, guess what the #1 entry is for this video
https://www.youtube.com/watch?v=pxOjuqAZOFs

apparently fans have collectively decided that shadowheart's nickname is "shart"

I'm at the point where I can tell you whether something is an lvalue, xvalue, or prvalue but i still don't understand why xvalue needed to be introduced.

this game is fucking long as shit

cofee

finally killed that smug piece of shit gortash. really enjoyed how they handled karlach's reaction to it, fantastic stuff.

so glad i am finished with my hobby (work) so i can go back to doing my job (playing baldur's gate 3)

For C++ saying that lvalues are things on which the & operator doesn't throw (and rvalue are things which cause & to throw) is slightly incorrect. After checking the official specification for the language there is a thing called a "qualified-id" that & can operate on, and there is a case where a qualified-id can be a rvalue.

in celebration of world frog day:
https://x.com/blephin_/status/1902179800480882710

oh that's a 60mph wind extreme weather warning for my city tonight. neat.

what if you had a language that passed all variables by value instead of by reference meaning that declarative passing of objects to other functions results in often-expensive copy operations for the arguments to and return value of each function call. so we use pointers for everything. except explicit pointer logic is extremely error prone so instead we should use objects which handle the pointer logic for us. also we need to invent references, which are like pointers but they're different, and add implicit conversion of objects to their references to the 1998 update to the language specification so you can pass these wrapper objects to functions without copies now. but also we need to invent rvalue references so you can pass rvalues to functions as well. btw do you know what an rvalue is? oops wait, these rvalue references so happen to fuck the taxonomy of value categories for the language so now you need to know what an xvalue is teehee

All of this fucking value category bullshit only to realize that the reference operator (&) is valid for lvalues and throws when used on rvalues. This is a valid definition.