Out of Synch at local network

[Maxemilian]

Hello guys

I wana play together with my friend, we re setting game and start succesifully but game giving this error after a while.

 Out of Synch
Red Alert 3 has gone out of synch with the other match participants. It is posible that the other players have modified their game versions. 
This match cannot contune.

Please restart Red Aler 3 to help avoid future desyncs. 

Our systems and tried something
Before list my system linux and I am playing with prton 4.11-13 myfriend running native win 10 and we’re using latest version of RA3

• Restart games in two computer.
  
• In network setting setted an Ip and port 22 and send delay active togeher
  
• Removed windows firewall completelly
  
• Error come out random, sometime at 5th min sometime at 9th minute
  
• Tried different 2 phone hotspot
  

More interesting that we played succesfully 8 months ago same systems and same computer same phone hotspot

we was deal with the same problem but we solved success but I remmeber port and ıp set only.

So Do u have a recommend for us.

[XYHC]

Were you using a VPN for the LAN games? I have previously got Hamachi to work for LAN, so you should try that if you aren't already using Hamachi.
Otherwise, it might be easier if both of you register for CnC Online: https://www.youtube.com/watch?v=LPrax-e-naU&t=2s

[Maxemilian]

@XYHC
yeah But I want to play on local network

[MShields]

man, i wish keb's emulator worked under win10. my siblings can't foreign languages and I refuse to maintain multiple cnc-online accounts.

[Maxemilian]

I tried between linux computers there is no problem but between linux and windows computers occours problem unfortunatelly

[Maxemilian]

Originally posted by MShields:

man, i wish keb's emulator worked under win10. my siblings can't foreign languages and I refuse to maintain multiple cnc-online accounts.

I doesn't know this emulator even I searched but I didn't find avalible thing. Could you give adress or more clearification

[MShields]

Originally posted by MAXEMiLiAN:

I doesn't know this emulator even I searched but I didn't find avalible thing. Could you give adress or more clearification

forum.teknogods.com/viewtopic.php?f=5&t=6630
it worked great when both machines were on win8.1.
with win10 the game crashes when you press "log in" in the game.

[Maxemilian]

Originally posted by MShields:

Originally posted by MAXEMiLiAN:

I doesn't know this emulator even I searched but I didn't find avalible thing. Could you give adress or more clearification

forum.teknogods.com/viewtopic.php?f=5&t=6630
it worked great when both machines were on win8.1.
with win10 the game crashes when you press "log in" in the game.

Yeah actually I prefer to play on linux with proton.
Thanks for recommendation
I played successfully between two linux
even different proton versions.

[SentientSheep]

I had this exact same issue, after many hours of troubleshooting and trying a lot of different options i have finally found a solution for it and it's quite simple.

Cross Play Windows/Linux

If you only want to simply play Red Alert 3 then force the use of Proton 3.7-8, unfortunately i do not know exactly why this issue is occurring but Linux and Windows play without any issues with this version. All other version that are available via Steam right now don't work properly for Red Alert 3 if you want to cross play on different operating systems.

The issue

There's a small catch however, the above mentioned version does not play nice with newer Proton version. Meaning it will result in the same issue you've stated. If more Linux players join the LAN match they will also need to have Proton 3.7-8 enabled on Red Alert 3. Even if the player base only consist of Linux players.

Just to be safe

My advice is to delete the wine prefix of Red Alert 3 first before switching to Proton 3.7-8 to prevent any kind of wine prefix conflict of previously used Proton versions.

To accomplish this delete the directory "17480" in the "compatdata" folder in your Steam library location.

This will delete the wine prefix and all relevant configuration data of Red Alert 3, reverting it to the "first boot" state.

The drawback

Since Proton 3.7-8 is the first version you can pick from in Steam it comes with a drawback not seen in more recent versions of Proton (4.11+) and that is the lack of D9VK which is now included with DXVK. Meaning it will use OpenGL as it's translation to DX9, which can lead to graphical artifacts and performance issues in some cases.

To solve those issues download the DXVK libraries from GitHub and extracts it's content to the Red Alert 3 wine prefix and setting DLL overrides for the libraries. I can explain this in further detail if necessary.

Link to DXVK [github.com]

Personal use

I've only used this solution in combination with Hamachi to host LAN games. I do not know if relevant issues with online play can be resolved by using this specific Proton version.

I hope this helps you and other people that come across this discussion. If you need further assistance just let me know.

[SentientSheep]

I'm probably reacting to a dead thread at this point, but i want to help people facing
this issue.

My above mentioned solution still works to this day but there is another more simplistic solution available.

Prelude

Even though the above solution using steam Proton 3.7-8 works, it has drawbacks. For me, the two main drawbacks are no D9VK and LARGE_ADDRESS_AWARE (LAA) support.

D9VK (now part of DXVK) helps with graphical glitches and performance. LAA helps 32-Bit application to utilize 4GB of RAM instead of 2GB, which greatly helps with mods like GenEvo.

Proton-tkg 5.14.r0.gb71d588d

Since Proton 3.7-8 is dated to say the least i thought it was time to see if there was an alternative for this issue and there is. Meet Proton-tkg 5.14.r0.gb71d588d.

This version is the latest version that is working without the out of sync issue and uses D9VK and LAA out of the box. Newer versions of Proton-tkg do not work, older versions do.

For people wondering about Proton-GE, it does not work, I've tried the Proton-7.3-GE-1 and Proton-GE-4.5-Beta-1 and a few in between but no success.

Versions newer than Steam Proton 3.7-8 will also give you the out of sync issue.

Installing Proton-tkg

Simply download proton tkg 5.14.r0.gb71d588d release zip [github.com]

After the download completes uncompress to ~/.steam/root/compatibilitytools.d on most distros or ~/.steam/compatibilitytools.d. If the directory doesn't exist, simply create it.

Restart steam and go the the properties of Red Alert 3 and select
proton_tkg_5.14.r0.gb71d588d as the specific Steam Play version and you're done.

Before booting

If you haven't booted up Red Alert 3 with any other Proton version yet, simply select proton_tkg_5.14.r0.gb71d588d and you're set. If you have, it would be advisable to delete the existing prefix first to prevent conflicts.

To accomplish this delete the directory "17480" in the "compatdata" folder in your Steam library location.

This will delete the wine prefix and all relevant configuration data of Red Alert 3, reverting it to the "first boot" state.

Conclusion

I do not yet know why this issue is occurring but i might have some leads.

Since Proton-3.16-5 FAudio has been implemented as can be seen in the Changelog [github.com]

• Completely new implementation of XAudio2, using the FAudio project. This should provide much higher quality audio for games that use XAudio2. Notably, this now supports volume mixing and audio effect processing features that were missing from the old implementation.

With Wine 5.15 they've started with the implementation of XACT libraties [www.winehq.org] which are libraries used by XAudio2, which in turn now uses FAudio as it's back-end.

• Initial implementation of the XACT Engine libraries.

After Wine 5.14 and thus after Proton-tkg-5.14 and Proton 3-16-5, Red Alert 3 starts showing the out of sync issue.

Which leads me to believe that Red Alert 3 does not like FAudio for some reason.

For now this is all I've got and i hope it helps someone in search of a solution.

[KWAGGA]

Originally posted by SentientSheep:

I'm probably reacting to a dead thread at this point, but i want to help people facing
this issue.

My above mentioned solution still works to this day but there is another more simplistic solution available.

Prelude

Even though the above solution using steam Proton 3.7-8 works, it has drawbacks. For me, the two main drawbacks are no D9VK and LARGE_ADDRESS_AWARE (LAA) support.

D9VK (now part of DXVK) helps with graphical glitches and performance. LAA helps 32-Bit application to utilize 4GB of RAM instead of 2GB, which greatly helps with mods like GenEvo.

Proton-tkg 5.14.r0.gb71d588d

Since Proton 3.7-8 is dated to say the least i thought it was time to see if there was an alternative for this issue and there is. Meet Proton-tkg 5.14.r0.gb71d588d.

This version is the latest version that is working without the out of sync issue and uses D9VK and LAA out of the box. Newer versions of Proton-tkg do not work, older versions do.

For people wondering about Proton-GE, it does not work, I've tried the Proton-7.3-GE-1 and Proton-GE-4.5-Beta-1 and a few in between but no success.

Versions newer than Steam Proton 3.7-8 will also give you the out of sync issue.

Installing Proton-tkg

Simply download proton tkg 5.14.r0.gb71d588d release zip [github.com]

After the download completes uncompress to ~/.steam/root/compatibilitytools.d on most distros or ~/.steam/compatibilitytools.d. If the directory doesn't exist, simply create it.

Restart steam and go the the properties of Red Alert 3 and select
proton_tkg_5.14.r0.gb71d588d as the specific Steam Play version and you're done.

Before booting

If you haven't booted up Red Alert 3 with any other Proton version yet, simply select proton_tkg_5.14.r0.gb71d588d and you're set. If you have, it would be advisable to delete the existing prefix first to prevent conflicts.

To accomplish this delete the directory "17480" in the "compatdata" folder in your Steam library location.

This will delete the wine prefix and all relevant configuration data of Red Alert 3, reverting it to the "first boot" state.

Conclusion

I do not yet know why this issue is occurring but i might have some leads.

Since Proton-3.16-5 FAudio has been implemented as can be seen in the Changelog [github.com]

• Completely new implementation of XAudio2, using the FAudio project. This should provide much higher quality audio for games that use XAudio2. Notably, this now supports volume mixing and audio effect processing features that were missing from the old implementation.

With Wine 5.15 they've started with the implementation of XACT libraties [www.winehq.org] which are libraries used by XAudio2, which in turn now uses FAudio as it's back-end.

• Initial implementation of the XACT Engine libraries.

After Wine 5.14 and thus after Proton-tkg-5.14 and Proton 3-16-5, Red Alert 3 starts showing the out of sync issue.

Which leads me to believe that Red Alert 3 does not like FAudio for some reason.

For now this is all I've got and i hope it helps someone in search of a solution.

Good news. I have created a custom Proton-TGK-7.6-R12 based build that fixes the Desync issues. You can grab the proton runtime profile here.

h t t p s:// tinyurl .com /proton76

MD5 Checksum: fbb643566d1d6d369abcba1de6275d97

I had to add spaces as links are getting blocked. Remove the spaces :)

Performance is great! Issue was tracked down to changes in the vcruntime files since version 5.14. I have put some changes in place that fixes it and provides what the games expects for consistency on cross OS platform play.


Enjoy!

[SentientSheep]

Originally posted by KWAGGA:

Originally posted by SentientSheep:

I'm probably reacting to a dead thread at this point, but i want to help people facing
this issue.

My above mentioned solution still works to this day but there is another more simplistic solution available.

Prelude

Even though the above solution using steam Proton 3.7-8 works, it has drawbacks. For me, the two main drawbacks are no D9VK and LARGE_ADDRESS_AWARE (LAA) support.

D9VK (now part of DXVK) helps with graphical glitches and performance. LAA helps 32-Bit application to utilize 4GB of RAM instead of 2GB, which greatly helps with mods like GenEvo.

Proton-tkg 5.14.r0.gb71d588d

Since Proton 3.7-8 is dated to say the least i thought it was time to see if there was an alternative for this issue and there is. Meet Proton-tkg 5.14.r0.gb71d588d.

This version is the latest version that is working without the out of sync issue and uses D9VK and LAA out of the box. Newer versions of Proton-tkg do not work, older versions do.

For people wondering about Proton-GE, it does not work, I've tried the Proton-7.3-GE-1 and Proton-GE-4.5-Beta-1 and a few in between but no success.

Versions newer than Steam Proton 3.7-8 will also give you the out of sync issue.

Installing Proton-tkg

Simply download proton tkg 5.14.r0.gb71d588d release zip [github.com]

After the download completes uncompress to ~/.steam/root/compatibilitytools.d on most distros or ~/.steam/compatibilitytools.d. If the directory doesn't exist, simply create it.

Restart steam and go the the properties of Red Alert 3 and select
proton_tkg_5.14.r0.gb71d588d as the specific Steam Play version and you're done.

Before booting

If you haven't booted up Red Alert 3 with any other Proton version yet, simply select proton_tkg_5.14.r0.gb71d588d and you're set. If you have, it would be advisable to delete the existing prefix first to prevent conflicts.

To accomplish this delete the directory "17480" in the "compatdata" folder in your Steam library location.

This will delete the wine prefix and all relevant configuration data of Red Alert 3, reverting it to the "first boot" state.

Conclusion

I do not yet know why this issue is occurring but i might have some leads.

Since Proton-3.16-5 FAudio has been implemented as can be seen in the Changelog [github.com]

• Completely new implementation of XAudio2, using the FAudio project. This should provide much higher quality audio for games that use XAudio2. Notably, this now supports volume mixing and audio effect processing features that were missing from the old implementation.

With Wine 5.15 they've started with the implementation of XACT libraties [www.winehq.org] which are libraries used by XAudio2, which in turn now uses FAudio as it's back-end.

• Initial implementation of the XACT Engine libraries.

After Wine 5.14 and thus after Proton-tkg-5.14 and Proton 3-16-5, Red Alert 3 starts showing the out of sync issue.

Which leads me to believe that Red Alert 3 does not like FAudio for some reason.

For now this is all I've got and i hope it helps someone in search of a solution.

Good news. I have created a custom Proton-TGK-7.6-R12 based build that fixes the Desync issues. You can grab the proton runtime profile here.

h t t p s:// tinyurl .com /proton76

MD5 Checksum: fbb643566d1d6d369abcba1de6275d97

I had to add spaces as links are getting blocked. Remove the spaces :)

Performance is great! Issue was tracked down to changes in the vcruntime files since version 5.14. I have put some changes in place that fixes it and provides what the games expects for consistency on cross OS platform play.


Enjoy!

Hello KWAGGA,

I revisited Red Alert 3 yesterday to re-test a mod and went to check on this post to see if any replies were made. To my surprise there was.

While i personally don't download files from unknown sources, i do really appreciate the effort you put into creating a custom proton version with fixes for desync issue.
However i wanted to find out if it could be fixed through other methods.

Since you mentioned Microsoft Visual C++ Runtimes (vcruntime) i narrowed my search and came across a ProtonDB post (Which i believe was from you) on Command and Conquer 3: Kane's Wrath. The post stated after installing multiple vcruntimes via protontricks that the desync issue was resolved.

So i went to try, Red Alert 3 ships with Microsoft Visual C++ 2005. So i installed protontricks (flatpak) and installed vcrun2005 for Red Alert 3 and lo and behold all the desync issues were gone! Protontricks installed a slightly newer vcrun2005 version and also set the correct overrides in wine.

I have tested this on Proton 7.0-5, but this will also work on other versions of proton.
My testing setup consisted of a Windows 10 Virtual Machine on my fedora desktop.
I created a LAN game and let my VM and proton join the game, threw in a few brutal AI and became spectator of my own game.

Normally, within 15 minutes a desync would occur. Now it can go on for 1+ hour without any issues, which is amazing since I've tried to look everywhere for a proper solution and thanks to your posts here and on ProtonDB you basically handed me the anwser!

For the uninitiated reading this, the main advantage of this is that it does not require a custom proton version, you can apply this on any proton version on any prefix (A.K.A. wine-bottles stored in compatdata). The best thing is, you only apply it on the game you need, others wont be affected.

Now onto the how-to, installing vcrun2005 can be done in multiple ways for simplicity i'll keep it down to two methods. Both using protontricks.

Protontricks via Flatpak

This is the method i used and tested. The advantage of flatpak is that you don't have to download all the dependencies of the protontricks via the package manager. You do need to have flatpak installed for this, since i already used flatpak for other things this was my preferred method.

1. Setup Flatpak LINK[flatpak.org]
2. Install Protontricks LINK[flathub.org]
3. Open Protontricks (search the application menu)
4. Choose Red Alert 3 (17480)
5. Choose "Select the default wineprefix"
6. Choose "Install a Windows DLL or component"
7. Scroll down until you find "vcrun2005" and select it.
8. Click "OK", now a few pop-ups will guide you through the installer.
9. After the installation of "vcrun2005" is finished close protontricks.
10. Enjoy your desync free Red Alert 3.

Protontricks via package manager

This is another method you can try, haven't tested it myself but should work just fine.
The below example will show on how to install for fedora.

Link to github [github.com]

1. Open a terminal window
1. Type 'sudo dnf install protontricks' without the quotes.
2. Type 'protontricks 17480 vcrun2005' without the quotes.
3. Follow the vcrun2005 installer
4. After the installation of "vcrun2005" is finished close protontricks.
5. Enjoy your desync free Red Alert 3.

Conclusion

It seems to have something to do introduced with the release of wine 5.15.
The changelog states the following.

    
• Beginnings of a math library in MSVCRT based on Musl.

I am unsure if this actually is causing the issue but it's something related to Microsoft Visual C++ runtimes.

Hope this helps anyone facing this issue!

Many thanks to @KWAGGA for providing a custom proton version and also leading me in the right direction!

Merry Christmas all,
SentientSheep.

[KWAGGA]

Well done and great guide.
I am happy when someone can benefit from my efforts just like I in turn did from others ;D

Thank you for taking the time and to provide a detailed write up and guide on how to get things running as It will undoubtedly help others and set them on the right path to enjoy this gem of a game.

A big merry Christmas and Happy New Years to you to!
KWAGGA

[Fonzz]

Works perfect. Played in lan a couple of long games with my 10 year old son. No more out of sync error! Thank you Sientientsheep.