Hey Yall.
due to some ridiculous ass situation idek how to START explaining, my bank account has been closed because of some scammer/hacker in Nevada
My rent is due tomorrow and Chase still has my entire rent payment, which they are going to mail to me in 5-10 business days 1/4
@vexmlk@PayPal Time for NSFW artists to start taking payment in Ethereum.
The banks and payment processors pulling this bs are absolutely ridiculous in their moral policing.
One of the things I want to write after I reverse engineer moc3 is an automatic model optimizer.
It is absolutely possible to mathematically compute error bounds and automatically remove vertices and reduce deformer precision in ways which minimize rendering differences.
Hot Live2D take: It seems like most live2D riggers are not attempting in ANY way to optimize their models, ex. lowering warp deformer density, minimizing vertices on artmeshes, and it's really hurting your clients.
Wait uhhh VTube Studio for macOS is still built for Intel only, no ARM64/Apple Silicon build???
That's... even more reason to reverse engineer MOC3 and make sure we have alternatives... oof.
RAM exists as a 1-dimensional space. For programming…that’s kind of irritating.
All the important math happens in 2D arrays.
It’s simple(ish) to compress a higher level space into a single dimension (most languages today are row-major), but there’s a funny quirk.
At the *physical* DRAM layer, the actual bits *are* stored in a 2D array, rows and columns. (…well, when you add up all the layers, it’s more like a hierarchy of 2D arrays, but you get my point).
If this information was directly exposed to you…gosh there are all sorts of neat tricks you can get away with!
Unfortunately, keeping memory addresses in a 1-D space makes things much simpler from the OS perspective for memory management, not to mention code portability. There are nasty security problems too...certainly some valid reasons for keeping physical structure hidden.
Yet, think of how much of performance engineering / memory locality work could be shortcutted if it were trivial to understand the exact physical layout of how your arrays were stored!