WinterCharmVT ❄️🌨️☕️

Vtuber | Twitch Affiliate | Valo-riety streamer. Wholesome with a nice voice. Come for the vibes, stay for the community.

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

@Crynautica_ @KamiOshiFader W on taking the time and effort to learn such a difficult craft <3

[c r y @Crynautica_]

hello past cry, you can rig your own model now :))

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

@KourraVT Honestly no.

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

And this is why reverse engineering is important. This could help so many vtubers on lower end PCs

[Hoshino Lina / 星乃リナ 🩵 3D Yuri Wedding 2026!!! @Lina_Hoshino]

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.

[Lua Lucky 🌟🐶 @LuaVLucky]

Computational cost for one example:
artmesh, 300 vertices
3 nested warp deformers 20x20 =
360,000 computations

Alternatively:
artmesh, 100 vertices
3 nested warp deformers, 10x10 =
30,000 computations

That's 12x the computations

For Every. Single. Piece.

[Lua Lucky 🌟🐶 @LuaVLucky]

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.

[Ares ⚔️🥀 MYTHOS @AresMythosVT]

New God of War game looks so hype and anyone who’s panties are in a twist over it needs to get a life :)

[Hoshino Lina / 星乃リナ 🩵 3D Yuri Wedding 2026!!! @Lina_Hoshino]

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.

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

@puppkats You have a *lovely* voice XD

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

I need someone with a cute voice to voice act for SnowBot. Does anyone wanna record like 2 hours of audio? (paid).

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

@kuromiyalucien I would love to. Making vtuber friends is so fun ^-^

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

@YamiKibami Giiiirrrllll :3

Okay you're hired.

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

@YamiKibami Haha I was scared to ask, but you were top of the list XD

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

@YamiKibami So is that a yes? XD

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

@O_Hyatsu_4 My god my jaw is on the floor.

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

@alien_mixture Wishing you all the best, and a speedy recovery! <3

[LaurieWired @lauriewired]

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!

[Hoshino Lina / 星乃リナ 🩵 3D Yuri Wedding 2026!!! @Lina_Hoshino]

This is how everyone should do it!

I'm not a rigger but I have daily backups of all my work machines to a local NAS, and biweekly syncs of that data to a hosted server.

Data on the NAS itself is snapshotted daily, and also backed up to the hosted server daily.

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

Microsoft continues to be one of the crappiest companies on the planet.

At least Adobe let CS6 stop working on its own rather than purposely bricking it with a software update.

When you’re **worse than Adobe** it’s time for a reality check.

[The Lunduke Journal @LundukeJournal]

This is outrageous and infuriating.

On July 13, 2026 Microsoft is intentionally bricking Microsoft Office 2019 for Mac.

It's important to note that this is not "Subscription-based Software".

This is purchased software. Mac users bought a "permanent" license for Microsoft Office 2019 (for a one-time price of $149.99), with the understanding that they then can use that software forever.

But, in a little over a month, Microsoft will be putting that purchased software into "reduced functionality mode"... prohibiting all users from creating new documents or editing existing ones.

There is absolutely no excuse for this sort of deeply unethical behavior from @Microsoft.

[WinterCharmVT ❄️🌨️☕️ @WinterCharmVT]

@Lina_Hoshino It’s a long and convoluted process. I spent ages nailing down the design… like 4-6 revisions.