GlaireDaggers🍉🏳️‍⚧️🎄

It's like $300 an order

Jesus. Insurance won't pay for any of my Medtronic equipment (beyond just having an "in network discount") cause I haven't met the deductible yet.

Several thousand dollars of deductible left to go.

Healthcare sucks ass dude

Windows 13 rumored to be "collecting hearts released from heartless" in an attempt to open Kingdom Hearts, sources say

But the other thing I like about it is that it does a much better job of documenting *what kinds of errors could happen*

You can attach an enum class error code, and that's a nice handy list of possible conditions built right into the code.

Exceptions? Doc comments is kinda all you get 🤷‍♀️

This is of course very Rust-y but also one of the things I prefer about that way of doing things is that "just ignore the error" becomes impossible as enforced at compile time (even if the way you handle it is just saying "either give me the result or crash")

Something I think I wanna do in Revolver is, as much as possible, eliminate exceptions from the codebase.

- Failures that cannot be reasonably recovered from should just panic and crash as soon as possible
- Failures that can be recovered from should instead return some kind of Result type

Lmao, the US Military got Wile-e-coyote'd

edited screenshot from Codename: ICEMAN Restart? Restore?... At least once more!!! CRAWLING IN MY SKIN THESE WOUNDS THEY WILL NOT HEAL [restore][restart][quit]

MY GAIR

"You crack me up, little buddy"

I know it's hard to compete with the profound unseriousness that is Elon Musk, but god help me if why isn't making a go of it anyway

When I can get around to doing actual game stuff instead of just engine work, I think I'd like to try and make something that's maybe the midpoint between Half Life 1 and Clive Barker's Undying

D&D Animated: It's Not Your Fault! 🦆

#dnd #ttrpg #dnd5e

@cyndervox.bsky.social : "Hazel I think I've come to terms with Grisham's stupid hair"

Me: "His toothpaste hair?"

Cynder: "Stop, it's not toothpaste hair 😭"

Me: "I don't know if you *have* come to terms with it."

Will probably simplify a lot of stuff honestly - no need to handle specific texture flags for water or transparency, that's just part of the material system.

The resource cache has a "RegisterMaterialType" function which is used to basically install material factories for each material type. Right now only used for entity models, but will also be porting over map rendering to use the material system too.

Revolver Engine stuff.

Implemented a material system, & made the mesh loader use it. Very simple, just a JSON file with a "material-type" which indicates which material class should be used (which is responsible for parsing, loading shaders, uploading uniforms, etc).

But yeah like

Single player games NEVER stopped being profitable. When corporations tell you that they're lying through their teeth. It's not that they aren't profitable, it's that they won't make as much money as these companies *think* they can make with live service.

But instead companies keep pulling the plug like .01 nanoseconds after it releases because it didn't immediately make the GDP of a small nation on launch

what's wild is if they were properly supported past launch, a decent number of them could probably be made VERY profitable.

Like

Fortnite is the gold standard, but at launch it did poorly. It was only because Epic stuck with it for a while and tweaked the gameplay formula that it BECAME so big.

well if that was the case wouldn't it be called teethpaste

Basically burns up all of the little stuck coffee grounds & unclogs it like a dream

Well I think I have discovered a hell of a life hack for cleaning out my espresso filters, and that hack is apparently "take out the filter & cook it on the stove for a sec"

Neat benefit of figuring out a more flexible shader system is that with a few tweaks I could probably even make this be more on par with Source 1

- Adding support for FACENORMALS lump for normal/tangent vectors
- Adding lumps for reflection probes
- Directional lightmap fork of ericw-tools maybe?

Frankly kind of just designed for the kind of game where lots of things reuse a small set of common shaders rather than having bespoke shaders on absolutely everything

Not a crazy fully artist driven pipeline like you'd get in Unreal or Godot or whatever, but functional enough for the kinds of games I want to make.

Okay so I think what I'm gonna do instead is make this be code driven - there's a base "Material" class & the idea is each shader has an associated subclass of Material which implements:

- parsing material parameters from the JSON file

- Pushing uniform structs & binding samplers for that shader

*pulling the plug on another game for failing to hook literally every player on earth* "I'm so good at business dude"

"Single player games just aren't profitable anymore" they say, as I watch another live service shut down for falling short of impossibly lofty user metrics