Client build packaged with binary editor cannot connect to dedicated server

  1. Cross compile linux dedicated server on Win64 from source-built version of the engine + deploy server
  2. Package Mac client from binary version of the editor on OS X
  3. Attempt to connect to server and receive “outdated version” error

The client build shares the exact same codebase as the server build, versioned with git.

Hi piinecone,

I have a few questions to ask you about this report

  • Did this particular process work in previous versions of the engine?
  • Would it be possible for you to clarify the steps of how you’re going about creating a Linux dedicated server on Win64?
  • Does this issue persist if the Mac client tries to connect from a version packaged from the same source code as the Linux Dedicated Server?

Hey @,

  1. I never tried, I was previously always able to get the source-built version of the engine to open my project so I would package from there.
  2. Sure, I documented the process on the wiki (A new, community-hosted Unreal Engine Wiki - Announcements - Epic Developer Community Forums) and on my blog (http://blog.piinecone.com/). Should be mostly identical. Note that the BuildingRocket() portion of the server target source is no longer relevant.
  3. All packaging occurs from the exact same source, versioned with git. When I package for Mac using the RunUAT command line interface, the resulting build is able to connect to the dedicated server. However, packaging from the binary build of the editor with the exact same project source produces a build that cannot connect to the dedicated server. There must be something slightly different about the way the binary editor “versions” the produced game executable as opposed to the source-built editor.

I’m not sure the engine is supposed to be able to do this, I just encountered it as a frustrating obstacle when the source-built version of the Mac editor couldn’t open my project (built from the same SHA from which the binary editor is built), while the binary editor could. I’ve since figured out how to package from the command line so this is no longer an issue for me, and it might not be worth resolving since it’s such a corner case and the source and binary versions of the editor probably aren’t supposed to be identical. Naturally I would defer to you. :smiley:

This issue is still not resolved. How did you fix the version error?