From Live2D 5.0 and onwards, I have been encountering CPU spiking in the physics window. These spikes cause very visible slowdowns each time they occur, and they seem to get worse/more noticeable the heavier the model (for example models with lots of physics or a large amount of layers). This was also the case before 5.0, but the level of severity has increased. The spikes/slowdowns were way less noticeable and not much of a problem in 4.2 and earlier.
This CPU reading is taken while I'm constantly moving the model left and right in the physics window.
Here is a video recording of what it looks like when the CPU spikes happen:
https://drive.google.com/file/d/1lBst54crzrjB0CBkPspQxnJig1wtY6Lf/view?usp=sharingI have tested in 5.0.03 beta1 and this behavior is still occurring.
Here is a recorded example, using the Mao (pro version) free model provided by Live2D. I copied and pasted the model parts once as to match a more average model bloat size.
(please skip to around 0:20 for example)
https://drive.google.com/file/d/1oTT3hRx98LKzf5JyAfAcqVJc3XHB4Dl-/view?usp=sharingComputer Specs:
AMD Ryzen 7 3700X 8-Core Processor 3.60 GHz
ASUS TUF GAMING X570-PLUS
NVIDIA GeForce RTX 3070 Ti
2x 32-bit G.Skill DDR4 RAM
Windows 10 64 bit
1 monitor is 1440p 144hz, 2nd monitor is 1080 144hz, 3rd monitor is 1080 60hz.
Comments
Thank you for always using our products.
We apologize for any inconvenience caused.
The cause of this issue is currently unknown.
We'll do some research, but it's likely to take some time.
If you reduce the width of the parameter palette in the physics calculation settings dialog to the minimum and hide it, there may be a slight improvement. (I'm sure you've already tried it...)
Best regards.
https://i.gyazo.com/2c5852236b8c6072bef2c8e83edaa119.png
https://i.gyazo.com/89a95b51d4d79cdb352dd3a2f3f390bb.png
It's odd, hope we can find a solution for this soon, thank you for your help in advance!
Spike happens whether the model is moving or not:
https://drive.google.com/file/d/1O_VNaXcKGyi0s9K7ZTwaAxXzFPD43Cz4/view?usp=sharing
Computer Specs:
B550 Vision D-P
AMD Ryzen 9 5900X 12-Core Processor
GeForce RTX 4080 AERO
2x 32-bit G.Skill DDR4 RAM
Windows 11 64 bit
Monitors:
LG 40WP95C-W
Acer VG271 Pbmiipx
16 gb Ram
Windows 10 pro 64 bit
Geforce gtx 1050
1080p ips monitor
https://drive.google.com/file/d/1FnSR9ApvwLSRICt9ZBAAjLLCmObx15dA/view?usp=sharing
windows 11 pro
R9 7950X3D
96G DDR5 5600
RTX4090
2X 2160p 144hz monitor
Windows Server 2022 (Windows Version 21H2) 64 Bit
Intel i9-9900K (4.7 GHz all core overclock / no AVX Offset)
128GB (4 x 32GB kit) DDR4 3600 MHz (18-22-22-42 XMP default timings enabled)
GeForce GTX 1080 Ti
ASUS Maximus Formula XI (Z390 Chipset)
1 x 3440x1440p Monitor (120 Hz)
2 x 2560x1440p Monitors (60 Hz)
1 x 1920x1080p Monitor (60Hz) - Wacom Cintiq Pro 13
Physics Palette Open
https://1drv.ms/u/s!AqIqzLgNKWJIbdatX7tTHrK5LMM?e=3lo98q
Physics Pallette Closed
https://1drv.ms/u/s!AqIqzLgNKWJIbDZqfwxu_9cwOWE?e=WDwlY2
OS: Windows 10 Home, all Windows updates installed
CPU: AMD Ryzen 7 5800X
RAM: 64GB (32GB x2 @ 3200MHZ)
GPU: NVIDIA GeForce RTX 3070 8GB
Motherboard: TUF GAMING X570-PLUS
1x 2560x1440p Monitor (144 Hz)
1x 1920x1080p Monitor (60 Hz)
Live2D is installed on a 500GB NVME SSD which is 80% full
I've tried the following, which didn't fix the problem:
I've tried disabling Ryzen Master's automatic overclocks of CPU & RAM
I've changed to both default and custom GPU clock speeds via. MSI afterburner
I've updated my BIOS
Windows Server 2019 (Windows Version 1809) 64 Bit
Intel i9-2700K (4.7 GHz all core overclock)
32GB (4 x 8GB kit) DDR3 1600 MHz (CL9 XMP default timings enabled)
GeForce GTX 980 Ti
Asus P8Z77-V PRO (Z77 Chipset)
1 x 3440x1440p Monitor (120 Hz)
2 x 2560x1440p Monitors (60 Hz)
1 x 1920x1080p Monitor (60Hz) - Wacom Cintiq Pro 13
Physics Palette Open
https://1drv.ms/u/s!AqIqzLgNKWJIcuGjr5lUw4G4Jh8?e=mNfqNp
Physics Pallette Closed
https://1drv.ms/u/s!AqIqzLgNKWJIc-Bii-JQPD3HY8Y?e=RgdO4m
CPU - Intel i7 12700k
Graphics - Nvidia 3080 TI
Ram - 32GB (16 x 2) 3600 MHZ
Motherboard - B660l Aurous Pro DDR4
Monitors - 2 1920x1080 60Hz
OS - Windows 10 64bit
@Omega
Thank you for always using our products.
Thank you for trying out the new beta version.
We apologize for any inconvenience caused.
We will continue to investigate for improvements.
Thank you.
We apologize for any inconvenience caused.
Our team continues to investigate this matter.
On the official forum (Japanese version), we received a report that stuttering occurs even when playing animation in the editor.
We would like to confirm whether the problem is the same as the one reported in this topic.
Could you please check if the stutter occurs when playing the animation?
Best regards.
We apologize for any inconvenience this may cause you.
I tested in the animation window, playing the "Floating Mood" animation using the Mao model, following the same steps as I initially mentioned (copying and pasting all parts once). Here is the CPU reading.
It seems that it is spiking in the animation window as well, even when there are no physics. So maybe it shares the same root cause.
Thank you very much for your reply.
Thank you very much for taking the time out of your busy schedule to help us investigate the problem.
It was very helpful to be able to confirm that the problem was likely to be the same as the problem reported by other users.
We will continue to investigate the problem.
I am very sorry for taking so long.
We appreciate your patience as we continue to do our best to respond.
Thank you.
I hope a solution can be found eventually, as it has honestly affected my work ability and increased work time by quite a bit since the move from 4.2 to 5.0 when the issue became more pronounced.
If there's any additional testing I can provide I'd be happy to assist.
It's pretty frustrating dealing with stutter while recording the model in physics tab
CPU - Ryzen 7 5800X
Graphics - Nvidia 1080 TI 11GB
Ram - 32GB (16 x 2) 3000 MHZ
Monitors - 1920x1080 240Hz + 1920x1080 144hz
OS - Windows 10 64bit
We sincerely apologize for the continued inconvenience.
We have been making corrections to improve the situation little by little, but the problem is deep-rooted and we regret that we have not been able to fully resolve it.
We will continue to consider further improvements in the future.