mirror of
https://github.com/spice2x/spice2x.github.io.git
synced 2026-09-28 09:48:17 +03:00
Updated PC optimization (markdown)
@@ -151,6 +151,7 @@ If you have no choice but to run on a laptop:
|
||||
* Live2D workload is almost entirely CPU bound; make sure you have a good enough CPU.
|
||||
* It's often solved by turning on XMP in BIOS, if it isn't on already.
|
||||
* Turning off VBS helps a lot as well, just make sure it's *actually* disabled and not just setting some registry keys someone on reddit told you to do. (open Task Manager and look for `Secure System`)
|
||||
* User has reported that shared mode WASAPI patch may also cause FPS drops with heavy Live2D, and was able to resolve by enabling low latency audio setting in spice. It may be worthwhile to try other audio devices (e.g., see if exclusive WASAPI helps).
|
||||
* There are some EA server-side flags that can be toggled that may affect client-side graphics performance (`SUBMONITOR_VSYNC_ENABLE` and `USE_CUDA_VIDEO_PRESENTER`). See [SDVX known issues page](https://github.com/spice2x/spice2x.github.io/wiki/Known-issues#sdvx).
|
||||
* If you're using shared mode WASAPI patch, strongly recommended that you try `Low Latency Shared Audio` option.
|
||||
* If the game locks at the wrong FPS even though you have done everything correct - for example, games launching at 120Hz but the framerate (on the attract screen) is something like 45-50 FPS no matter what you do - try restarting Windows. Sometimes this fixes it. Seems to affect Windows 11 users a lot.
|
||||
|
||||
Reference in New Issue
Block a user