Pixel Streaming Mouse/ The mouse remains invisible

Hello everyone,

Maybe you can help me.

When I open the Pixel Streaming project locally in the browser, the mouse does not appear in the widget.

The level blueprint “Set Input Mode UI Only” works well in gameplay, but unfortunately, it has no effect in the browser.
The “Enable Mouse Over Events” blueprint also does not work.
If I set “Hovering Mouse” in the Pixel Streaming Browser Settings UI, the mouse remains visible all the time, but it should only be visible when the widgets are called.
I have tried various settings in “Project Settings” (Pixel Streamer Default Cursor Class Name to “DefaultCursor” or ‘None’), but unfortunately, nothing works.
The mouse remains invisible.

It can’t be that difficult, can it? :slight_smile:

Hi there!

Unfortunately, there isn’t an “out of the box” solution to this issue. However incorporating your own fix is possible!

To achieve the function you want, you would need to modify the frontend WebRTCPlayerController.ts as found here:

You could modify the “OnCommand” function to handle receiving new commands, perhaps a command called “showCursor”. Then modify your blueprints to send this new command whenever you want to toggle the mouse cursor.

I hope this helps put you on the right track! Please let me know if you had any further questions.

Kind Regards,

Michael Wallace

1 Like

Thank you very much for the solution approach. I will definitely try it, but unfortunately, I am not a trained programmer, so it will probably take me a bit longer :slight_smile:

I have looked at TensorWorks’ website, and their projects are impressive! What might a solution cost, i.e., script lines in WebRTCPlayerController.ts and the associated Blueprints, to solve the problem?

Thank you for checking us out! You’re very kind.

Regarding a solution to the issue, what may be worthwhile is creating an issue ticket on the Pixel Streaming Infrastructure here: GitHub - EpicGamesExt/PixelStreamingInfrastructure: The official Pixel Streaming servers and frontend.

If issues are small enough and benefit the Pixel Streaming community as a whole, we often try to fix issues there. Please feel free to create a ticket there and we can have a sticky beak at the problem!

Thank you for the interesting solution approach! I will try it out. In the meantime, I have found a simple solution, thanks to MWillWallT :slight_smile:

3 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.