You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using osu! fullscreen mode during gameplay, the KPS counter becomes very laggy, even if it's entirely visible on a second monitor. This is not related to OBS since the software itself is visibly lagging.
However, on top of things, when using Window capture mode with the Automatic setting, the KPS software causes huge encoding errors for the whole recording. (it is fine when specifying the Windows 10 capture method). This tells me that there could be serious performance issues related to the software when some application is running in fullscreen, if attaching a capture to it causes such instability to OBS.
It is also important to note that the KPS software caused multiple OBS crashes during streaming and/or recording when causing encoding errors.
_kps_encoding.mp4
This was recorded on the latest versions of osu!, OBS (31.0.0) and this software (8.9)
The text was updated successfully, but these errors were encountered:
When using osu! fullscreen mode during gameplay, the KPS counter becomes very laggy, even if it's entirely visible on a second monitor. This is not related to OBS since the software itself is visibly lagging.
However, on top of things, when using Window capture mode with the Automatic setting, the KPS software causes huge encoding errors for the whole recording. (it is fine when specifying the Windows 10 capture method). This tells me that there could be serious performance issues related to the software when some application is running in fullscreen, if attaching a capture to it causes such instability to OBS.
It is also important to note that the KPS software caused multiple OBS crashes during streaming and/or recording when causing encoding errors.
_kps_encoding.mp4
This was recorded on the latest versions of osu!, OBS (31.0.0) and this software (8.9)
The text was updated successfully, but these errors were encountered: