🐧 ESO 7.2.5 patch completely broke on Linux (unsupported)

Techwolf_Lupindo

Ant1 wrote: »

I just tested this out, and indeed, it works!

I just did, no go. Still get a black screen and the ZOSCrashlogger.exe running in the background.

Techwolf_Lupindo

Ant1 wrote: »

But just a question, how are your performances with this wine version? Because I get only ~40 FPS vs ~100 FPS with proton (the "steam wine release" to be short)

Make sure esync is enabled and if the kernel supports it, fsync. They do make a huge difference, excpelly in LUA (AddOns) performance.

DizzyGin

Techwolf_Lupindo wrote: »

Ant1 wrote: »

But just a question, how are your performances with this wine version? Because I get only ~40 FPS vs ~100 FPS with proton (the "steam wine release" to be short)

Make sure esync is enabled and if the kernel supports it, fsync. They do make a huge difference, excpelly in LUA (AddOns) performance.

Yes definitely run with fsync. I would recommend using the zen kernel for beginers as it usually is packaged with popular distros. https://github.com/zen-kernel/zen-kernel

I am currently running with PDS (scheduler) and TKG kernel. https://github.com/Frogging-Family/linux-tkg. This may have a package available for you within your distro.

Also, if using Steam you can use the Glorious Eggroll version of Proton instead of Wine.
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/7.0rc3-GE-1

Techwolf_Lupindo

An update for you all.

Back when this happen in Nov, I ended up buying a laptop to get me by untill I could fix it. Got some time off at home over the holidays and did a bunch of upgrades and rebuild the system to gcc 10, clean up a lot of outdated packages.

On a whim, I fired up linux steam client and noticed there was a few updates. I updated the proton stuff and click play...the game started!!!!!

Spent the past couple weeks getting audio to correctly work plus some rework, including trying out pipewire. Now for some tips.

Proton has a bug that refuses to honor PULSE_SERVER=tcp:127.0.0.1:8888 resulting in grabbing whatever audio device via alsa:hw interface, blocking any and all chat clients. So trails and PvP runs are no go in many guilds. I do plan on filing a bug report. Tried to configure the proton wine in there to use alsa:plug and it just refuses to do so.

If the audio is busy for any reason, like an active chat client, eso64.exe will crash on startup. I think this was my source of black screen problem I had before.

If you do not have .NET 472 installed, you can not start eso64.exe and have to start via the launcher. Upgrading or installing .NET 472 fixes it. I am pretty sure of this due to the only change I made when I was trying to get TTC client to work and discovered the eso64.exe started to work again.

TTC Client.exe AddOn will not work unless you create a Z:/ and give it access to root directory, meaning the Client.exe can see and read all the files on /home and everywhere else. I have not found a workaround yet of this security issue.

So in the end, I now have three different ways of running ESO. One via Steam Linux Proton client. One via Lutris with the GE runner, and one using the system built wine. I created a Proton-wine ebuild for my local use. Will be uploading that to my public repo in the future. The AddOns directory can be left in the Steam Linux Proton area sense that is heavily sandboxed and symbolic links can be use out of there point to it when running Lutris or standalone. I now have two complete installs of ESO and one install of PTS. I used a symbolic link to PTS to have it aviable in all three run use cases.

Only when running Steam Linux Proton client and letting it use blocking audio, sound is in surround51, but when using the standalone, the sound is in stereo even when everything is configure for surround 6 channel sound, and have tested to make sure it is working.

My next step to figure out why ZOS broke my window 7 laptop backup at the same time.