Also, are you allowed to just come out and _say_ "the real monster is Victor Frankenstein"?! How will film critics feel clever when they write their reviews??

I know I'm like 2.5 months late to make this extremely lame joke, I don't care.

My wife has this recurring problem where she starts reading a romance novel and it turns out to be a sci-fi time travel story.

Somehow, inexplicably, I have managed to do the exact opposite.

Okay, this is getting wild already: deadline.com/2025/12/prin...

Also: high likelihood they lose 77 billion bucks trying to push AI-powered glasses, too. Just keep doing what you're doing and refuse to use this shit, we'll get there, too. :)

This also loses the completely functional D3D shader assembler, since most things probably won't use it at this point (but Star Wars: Republic Commando on the Switch did, since it wanted to assemble D3D8 shaders at runtime!)...I might pull that out into a separate library, but it'd take some work.

Is this a high-res mouse or high-dpi display, neither of which were concepts these games would know about in the early 2000s, and thus one happens to mishandle and the other doesn't?

I'm wondering if it's less about how they obtain mouse input and more about what they do with it, though. Is D2 not updating the mouse position every frame? Is the framerate capped in D2 so it feels sluggish vs a real mouse while Throne runs uncapped?

Your choices were basically standard mouse events, DirectInput, or GetCursorPos() and warp the system cursor to the center of the window every frame; from looking at strings in both games binaries, my guess is both use the third method. It was good enough for WinQuake, after all!