Hey guys,
We are here to ask for some professional insights as to the issue we are currently facing. We’re investigating a cross-engine, cross-version EOS P2P failure and wanted to check whether this is a known limitation or something that’s been addressed in newer EOS SDK releases that made it incompatible to join cross-engine versions.
Our setup currently albeit weird is,
- UE 4.27 build using an older EOS.
- UE 5.6 build using the latest EOS.
What we found out,
- UE 4.27 is able to online & play with other UE 4.27.
- UE 5.6 is able to online & play with other UE 5.6.
- But UE 4.27 & 5.6 can never join a session together even though they can see the session.
Questions,
- Is EOS P2P between different EOS generations (UE 4.27 vs UE 5.x) known to be incompatible?
- Were there any changes in newer EOS versions that would explain why this occurs?
- Due to console stabilities & limitations being the reason we choose not to upgrade the engine entirely for the current moment, and I am assuming because of this the only option is to upgrade the EOS version upwards instead of downwards while ignoring the entire engine upgrade, what will happen?
(For example, 4.27 console platforms will be using a modified version of the latest EOS.) - Following up on the previous question, what will be the things to look out for / possibly needing to be modified to make it work?
(Low level networking issues? P2P logic? Encryption & Decryption logic? API mismatch? ext.)
We’re not expecting long-term support, we mainly want to confirm whether this is an architectural limitation, is it a possible direction, impending immense work or other concerns not known on our side. Any insight / direction would be greatly appreciated.