I’ve heard that esync might help a lot with apps that are CPU-heavy, so I’d wanted to give it a try with the MMO Elder Scrolls Online.
I’ve done the file editing as shown here and set the variable, but I can’t get the game to run. If I start it via launcher and hit “Play”, it seems like 100ms, doesn’t start anything and I could hit the button again.
If I run eso64.exe directly, it gives me an esync error (I guess), which I can’t compute for myself: pastebin link
Running it with esync-3.12 though does it and gives me only this line on the terminal:
[0x7F7AEE0CB120] ANOMALY: Instruction "lea" is modifying the stack
What do you mean “running eso64.exe DIRECTLY”? Does the game start from another exe?
When you say “doesn’t start anything”, it doesn’t even show anything in the terminal?
I’m asking this because you had outputs for both other tests, but pressing play had no error message at all?
When did you download esync-3.13? I’m slightly sure they reuploaded some version of esync these days into the Lutris runners list
What do you mean “running eso64.exe DIRECTLY”? Does the game start from another exe?
Yes, normally it runs a Launcher.exe, which then launches the exe for 32/64 bit game, either for the live server or the test server. So if I’d start the Launcher, I’d only get Launcher’s terminal output. That’s why I directly started eso64.exe to see the mentioned errors.
When you say “doesn’t start anything”, it doesn’t even show anything in the terminal?
I’m asking this because you had outputs for both other tests, but pressing play had no error message at all?
IMHO no need for a terminal output when launching it from the Launcher. Directly launching the exe (which the Launcher would do, too), gives me the mentioned pastebin output
When did you download esync-3.13?
Via Lutris itself. I re-downloaded it to be sure I don’t have a faulty version - same error
When you launch a game on Lutris, an child process will have its output in the terminal. So running the Launcher which then launches the game’s EXE will output everything there. It doesn’t open “more terminals” to run child processes and “puts their text” there.
In your pastebin link, there’s
System information:
Wine build: wine-3.3-2110-gf4492b5 (Staging)
Platform: x86_64
Version: Windows 10
Host system: Linux
Host version: 4.17.4-1-ARCH
Which leads me to believe you’re somehow running the game with wine 3.3, and not wine 3.13+esync patch.
That’s really odd because you’re launching via lutris. My two leads now are that you’re either not running the correct wine (how??) or you don’t have WINEESYNC environment variable set (just WINEESYNC, no need to put its value to 1, but that doesn’t hurt).
Now if you do have everything setup correctly, what I’d try would be to exclude the WINEESYNC variable and run the game “without esync”. Since it’s extra, the performance should be the same as with wine staging-3.13, because you already reported being able to run with wine, but not with the esync patched version.
This is the only line I get in the terminal when pressing the Play button:
wine: Unhandled page fault on write access to 0x00000048 at address 0x7b4841d9 (thread 00e3), starting debugger...
Which leads me to believe you’re somehow running the game with wine 3.3, and not wine 3.13+esync patch.
rofl indeed, didn’t see that. But I’m definitely running it from the downloaded Lutris stuff. I checked twice that I selected the right WINE version in the game’s properties. So either this is just a wrong string/variable that stands in the debug message, or there’s something wrong with the commited WINE on Lutris’ server.
I’ve already set WINEESYNC, as with esync-3.12 I definetly have difference with or without this environment variable.
