mike

AUTOTOOLS IVE HAD ENOUGH PLEASE SPARE ME

"hey MemoryPool can i have 100mb of memory"
"yeah man whatever ill even make three of them that remain in memory even after the memory owner is disposed"

OF COURSE

here's to 8 more years of input delay

music theory videos are all like "this melody is actually super fucking smart. i can tell exactly what it does. it conveys this precise emotion btw. reminds me of how one guy in the year 6 did it. what a pioneer! i can list every musician ever and all of their works from memory btw

@mike309game.bsky.social you're gonna enjoy dissecting pixel party frame by frame 👀

fucking idiot

@lnx.mephist.net can it sharty

im so glad youtube has implemented a fade effect for the video title when clicking on next videos i was waiting for that for so long it's so incredibly important

WE WERE ROBBED AS FUUUUUUUUUUUUUUUUUUUUUUUUUCK

(not using a vpn mind you)

good job xkeeper

jason citron what are your engineers doing

im way too susceptible to non-gamemaker "developers" ragebaiting by trying to reason how gml code screenshots with no context are bad

ON GOD!!!!!!!!!!!!!!!!!!!!!!!

YOURE TAKING TOO LONG!!!!!!!!!!!!!!!!!!

To anyone who encounters this issue, the patch is just overwriting 4 bytes starting from 0x010789F0 with 48 31 C0 C3

Further details: It dereferences a null ptr @ VerifyD3DTextureSharingCallback; stubbing this method seems to fix it, but I found that shoving xor rax,rax; ret at the start of InitializeVideoDevice also works fine, and *might* let unity know better that something's fucked since it returns 0 normally

UPDATE: I was wrong, it does support dx11, HOWEVER I had to patch the unity player because, for some ungodly reason, it was crashing due to something related to video playback not initialising correctly. But after patching that, for SOME REASON, the border IN SPECIFIC has this extremely weird bug:

15 year old game btw

absolutely fucking appaled that i cannot run the off remaster demo because it was just THAT important to use the absolute latest unity version which happens to exclusively support directx12

SUPERHOT VR had its whole story patched out. I thought about it slightly too long and fell into rabbit hole. It doesn't make sense, it's bad that it happened, and it prompts a whole bunch of naval-gazing about Art.

all phones are fucking cancer

I could ramble on and on longer about mobile apps themselves but, in conclusion:
Maybe if iPhones were less expensive I'd get them for this sole reason. And if they were where they were some four?years ago? I recall hearing good things about them (other than, the inherent issues of being The iPhone)

Then, after ALL that, I have to sit through ANOTHER screen of ""verifying information ☺️☺️☺️"" for SEVERAL minutes. Telling absolutely nothing useful about what it's doing, other than the interface is strikingly similar to the Android update screen.

Surprise, this is once again an illusion of choice, and it continuously asks me for the permissions again, and is only happy when I select all.

Then comes some Samsung bloatware DEMANDING I log in. There's no skip button. So I have no other choice. At some point there's a screen asking for certain permissions, and gives me the option to select which ones I want.

Apparently that's not actually an option because it tells me shit about the carrier and then on a ""verifying information ☺️☺️☺️"" screen it goes "erm something happened.. what could THAT be?"
Needless to say it wanted an internet connection. After that it GLADLY did whatever it needed to.

I hate modern day mobile phones with every single fibre of my being.
My mother got a new phone today, a Samsung one. First thing I see when i boot the phone up is it asking me to OPTIONALLY connect to the wifi, so I tap skip.