【Early Release】Script for an Upcoming YouTube Video (Patreon)
Content
Sorry (´;ω;`)
My health hasn't been great, so I couldn't finish this month's Patreon article in time, so I'm releasing the script for an upcoming video early instead.I hope this can be of some help to you.
【Shocking Discovery】The Real Reason a 100,000-Polygon Ultra-Heavy Live2D Model Was Stuttering Wasn't File Size 【nizima LIVE Investigation】
First, take a look at this.This is how Himono has been moving for the past several months, And this is how Himono moves now.
Wow, that's an incredible difference compared to before, right?Looking back, Himono's movement a few months ago was way too choppy, wasn't it??I can't believe I was streaming like that lol
So, hello, everyone! I'm Himono, a Live2D modeler and virtual YouTuber!
What do you think of this? How about this smooth movement? This is Smooth Himono!
...Smooth Himono sounds kind of contradictory...
As I've mentioned a few times in nizima LIVE's PR videos, one of the great things about nizima LIVE is how lightweight the app is. True to that, the nizima LIVE app is so lightweight that, even when streaming with multiple apps running at once, my PC always has plenty of processing power left over.
However, my model was moving so choppily that viewers kept commenting, "Isn't that too stuttery?"As I've mentioned, my model has 100,000 polygons and over 200 mask ID permutations, which is an absurd file size, equivalent to about three to five high-range-of-motion models combined.
So, no matter how lightweight the app itself is, my model's file size is just too monstrous, right? The choppiness can't be helped, right? I'd resigned myself to that and kept streaming anyway.
But then. At one point I tried moving a sample model, and it was stuttering just as much.
Wait? So this isn't caused solely by the model's heaviness??
That thought led me to research various things, and the result is the comparison video I showed earlier.Actually, between before and after, I made zero reductions to the file size.Yes, in other words: "The main reason Himono's model was stuttering wasn't actually the model's massive file size" This is the shocking fact that has now come to light...
So this time's theme is "Improving FPS in nizima LIVE"!FPS stands for Frames Per Second, a value representing how many times the image updates per second. By the way, first-person shooter game genres like Apex are also abbreviated as FPS, but that stands for First Person Shooter, so it's a different meaning. (I only learned this while researching for this video lol)
As a Live2D tip, this is an extremely niche theme, but I thought it might be helpful if any nizima LIVE users watching this channel are struggling with similar stuttering issues, and also I simply enjoy this kind of detailed investigation, so this time I want to make a new video as part of a "Live2D Investigation Series."
So, here are the 4 methods that were effective for improving FPS!
① Higher GPU Prioritization② Set Mask Texture Size to "Fit to Window"③ Turn OFF Virtual Camera④ Use Spout2 instead of the OBS Plugin
Before explaining each item, regarding how I measured FPS - this time I didn't use any external FPS-measuring apps at all.Instead I used the rather analog method of: record with OBS → import the recording into Premiere Pro → cut out 1 second → place markers wherever the movement changed and count them. It was a brute-force approach, but it turned out to be surprisingly easy to understand.
First, using this measurement method, I measured footage with none of settings ①-④ applied.
The result was a shocking "12"! For those unfamiliar, this number's severity might not hit home immediately, but the FPS standard for recent games and video is often 60. This means "the image switches 60 times per second." At this rate, the human brain perceives it as "wow, that's moving smoothly~". This time's final goal is also this 60 FPS. Compared to that, my model was at 12 FPS. That's one-fifth of the number at which humans perceive "smooth movement." A flipbook might move better than that.
Realizing there was no way to properly record video like this, I went through various trial and error changing settings, and arrived at the 4 items I mentioned earlier.
Let's go through them one by one!
① Higher GPU Prioritization
In nizima LIVE's "Option" → "Graphics," there's an item called "Higher GPU Prioritization" As the name suggests, this is a setting that says "raise the priority of nizima LIVE's GPU processing."
Compared to items ②-④ which I'll explain next, the effect is smaller, but it still reliably raises the FPS.
Comparing all-OFF versus only ① turned ON looks like this. The number itself doesn't change from 12 with just this, but you can see the frame intervals shrink slightly. With all of ①-④ turned ON versus only ① turned OFF, the number itself changes too. The more the numbers have improved from other settings, the more noticeable this effect becomes.
Unfortunately, this setting might not appear depending on your PC's specs. Conversely, an even stronger setting like "Even higher GPU Prioritization" might appear instead.If these settings are displayed and your PC has spec headroom, definitely turn it ON!
② Set Mask Texture Size to "Fit to Window"
This is also a setting item found under "Option" → "Graphics." You can set how clean the clipping mask boundaries look. The smaller the value here, and the more/larger the clipping masks you're using, the blurrier the boundaries become.
As I mentioned at the beginning, my model has over 200 mask ID permutations. So a few months ago, I had this set to the maximum value of 16384×16384. Here's the result!!
It's way too choppy no matter how you look at it, but then again, if you lower the number, the mask boundaries get blurry, and I was racking my brain over what to do - until I realized that simply changing it to "Fit to Window" dramatically improved both problems at once, and I remember being floored by it. (I actually tweeted about this on my sub account at the time.)
Here are the measurement results with ② toggled ON/OFF! I really wish I'd noticed this sooner... (´;ω;`)
③ Turn OFF Virtual Camera
Virtual Camera is a feature that outputs nizima LIVE's video as a webcam feed to other apps. It's a convenient feature when you want to use nizima LIVE's footage in Discord, Zoom, and similar apps!
Thankfully, I've recently been doing more guest lectures and seminar appearances, often using this Virtual Camera feature in external apps like Zoom, so I'd been leaving it ON all the time as a habit.
However, it turns out this Virtual Camera officially outputs at 30 FPS by specification. Furthermore, whether it's spec or a bug, I'm not sure, but in my environment, simply having the Virtual Camera turned ON was also dragging down nizima LIVE's own movement to below 30 FPS...
It seems best to diligently turn it OFF except when you absolutely need to use the Virtual Camera! If the Virtual Camera could also be made to support 60 FPS, I'd really love to see that in a future update...!
④ Use Spout2 instead of the OBS Plugin
Last one. This item might be the most relevant for streamers.
Currently, there are 2 ways to display nizima LIVE's footage in OBS: "capturing directly with Window Capture or Game Capture" or "using an external plugin." The former has downsides like the UI showing up or accidentally capturing a different tab, so the recommended method is using an external plugin.
Among external plugins, there are also 2 types: "OBS Plugin" and "Spout2," and I had been using the OBS Plugin.
But sadly, between "OBS Plugin" and "Spout2," "Spout2" is overwhelmingly lighter... I really wish I'd noticed this sooner too.
Here are the measurement results comparing the two plugins. It's completely different...
Actually, the fact that Spout2 is lighter than the OBS Plugin is properly written (though quietly) in nizima LIVE's manual. You really do need to properly read the manual!!!!!
That's all the improvement items! Doing all of them versus doing none of them makes this much of a difference in FPS. It's a genuinely frightening difference. Let me say again, in this before-and-after, the model's file size didn't change at all.
Over these past several months, I've continued updating my model for further evolution, but I'd hit a wall - not one of technical skill or man-hours, but the numerical wall of "FPS" - and I was feeling down thinking "maybe I really can't keep building out this model any further due to these constraints..." so this was truly a happy surprise (´;ω;`) This means I can keep creating! So glad!!
This is strictly the result of investigation on my own PC and model, but if anyone out there is struggling with a similar issue, I'd be happy if this could be even a little bit helpful ✨
Going forward, whenever I find an interesting theme, I'd like to keep making videos as part of the "Live2D Investigation Series"!If any of you have topics or requests you'd like me to investigate, please feel free to leave a comment! And if you found this video helpful or interesting, I'd really appreciate a like and subscribe 🥰
See you all in the next video! This was Himono! Bye-bye!