Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPU rendering drops clients when they look at GPU connected screen. #346

Open
murm9000 opened this issue Nov 2, 2024 · 1 comment
Open
Labels
bug Something isn't working

Comments

@murm9000
Copy link

murm9000 commented Nov 2, 2024

Hosting a local game, 1 friend connected.

When a connected client looks at a ScreenDriver (Screen Tab), Screen Module, or Large Screen, bound to a GPU, it causes the client to immediately get dropped from the host. Host is unaffected.

To Reproduce
Steps to reproduce the behavior:

  1. Build Computer: 1xCPU, 6xRAM, 1xScreenDriver, 1xGPU
  2. Build Panel: 1xScreen Module or Build Large Screen
  3. Connect Computer, Panel or Large Screen, to Network Wall Plug
  4. Use this code: https://docs.ficsit.app/ficsit-networks/latest/lua/examples/paint.html
  5. Have client connect, and look at or attempt to interact with the Screen Tab, Screen Module or Large Screen (whichever is bound to the GPU)

Expected behavior
Client should be able to interact with Screen Tab, Screen Module, or Large Screen without being disconnected in the same manner the Host can.

Additional context

  • Using latest FicsIt-Networks release 0.3.24
  • Tried setting the size of the screen, using :setSize() to different sizes, all lower than 150x50 to no avail.
  • Tried deleting ScreenDriver and using external screens (Screen Module and Large Screen), same issue.
@murm9000 murm9000 changed the title GPU rendering drops clients when they look at connected screen. GPU rendering drops clients when they look at GPU connected screen. Nov 2, 2024
@Panakotta00 Panakotta00 added the bug Something isn't working label Nov 4, 2024
@Panakotta00
Copy link
Owner

This issue will sadly have to stay here for a longer time.
The only way of mitigating this issue would be to change your "Network Quality" settings (up and down, both could make it better or worse).
And ultimately a better network connection could help. If thats still then case I'm sorry but there is not much else I can do.
Another reccomendation would be, if you use many screens, refrain from high refresh rates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Open
Development

No branches or pull requests

2 participants