-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error during mod dependencies query: NoConnection (upgrade to proton-ge or wine-ge) #32
Comments
I will have a look into this as soon as i can, december is in general full of stress on my side, sorry! |
Thanks, and I'm sorry to hear that the holidays have been stressful for you. I have my suspicions that this might be related to #31 and I was coincidentally running into connection issues when hosting/enabling the port. This issue can be worked around during how busy Steam's servers are, if you attempt the mod download during a time of day when Steam is at low load you can actually get it to download the mods and start. It's quite odd. |
Just checked out current version and always got NO_IP issue locally... so did not get to mod downloading - but i just tried wine 7.0.1 and got no more NO_IP issue and ran into the mod downloading issue. Currently i'm experimenting with wine versions and will check if the upcoming v8 (currently RC4) might solve the issue, |
So for now, i can say that wine 8 will run too but for now i for sure stick to the stable version. Nothing did solve the downloading issues, but i had to create a new instance locally, now he tries atleast to download all mods (before i only got the message "Unable to download mods"). I've tried to use the pinned workaround from discord server to fix that issue (copy *64.dll files) but that did not do the trick for me. I'll try to run that on my root vm instead of my local wsl2 next but later. |
Did not work on my remote vm either. |
Is there any way to get wine-ge or proton-ge working in the image? I've heard from other threads that that solves the issue for many. |
I could try, but i never used one of these so i have to figure out how to setup these. I'll check that maybe tomorrow - today is a busy day. |
What i red about wine-ge/proton-ge so far is, that for steam games proton-ge should be used and for non steam games wine-ge. What i also red is that vulcan drivers are needed. I could not find anything about using it with a headless server. All Install Guides refer to desktop versions (those i found so far) |
Dang, let me see if I can reach out to GE to see if he would be willing to make a version of wine/proton meant for Windows game servers. It's unlikely he'll have time for it considering he's working on quite a few projects, or maybe there's a way to get the existing GE compatibility layers working without display drivers. |
I haven't been able to reach out to GE. However, ever since the last Wine upgrade I've noticed that I haven't had many issues with getting the server started and installing mods. I'll keep and eye on it and if I don't notice any issues with downloading mods I'll come back and close this issue. |
On my server it still does not install mods even with the new wine - but in general it seems to run better - atleast i got no NOIP so far. |
Interesting, I've had much better success. Maybe there is an issue with Steam needing its port opened. I believe I detailed my solution to Steam's port in #31. If I have free time in the coming week I'll try experimenting with removing it from the docker image. Are you using Mod.io or Steam for mods? |
Steam usually. |
I'm still getting errors when trying to download mods. With or without dll fix...
|
Go into your game logs, what's the reason it's failing? Mine would typically be related to a connection issue. |
I've been having issues after Tuesday's maintenance with installing mods. I'm able to get my server world running on my native Windows machine. This appears to be an issue with Wine itself and can be solved using Wine-GE or Proton-GE (TorchAPI/Torch#514 (comment)) as per other user's reports trying to get SE servers working on Linux.
The text was updated successfully, but these errors were encountered: