Closed Salvodif closed 3 days ago
Please delete the log and retry and send the new log file so i only get the relevant logs.
So im not shure why its not working, is this the only game with that Problem. Right now i also in holiday so i havent looked at the code for a bit. For now i'm not shure about that Problem.
So im not shure why its not working, is this the only game with that Problem. Right now i also in holiday so i havent looked at the code for a bit. For now i'm not shure about that Problem.
take your time and enjoy your holiday
So I marked this with help wanted, then someone else may help, but I'm out of ideas sadly. Sorry that I have no ideas.
Have you seen the log and have no idea out it? :-o
The log looks normal,
the only thing that i still have is the idea that it gets stuck on something,
but i have no idea what causes this.
The thing is that this appeares just on this game
so the script should be normal,
the game really makes no functional difference,
thats why I have no ideas.
Well maby try without any game arguments, that may do something or not.
Ok this issue seems very strange, as we have discussed it will try to solve this. @calvyb and @Salvodif since it seems you have the same problem, both of you can post what i ask for. This is mostly in case it is a other issue. First close steam, then open a terminal, then type "steam", next delete the wemod.log file, next start the wemod desired game, after that post the steam terminal output and the wemod.log file. Please upload the steam terminal output as a file so this chat dosn't get spammed. So save the steam terminal output in a file and drag it to the github comment box. Also upload the wemod.log as file. Lastly i know you have uploaded some of this already but i have pushed a update, so just re-post the new outputs please.
konsole.txt wemod.log I hope these are helpful to you and what you asked for. i had do to the konsole twice as the first time i left it running so long it wouldnt export the whole thing.
run:
cd /home/$USER/wemod-launcher
git reset --hard origin
git pull
sudo chmod -R ug+x .
and if there is no error repeat the steps below
First close steam, then open a terminal, then type "steam", next delete the wemod.log file, next start the wemod desired game, after that post the steam terminal output and the wemod.log file. Please upload the steam terminal output as a file so this chat dosn't get spammed. So save the steam terminal output in a file and drag it to the github comment box. Also upload the wemod.log as file.
Done all that. had to add /home/$user/wemod-launcher to the chmod command.
we mod still freezing on game launch konsole.txt wemod.log Pressed stop in steam after freezing to prevent log spam
Jep sadly same thing as this issue, this means i have no idea how to fix this, sorry you can try a other game, but other then then that i have no idea.
Considering that steam is doing nothing when the wemod launcher tryes to run it,
then if both of you still have this problem try to reinstall steam.
Also remove the .steam folder, but if you try that i recommend you to
move your .steam/steam/steamapps/common
and your .steam/steam/steamapps/sourcemods
folders beforehand if you don't want to reinstall the games you have.
After the steam reinstall move the 2 folders back, steam will think that the games are not installed but when you click on install it will then say, discovering old files
, and find the old game files.
Considering that steam is doing nothing when the wemod launcher tryes to run it, then if both of you still have this problem try to reinstall steam. Also remove the .steam folder, but if you try that i recommend you to move your
.steam/steam/steamapps/common
and your.steam/steam/steamapps/sourcemods
folders beforehand if you don't want to reinstall the games you have. After the steam reinstall move the 2 folders back, steam will think that the games are not installed but when you click on install it will then say,discovering old files
, and find the old game files.
If you @Salvodif or you @calvyb have tried this, report back if this has worked.
Tried that and had no joy. same issue persists. had a spare 120g SSD so decided i'd try a totally clean arch (kde) install on that and having the same issues.
got tk wine mono python-pip python-virtualenv steam protonup-qt and proton tricks all installed to make it as far as i do get.. little baffling. have tried it on 3 different games now and the exact same issue happens with all 3.
Tried that and had no joy. same issue persists. had a spare 120g SSD so decided i'd try a totally clean arch (kde) install on that and having the same issues.
got tk wine mono python-pip python-virtualenv steam protonup-qt and proton tricks all installed to make it as far as i do get.. little baffling. have tried it on 3 different games now and the exact same issue happens with all 3.
Strange, try to see if https://garudalinux.org/downloads works (just boot the iso gaming version then you don't need to have a fresh install, steam is preinstalled so you can just see if that works). Also you have tried a fresh install, but I'm not sure if you also tried to reset the .steam folder if not you can also still try that. If none if this works then it must be some strange hardver problem that is way beyond me.
Update: I think ive found a possible culprit.
My linux distro is Arch Running KDE Plasma. and i've discovered it only freezes and crashes on Wayland. If i logout and login with X11 instead of wayland wemod doesnt freeze and works as i would expect. and the game runs. Frame rate is terrible but it's progress.
switched between x11 and wayland several times and the behaviour is repeatable and consistent. wayland always freezes wemod but the game runs buttery smooth. x11 wemod always works just with terrible framerates.
so i now have 2 avenues to pursue. either figure a way to fix it on wayland, or figure how to improve the framerates on x11.
UPDATE: out of curiosity as my laptop is AMD and wondered if it could be a nvidia issue. I Decided I'd stick Arch with KDE on the laptop and got wemod working perfectly once again. even in wayland. Using AMDRadeon drivers. Integrated AMD GPU. So it's possible it's a nvidia on wayland driver issue. As nvidia on x11 works fine..
Just thought I'd post this update as it may be helpful to someone.. or if someone stumbles across and has it working on nvidia could offer insight into how.
So I am also on NVIDIA (latest beta driver), OpenSUSE Tumbleweed, and I am running into the same issue on Wayland. Now, I've noticed that wayland doesn't actually freeze. For me, it refreshes and I'm able to interact with it. It just takes about 2 minutes or more for it to update based on what I selected.
As mentioned
So I am also on NVIDIA (latest beta driver), OpenSUSE Tumbleweed, and I am running into the same issue on Wayland. Now, I've noticed that wayland doesn't actually freeze. For me, it refreshes and I'm able to interact with it. It just takes about 2 minutes or more for it to update based on what I selected.
Try x11, other than that, no solution was discovered yet.
Yeah, I've read the comments and I've also discovered that x11 is working fine. However, wemod appears to be completely operable on wayland despite the refresh issues. I'm able to toggle the cheats on and off and have the audible ding play at the exact moment I activate it. If the user has some patience, all they have to do is navigate through wemod to their game, hit "Play Game", wait some more until it says "Playing game" and then take screenshots of your available cheats and store them somewhere so that you don't have to rely on wemod's slow refresh issue. Then, wait some more until it processes that, go back to your game, and now you're able to hit the hotkeys for the cheats and they'll work.
Ok so this has been a long running issue and i pretty sure the wemod launcher can't actually fix this issue. The reason for this is that the wemod launcher just uses steam and wine behind the scenes and Im pretty shure the issue lies in the support of wayland from wine and steam (+nvidia). So there is no real way to fix this right now and keeping this issue around is also not that useful, since if it is not a launcher issue, then if this gets fixed it will be by wine and steam (+nvidia). So if there is no objection to this i will close this and add a help page about this in the wiki.
Thee wiki page is already online and can be seen right here.
Ok so this has been a long running issue and i pretty sure the wemod launcher can't actually fix this issue. The reason for this is that the wemod launcher just uses steam and wine behind the scenes and Im pretty shure the issue lies in the support of wayland from wine and steam (+nvidia). So there is no real way to fix this right now and keeping this issue around is also not that useful, since if it is not a launcher issue, then if this gets fixed it will be by wine and steam (+nvidia). So if there is no objection to this i will close this and add a help page about this in the wiki.
Thee wiki page is already online and can be seen right here.
Sure, you can close the issue.
Before you close the issue, I would like for the help page to be corrected because the wemod launcher DOES work under wayland, it is not frozen, it just loads VERY slowly. I've been using it under wayland like this for the past few months now.
I have added this as you requested, can hurt to have that after all.
I close this for now as mentioned.
Describe the bug
I just changed game (Hades) and doesn't starts anymore nor game nor wemod
Steps to reproduce the behavior
launch the game after everything had been configured
Expected behavior
I was expecting the WeMod start screen but it does not appear
Logs
wemod.log
Screenshots
No response
System Information
OS: EndeavourOS Linux KERNEL: 6.6.34-1-lts CPU: 13th Gen Intel Core i5-13600K GPU: NVIDIA GeForce RTX 3070 Ti GPU DRIVER: NVIDIA 550.90.07 RAM: 32 GB
Additional context
No response