search

Xiexe / XSOverlay-Issue-Tracker

This is a public repository for tracking issues with XSOverlay. There will be no other activity here other than bug reports / feature requests.
10 stars 4 forks source link

Can't controllable white overlay is displayed. #304

Open sim1222 opened 8 months ago

sim1222 commented 8 months ago

Describe the bug in detail: Can't controllable white overlay is displayed. Also a white window appears at my feet image

Provide steps to reproduce the bug: Steps to reproduce the behavior: Start the XSOverlay

Expected behavior: Overlays are displayed.

Output Log: output_log_2023-10-22__00.54.32.txt

Additional Information: This could be a problem on the Windows side. The following command on the PowerShell is solved the problem.

Restart-Service -Name winnat
Xiexe commented 8 months ago

If restarting winnat fixed the issue I'm wondering if you have some other service that was taking port 42070 and 42071?

sim1222 commented 8 months ago

I have no application for using port 42070 and 42071, but Windows says these ports are reserved. I am using WSL and found this Issue now. The problem is very similar to this one and is most likely a problem on the WSL side, not XSOverlay, but I am creating this Issue just to report it. https://github.com/microsoft/WSL/issues/5514

Xiexe commented 8 months ago

You can configure which ports are being used, navigate to InstallDirectory/XSOverlay_Data/StreamingAssets/Plugins/Config

You'll find a config file there. You can change the websocket port. XSOverlay will WebsocketPort and WebsocketPort + 1, so make sure both are available.

sim1222 commented 8 months ago

Your advice fixed the problem. Thank you. For other people, I think it would be better to display this when a port is unavailable.

Hackebein commented 2 months ago

I have this issue since today, too. XSOverlay itself is using port 42070 and 42071 (Verified with netstat -aon). It works magicly after changing ports.

Hackebein commented 2 months ago

I also have this visual issues since: image

I think they relate to it because the solution was to change the port another time. Changing back to the original port always shows the whilte version of the initial post. my 2nd port choise shows always like the broken version from picture above. and my 3th port choise works again.