Hide system cursor

[FadiNahhas]

Is your feature request related to a problem? Please describe.
Platform: Windows 11
Currently the cursor that gets added by Recordly is not perfectly aligned with the system cursor (especially with smoothing). Visually it doesn't look good when two cursors are visible.
I noticed that if I adjust cursor settings, it snaps back to the actual cursor's position. But when I resume it lacks behind again.

Describe the solution you'd like
Instead of turning off Recordly's smoothed cusror which has the click effects too. It would be better if the system's cursor can be turned off or replace and smoothed.

1. Record screen without cursor while tracking cursor position throughout the recording
2. Get to choose to use real cursor movement, smoothed cursor, and whether to use the system visuals or custom one.
   Additional setting: choose whether the custom cursor changes based on context or remains as the default style.

Describe alternatives you've considered
Can't really think of a different method to achieve the same result. The on described above is the most straight-forward approach.

Additional context

[FadiNahhas]

Testing with the latest version I'm getting this error
Even when running as admin

[webadderall]

Javascript error should be fixed, let me know if the two cursor issue persists. Have you tried disabling your custom cursor and seeing if anything changes?

[tokenflow1m]

The two cursors being visible at the same time should be fixed in v1.0.8+ with WGC capture, which records without the OS cursor.

The smoothing lag is a separate issue. Even with the system cursor hidden, the rendered cursor still trails behind the actual position because of smoothing, so click effects can appear before the cursor visually arrives. One way to fix this is to apply a negative time offset to the cursor telemetry lookup, shifting the rendered cursor slightly ahead to compensate for the smoothing delay.

[webadderall]

Closing as issue seems to be resolved

[FadiNahhas]

@webadderall @tokenflow1m
I just installed 1.0.9, and the system cursor remains. There is noticeable improvement in the custom cursor tracking.
I also noticed another bug, the editor breaks after exporting.

[webadderall]

Are you using a custom cursor application? Can you try disabling it and seeing if the cursor gets hidden?

[webadderall]

This cursor looks like it may be rendered as part of a website.

[FadiNahhas]

That's just a custom Windows cursor. Not using any 3rd party application

[webadderall]

What version of windows is this? 10 Build 19041 (May 2020) or newer?

[FadiNahhas]

Windows 11 Pro
25H2
Build: 26200.8037

[webadderall]

Do you have Windows Graphics Capture installed or supported on your system? Are you running a VM? Could you give more hardware details?

[FadiNahhas]

1. Yes, Windows Graphics Capture is supported. I'm on the latest version of Windows 11
2. No, it's not running in a VM
   System Specs:
   Intel Core i7-14700KF
   RTX 5070
   32GB RAM

I will install the latest version of Recordly and test again.

UPDATE:
I just tested v1.1.0.
The issue persists, I can only hide the custom cursor. If I set smoothing to 0, it still lacks behind just a tiny bit so I can still see both cursors.

[pierrejacquet]

Hi I have the same issue. No VM, windows 11, last version downloaded this morning :)

[webadderall]

Does anyone have this issue on Windows 10?

[webadderall]

I'm going to release a build that will toast an error if it's using the electron capture path that causes duplicate cursors.

[webadderall]

It seems to be an issue with Window's WGC API itself, I'll try to code a workaround

[webadderall]

If anyone wants to help, they can. I've made a commit "feat(windows): replace WGC with DXGI and fix HUD window bounds", if someone could test on Windows to see if it resolves the issue that would be very nice.

[QBoulanger]

Just tested it, i still have the issue, but I actually got the toasted error: "Native Windows Capture (WGC) is unavailable. Falling back to browser capture."

[FadiNahhas]

Same issue, Native Windows Capture (WGC) is unavailable. Falling back to browser capture.

[FadiNahhas]

I cloned the repo and managed to fix the cursor issue. But I had to make changes to the Visual Studio version config to get npm install and run the dev server on my machine.

I'll open a PR, but you might wanna migrate the relevant changes and test with your version of VS

[webadderall]

Migrated relevant changes and pushed, can somebody test on Windows to see if Windows cursor is hidden now with Selective merge of Windows system cursor fix #66?

[FadiNahhas]

If it's building on your machine could you publish another release with the fixes?
I tried cloning to test, getting Wasapi Capture errors

error C2039: 'pause': is not a member of 'WasapiCapture'
error C2039: 'resume': is not a member of 'WasapiCapture'

[louayhouimli]

Yes please publish a release

[webadderall]

v1.1.3 should appear in a few minutes, someone tell me if it works 🙏

[pierrejacquet]

v1.1.3 should appear in a few minutes, someone tell me if it works 🙏

It seems to have fixed it for me :) !

[webadderall]

Issue resolved

[webadderall]

I've also heard reports that the smoothened cursor on Windows seems to lag behind, anyone experiencing it?

[ranggasan]

I've also heard reports that the smoothened cursor on Windows seems to lag behind, anyone experiencing it?

Yes, I can confirm it, the cursor movement is lag behind

[webadderall]

Are you experiencing this in the latest version?

[ranggasan]

Yes, I'm using the latest version (1.1.3)

[webadderall]

Have you tried turning on "Optimizations for windowed games"?

[ranggasan]

"Optimizations for windowed games" is already enabled

[pierrejacquet]

The problem I have (may be unrelated) is that cropping window / video seems to offset the cursor position / or the cursor position is relative to the window size but not to the original video positionning.

[webadderall]

You do experience the cursor lag too, right? Or is it just this problem?

[webadderall]

#72 Any help would be appreciated

The problem I have (may be unrelated) is that cropping window / video seems to offset the cursor position / or the cursor position is relative to the window size but not to the original video positionning.

I'll fix this