Well...
View attachment 5014796
View attachment 5014797
The game certainly filled up the 2GBs of video memory, but the other 3GBs went into system memory. No lag. No flickering clothing. Kind of anticlimactic, though par for the course for when happens when you're short on video memory - granted for a game on an engine that doesn't need "gaming" level hardware. Also, I'd say that this benchmark was just for fun since you'd only use a 750 Ti with 32GBs of RAM and an i9 if your main GPU died and you have a 750 Ti laying around.
So, to attempt for a more "balanced" configuration: mimicking an 9th Gen Core i3 (4 cores, 4 threads, no hyper-threading), dropped myself down to 16GBs of RAM, and the 750 Ti is still in:
View attachment 5014799
No lag here - still running normally.
Now switching to Intel UHD 630:
View attachment 5014807
...And now we're talking about seconds-per-frame - including turning on Live2D Lite and Low Resolution, setting the image cache to 512 MB, Image Prediction on, and Multithreading disabled. It's safe to say that I found the CPU limitation with this config.
Now still on Intel UHD 630, but giving myself 2 more cores so that I'm mimicking an i5 9600K:
View attachment 5014809
The game is playable and responsive again in the 30 frames range.
And now putting the 750 Ti back in, but mimicking an 9th Gen i3 again.
View attachment 5014871
So, out of the seven system configurations I've tested so far, I've only had significant slow-down with the quad-core, Intel HD and 16GB of RAM configuration. The clothes flickering that Boss and I mentioned seems to be an issue with AMD CPUs based on his laptop and the Steam Deck. Though, the important thing is that video memory, and even having dedicated graphics, is only a part of the story as to why some folks like
Justonemore20 were having issues running this game. And now I wonder what exactly
Dittymyman is working with and if he bothered to try the current version.