#mverse
78 messages ยท Page 1 of 1 (latest)
line 139 should be when mverse started
port state for listening, launching/closing mverse and launching/closing the game changes nothing
among other notable moments:
hosting & connecting via lan doesn't work (even as i brought laptop with me to check)
hosting & connecting doesn't work on windows
a year or more ago i did play on this computer in mverse with same person on windows
the router didn't change since
Epic Manager: Category - LogEOSConnect Message - DeviceId access credentials already exist for the current user profile on the local device.
this part is what prevents the game from starting a lobby properly, but i am not sure what the steps are to fix it other than "try again later"
one thing is that the game doesn't handle switching between LAN and Internet properly in the same session, so if you want to try one or the other you should restart the game
the error you got indicates you might be using the Internet option with two instances of the game on the same network which doesnt work and you need to use LAN, but restart the game first if you used Internet option before
Yeah, the EOS stuff isn't (as it existed at the time CW4 was created and how it was implemented in the game) fault tolerant and requires a game restart if you switch most anything (or anything fails)
i am pretty sure it was right after the game was restarted (for logs clarity), but here's another piece of puzzle: log of starting mverse after full computer restart, booting up the game first time
and you are not also running mverse/trying to join on another computer in the same network?
no. running in internet mode, no other computer working in LAN
i can restart pc and try LAN if that would clarify logs
do you have EGS running on the computer in the background?
Epic Games Service i assume? i don't have EGS on my pc, but can't tell if any other process uses it, though it's unlikely (running rn from user side: file explorer, notepad, CW4, discord, steam, wireguard)
the store
don't have it
as unfortunate as it is, my only remaining idea is that maybe EOS is having trouble identifying the local computer when it is running through proton... i am on linux myself right now actually so i'll go and check out of curiosity if i get the same problem
Epic is not known for their linux support (or lack thereof)
i did think it may be linux issue, but then it would have worked on windows (which it didn't)
ah right, you did mention that
though it is possible it happened for an entirely other reason (such as accidental relaunching of mverse)
it seems like my game hosted a lobby without an issue, at least looking at the log
want to try joining to see if at least that works?
sure
AwEAYSAAMDAwMjcxYTczNDExNDg0MTg4ZDdlYjI3MDcwYjBjZGPmAQBiAAEBAGOryg0qAwEAZAQARGFudQA
*relaunching game for clarity*
naturally
which proton version do you use?
well eh, if it doesnt work on windows too perhaps that does not matter
connection failure
yeah, you keep getting the same error about access credentials already existing on the local machine.. as if something was running and initializing EOS already so CW4 can't do it. but you don't have anything like that running
unspecified. i checked mark and it briedly showed proton 9.0-4 before moving to hotfix
oh hey, restarting game at proton experimental and hosting via lan doesn't have that issue
it won't, LAN does not use EOS at all
on internet hosting same error
huh. i recall we tried to LAN and we failed too. that's odd
i guess we try again
you might not have restarted the game after trying Internet
then LAN is likely not to work
possible yeah
also, is EGS library outdated for CW4? because i can't see the trace it points at
i have no idea, depends on the definition of outdated, the mverse update was in 2021, i doubt it was updated much since then
did you make two attempts to connect to my lobby?
negative
i found two connection failures in my log
maybe it just crashed twice for some reason
but you did connect to me it seems like
it just failed
tbf "does everything mverse related twice" is a plausible reason why game acts like i already have mverse hosted when i host
that it definitely would
i guess i could have uncarefully clicked again, care to check it another time?
sure
hm
now that i have started the game back up again
EOSSDKComponent.Awake
Epic Manager: Category - LogEOSConnect Message - DeviceId access credentials already exist for the current user profile on the local device.
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogError(Object)
Epic.OnlineServices.Friends.OnRejectInviteCallback:Invoke(RejectInviteCallbackInfo)
(...)
you mean it may be persistent between relaunches?
i don't know, all i know is that i did not have the error the first time i launched, but now it appeared after restarting the game and hosting again
AwEAYSAAMDAwMjcxYTczNDExNDg0MTg4ZDdlYjI3MDcwYjBjZGPmAQBiAAEBAGOKQIx3AwEAZAQARGFudQA
feel free to try but i doubt it will connect given the circumstances
fail
my game did log a failure as well, a single failure this time
wait
and then a few seconds later it logged a second failure
well it could also be that someone is reading this thread and also trying to join ๐
its not completely unlikely
should probably be DMing you these invites
nah, you overestimate my number of currently awake friends who want to play mverse (0, may become 1 in 4 hours)
well anyone can read this thread
if you have a way of LAN connecting with your friends, that might be the best thing to try. my best guess is that it's ultimately some linux problem that ended up also breaking the windows version on the same local machine, perhaps its not cleaning up correctly on game exit or something
lack of isolation is unlikely, since the appdata folder is different and even game for linux is another copy on linux disk
but i'll try LAN and report results, thank you!
mverse is still "experimental" and always will be, and the LAN option at least should be fairly bulletproof. there is a way to test it yourself too, you can run more than one instance of the game locally to test it
this wiki page explains how, although the instructions are for windows, you can probably figure it out
https://knucklecracker.com/wiki/doku.php?id=cw4:mverse