Repository navigation
OpenVT rendering OpenSeeFace stuff very slowly #45
Answered
by
erodozer
FlyingSaturn
asked this question in
Q&A
|
Facetracker is perfectly set up. However, the face movement that works instantly in vtube studio, is running on 1FPS on OpenVT. Also, the CPU load of OpenVT and Python3 are a lot, taking more than 1 core each. Couldn't see the OpenSeeFace stuff in log, but in case one needs it, here are the logs: |
Answered by
erodozer
Oct 18, 2026
Replies: 1 comment
|
Hi, your hardware is a bit below what I usually test against, so I spent some time tonight profiling to see what were the most CPU intensive areas that I could try to clean up. From testing on my R5 5600X, I was able to reclaim almost 7ms of CPU time on average per frame, going from 10ms to 3.5ms, by simply avoiding any UI updates within the blueprint system while it's off screen. Of course this means when the blueprints are visible you can expect FPS to drop again, so try not to forget about the popup. The change has already been pushed, the next nightly release will include it. |
0 replies
Answer selected by
erodozer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, your hardware is a bit below what I usually test against, so I spent some time tonight profiling to see what were the most CPU intensive areas that I could try to clean up. From testing on my R5 5600X, I was able to reclaim almost 7ms of CPU time on average per frame, going from 10ms to 3.5ms, by simply avoiding any UI updates within the blueprint system while it's off screen. Of course this means when the blueprints are visible you can expect FPS to drop again, so try not to forget about the popup.
The change has already been pushed, the next nightly release will include it.