Can't launch local Replication server outside of editor

Description, details and error message(s)

I wanted to try the Steam sample for a little project I’m working on.
Downloaded it, used it in editor no problem. Made a build to use on my second computer, join the editor hosted lobby also no problem.
And then I tried the other way around but I can’t launch the replication server with the build version.
I verified the settings to bundle the replication server et verified the dll in the build all seems fine.
I made no code modification, the only change is the Steam App Id

Error logs :

SteamManager: CoherenceBridge connection error 	Exception=Coherence.Connection.ConnectionException: No connection could be established because the target computer expressly refused it.
SteamManager: Replication server exited with code -100.

After some digging I found the enum NLError in the InteropAPI

public enum NlError
        {
            InvalidVal = -100,
            TimedOut = -101,
            Pipe = -102,
            WouldBlock = -103,
        }

Don’t know if it’s this error exactly.
Thanks for the help !

Expected behaviour

It should be possible to host a game in a fresh downloaded steam sample with a build without errors.

Screenshots

How to reproduce

Rate: Every time

Steps:

  1. Download Steam Sample
  2. Import in Unity Hub
  3. Convert to Unity 6
  4. Open Project
  5. Change Steam App to a working one (480 for testing)
  6. Bake coherence
  7. Make a build
  8. Try to host a game with the build sample

Environment

SDK: 1.4.2
Unity: 6000.0.37f1
OS/Platform: Windows 11 x64

Hi @Dyecode

Thank you for taking the time to report this issue.

We’ve detected an issue with the Replication Server bundling and is we’re not bundling the RS correctly in the latest version.

While we deploy a fix, you can work around this issue by copying the RS manually.

The RS exists in the folder: Library/PackageCache/io.coherence.sdk/Runtime~/{your_platform}/replication-server.exe

You can copy this file to the StreamingAssets folder of your final build folder, inside the {your_project_name}_Data folder.

Sorry for the inconvenience

Hi !

Thanks for the response, with this little manipulation it works perfect !

Just started with coherence but it looks amazing.

Thank you!

Next patch 1.4.3 will include a fix for this issue.

1 Like