sta / sta/websocket-sharp

UE4: Client receive only an one message after connection and then receive always empty messages

Open
#505 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
6.1k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

I trying to work with websocket from unreal. And i dont understand what is going wrong when i try to exchange messages.

I use it with this UE4Websocket samples https://github.com/feixuwu/UEWebsocket .

I tried a simple thing: say to a server from a client a simple message like "HelloWorld" but the client recieve as echo only first message as "HelloWorld". Other messages were empty.

I also tried "Fleck" (name of the websocket system) and there an echo work was ok.

What is can be causes of this problem?
I debbuged the sending routine and i really dont saw any different cases in the first\second message sending routine. Also if i close the connection and already open the connection - the next first message will be ok. Maybe some connections information somewhere marked as "dirty" and wait for some message from a client?
Also if that will usefull - messages from a client is ok always.
Also i've tried this case: client connected to a server, and the server send to a client what i wrote in the console. First message is always OK, next - empty.

Can you help me or give me some advice please? Thank you!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked UE4Websocket samples and compare the first and subsequent message paths in the sending routine. Reproduce the echo behavior with the Unreal client and websocket-sharp, then determine why later server messages are empty; done means repeated messages are received correctly without reconnecting.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, unreal-engine
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.