#When attempting to open MVerse, it hangs, and then gives "connection timed out"

9 messages · Page 1 of 1 (latest)

frozen plinth
#

Hello,

Trying to get MVerse working, and when trying to host a game, the MVerse screen never loads; after about 20-30 seconds, a timeout message is given.
Things tried:

  • Complete system reboot
  • Re-validating files on steam
  • Checked the github issues and discussions for anytime that seemed similar
  • No other games or services were having issues.
  • Checked with some friends who have the game, they were able to start MVerse normally, and were able to play a game.
  • Manually set the executable for CW4.exe as an exception in the firewall
  • Ensured that my Antivirus was not interfering with the application; nothing in the logs demonstrated that it was.

To be clear, this isn't "can't join another game", this is "MVerse doesn't even open".

In the player.log it looks like EpicEOS fails to register a device ID? the only information I could find about this error was in android/unity developer forums, and seemed to be related to the game development, not a client issue that I could fix.

I'll attach the player.log file, but here's the actual error:

EOSSDKComponent.Awake
NetworkManager created singleton (DontDestroyOnLoad)
Mirror | mirror-networking com |
Epic Manager: Category - LogEOSConnect Message - Failed to save DeviceId access credentials on the local device. Result: 2147483647.
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogError(Object)
Epic.OnlineServices.Friends.OnRejectInviteCallback:Invoke(RejectInviteCallbackInfo)
Epic.OnlineServices.Platform.PlatformInterface:Tick()
EpicTransport.EosTransport:ClientEarlyUpdate()
Crosstales.FB.OpenFilesStart:Invoke()
 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

Device ID creation returned UnexpectedError
AutoSave

There was a similar sounding issue called https://discord.com/channels/192420539204239361/1211388165147988108 but the OP has left the discord, so unsure whether they ever fixed the problem.

Here's the player.log

#

Carlbot deleted my message because I posted a snippet from the log that includes the discord.gg invite. Hopefully a moderator can undelete? that would be great, it's 2:30AM and I don't want to re-write that.

#

<@&368803924984987658> (please help ❤️ )

fickle ocean
#

sure, i can do that for you

#

Original message:

Hello,

Trying to get MVerse working, and when trying to host a game, the MVerse screen never loads; after about 20-30 seconds, a timeout message is given.
Things tried:

  • Complete system reboot
  • Revalidating files on steam
  • Checked the github issues and discussions for anytime that seemed similar
  • No other games or services were having issues.
  • Checked with some friends who have the game, they were able to start MVerse normally, and were able to play a game.
  • Manually set the executable for CW4.exe as an exception in the firewall
  • Ensured that my Antivirus was not interfering with the application; nothing in the logs demonstrated that it was.

To be clear, this isn't "can't join another game", this is "MVerse doesn't even open".

In the player.log it looks like EpicEOS fails to register a device ID? the only information I could find about this error was in android/unity developer forums, and seemed to be related to the game development, not a client issue that I could fix.

I'll attach the player.log file, but here's the actual error:

EOSSDKComponent.Awake
NetworkManager created singleton (DontDestroyOnLoad)
Mirror | mirror-networking.com |
Epic Manager: Category - LogEOSConnect Message - Failed to save DeviceId access credentials on the local device. Result: 2147483647.
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogError(Object)
Epic.OnlineServices.Friends.OnRejectInviteCallback:Invoke(RejectInviteCallbackInfo)
Epic.OnlineServices.Platform.PlatformInterface:Tick()
EpicTransport.EosTransport:ClientEarlyUpdate()
Crosstales.FB.OpenFilesStart:Invoke()
 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 39)

Device ID creation returned UnexpectedError
AutoSave

There was a similar sounding issue called https://discord.com/channels/192420539204239361/1211388165147988108 but the OP has left the discord, so unsure whether they ever fixed the problem.

frozen plinth
#

Thanks Grabz, you rock

frozen plinth
#

🥺 Anyone with a similar issue and hopefully a solution? Or is this the kind of thing that should get lodged on the Git?

thorn flame
#

I'm not sure I can help...but
do you have access control issues or Onedrive that you use?

My theory is that something is restricting access to part of your file system so that EOS can't save the needed information.
So, you could try running under an admin user or something which may get you past this blocker.
My only other suggestion is perhaps a re-install of CW4 and/or reverify game files - but you'll want to back up your progress and saved games before you do that.

cyan nest
# frozen plinth Hello, Trying to get MVerse working, and when trying to host a game, the MVerse...

Hi Frosty, sorry you're having issues. Seems it has been a few days. You have done some spadework on this, so I'm going to be brutally frank.

Even though there are two types of connection (LAN and Internet) it is my recollection that only Internet works reliably (reliably here is used as a relative term comparing the two connection methods, and not in absolute terms).

The whole Mverse excursion was - as it says on the Mverse screens - an experiment. Knucracker was wondering whether it would be possible to allow multiple players with minimal data transmission given that the state of the creeper simulation was deterministic. We soon discovered how many exceptions to the deterministic state existed. The workload to create a more comprehensive communications model was deemed too high for the increase in player numbers - not many folks play Creeper World in multiplayer. So essentially the project was shelved at a specific point - where most things work and some things don't.

As for support issues - that is also an order of magnitude larger than supporting a single player on a single machine. There are many more components involved and many more configuration issues that may affect establishing a connection between players.

Ultimately we know that the current setup works for some players, and that's where it will remain. We can try and give advice, but there will be no code fixes or updates to the base product. If we see some easy-to fix anomaly in the log fil, we might be able to suggest a fix.

In your case this is not so, we cannot even begin to determine the cause of the error, and are thus unable to assist you.

I'm really sorry, but it may be anything specific to your machine - malware blockers, a network configuration, routing - we just don't know and we don't have the toolds or the skill to assist you. Opening a GitHub issue will also not garner a response, the developer is full-time engaged on completing the next Creeper World game.