The Elder Scrolls Online

The textures are awful in Elder Scrolls Online with Wine. The grass flickers a lot, the terrain textures won't load (black), and the water flickers, of course this could be the terrain under the water.

I am running on an Nvidia GTX 980.

I'm at Debian Buster with NVidia, everything works perfectly except ground textures. They are there, but have some awful flickering effect.

Using an AMD card with and am seeing some ground texture issues where the some of the textures will load, but other areas the ground is pure green.

Anyone knows a workaround/fix for the ground textures issue? Everything appears to work fine (without any hacks), it just the ground textures now that are problematic.

No matter how mich research I've done, I couldn't find any workaround or someone whi fixed that. It really seems to be an issue with WINE's (unfinished) implementation of DX11, and it only affects Nvidia and I think Intel as well.

It seems more to be a driver issue. From what I've read, AMD doesn't have issues at all. Nvidia proprietary driver causes texture problems, while the open source driver (Nouveau) doesn't.

I am using Nouveau and I have the ground texture problem too.

Currently on 2.14 staging / development and ground continues to be glitchy upon movement. Set to Windows 10 and changed d3dcompiler_47 to use native, otherwise it fails to get to the character screen. Hoping someone can get this resolved.

The ground issue is still here in 2.16

The ground, shadows and weapon movement is glitchy but the framerate is almost on par with windows!

"With wine 2.10 staging game launches sucessfully"

Could you be more exact? Is the DWORD and/or copying of the .dll file not necessary anymore?

With wine 2.10 (staging) it works for me out of the box, changing to windows7/10 in winecfg (not sure its called that way but you know what I mean)
The ground textures are buggy though, maybe in the next months this will be fixed with futher development of dx11.
I have GTX 1060, i5 4440, 8gb ram, running mint 18.1 cinnamon.

- Moved d3dcompiler_47 from x64 to parent directory and setting it to 'native' in winecfg
- Played around with the registry MaxVersionGL, 40005 in decimal and 30002 in hex.

Installation from official page, without steam:
- Registry was not needed, with the d3dcompiler_47 change it started up the game, but I bought the game from steam so I couldn't login to futher test if it worked.

Installation from steam:
- Registry is important, if set to 40005 decimal it crashes, if set to 30002 or higher in hex it launches with 'Your version of DirectX is unsupported'.
Couldn't manage to find a fix, dont think there is any for the steam version of the game, im surprised it works this way though, maybe im wrong on something.
On a side note, if you run the test from the launcher -> settings -> about -> game consultant, results show im on directx9.0c and running windowsxp, even though I had windows 7 set up in winecfg

Linux Mint 18.1 Cinnamon 64-bit
Processor: i5-4440
RAM: 8 GB
GPU: GTX 1060 6 GB -> Drivers 375.66

I'm playing ESO through Steam. I set the registry key for MaxVersionGL to 40005 decimal and it worked the first time but after that I got the error message about unsupported DirectX. I removed the registry key and it's been working (albeit with ground texture glitches and animation trails). Getting 60 fps in wilderness areas and 20-40 fps in towns like Daggerfall.

I'm using:

Windows Steam installed via PlayOnLinux ("install a non-listed program" not with the POL installer for Steam)
Wine version 2.9-staging (CSMT on or off, both works)
Winecfg set to Windows 10 64-bit (display settings all default, -no-cef-sandbox or -no-dwrite arguments not required)
Installed d3dx11, corefonts, tahoma, vcrun2010, vcrun2012, vcrun2013 (don't know if the vcrun libraries are necessary)
Copied d3dcompiler_47 from .../steamapps/common/Zenimax Online/The Elder Scrolls Online/game/client to the ...client/x64 folder
Set d3dcompiler_47 to 'native' in winecfg

Linux Mint 18 Cinnamon 64-bit (linux kernel 4.4)
Processor: Intel i5 @ 3.8 GHz
Video Card: Asus GeForce GTX1070 Turbo 8GB (nvidia 375.66 proprietary driver)

The MaxVersionGL registry key has to be set with Hex values, not decimals:

Explained in docs wiki.winehq.org/Useful_Registry_Keys

| +->MaxVersionGL
| | [DWORD Value (REG_DWORD): Choose the maximum GL version to request. Currently defaults to version 1.0.
| | Set it to 30002 (hexadecimal) or greater to request a core profile context.]

wine output confirms as well:

with 40005 decimal:
err:winediag:wined3d_dll_init Setting maximum allowed wined3d GL version to 0.40005.

with 40005 hex:
err:winediag:wined3d_dll_init Setting maximum allowed wined3d GL version to 4.5.

In the first case the game returns the error Directx unsupported, in the second case something runs for a few seconds, then the play button lightens up again and game doesn't start.

Arch 64 4.11.4
R9 390 amdgpu, mesa 17.1.2
wine 2.9-staging
installed in a clean win7 64 bit prefix

Hi all,
For me, the launcher works, but when I click "Play" I get nothing -- no errors, no failures, no app.
I have followed the steps above and it didn't solve the issue.
Does anyone know if the launcher's play button uses Html/Javascript?
I think that there may be some issue with javascript in my wine instance.

Thanks for any help.
--kevin

never mind.
My bad. I re-installed wine and got past the issue.
Now I'm trying to get past the black screen thing mentioned below.
I will have to step through the hacks again.
thanks
--kevin

A few people are getting to the character login screen while still saying they are getting the DirectX error but not saying how they got past said error. I'm still getting the DirectX error, even after adding the registry key. Any advice?

My system is
Ubuntu Gnome 17.04
AMD RX 480 / MESA 17.2
Kernel 4.12-rc4
Wine 2.9-staging

Apparently the last test result "Garbage" for WINE 2.9-staging isn't true.

A bunch of us tinkered often with ESO and current WINE versions and the state for now is: THE GAME DOES RUN, but...

Requirements:

WINE 2.9-staging
+ copying the d3dcompiler_47.dll from the game directories into the .exe directory
+ AMD GPU users need to set specific registry keys (AFAIK the game there runs "good enough", but I only can tell from nVIDIA perspective)
+ nVIDIA users can also run the game (don't need registry fixes), but ground textures are performing weird (black or "solitaire win effect")

IMHO the game should receive a BRONZE rating. The game installs fine, launcher runs, game runs, login works, IIRC shop too, gameplay is fine.
*BUT* graphic glitches may appear if graphic setting are more-than-medium, nVIDIA GPUs don't know how to ground texture and performance is lacking overall. As an MMO, it's already demanding and ESO had optimization issues since it's birth, but the game itself is playable for now - but not good enough to make it a decent rating.

As WINE improves on DX11 on every release, we could also see good improvements for ESO. I'm keen on seeing the next releases of WINE, because I think the game will run on it at least as Silver in a short matter of time (maybe 2 weeks - 2 months).

My setup:
Arch Linux (4.11 kernel)
i7-4790K @4.4GHz
GTX 1080 with proprietary drivers

FPS in crowded city: 15-35 (probably CPU optimization is missing for ESO, but that's nothing new, hihi)
FPS in smaller places (wilds, dungeons): 60+ (hard to tell exact numbers, but if not too many players are showing up, the performance is very good)

--------------

TL;DR The game runs, but has many flaws. They don't break the game, but also don't provide the full immersion experience of ESO. Game may receive a good rating in 2 weeks to 2 months, IMHO.

Hello,

@Jonathan ( and all ESO enthusiasts:) ), I think Gold rating is too flattering for ESO at the current state of the wine, especially with NVIDIA cards.
You can check rating definitions here: wiki.winehq.org/AppDB_Maintainer_Rating_Definitions .

My conclusion is that there is in game ground flickering/strange artifacts and missing texture issues (the latter are visible on character selection screen at least) utilizing NVIDIA cards.
AMD seems to run the game better .

We need to file a bug report to inform developers and help them identify the issue. I had posted some logs/screens in another bug: bugs.winehq.org/show_bug.cgi?id=41213#c30
a couple months ago. I will try to find some time to update everything and file a new bug report, but I am really really busy lately.

Hi folks! Trying to run ESO in a wine_64 prefix, but when I want to start the game, this error appears immediately:

Your DirectX version is unsupported. Get Help:
help.elderscrollsonline.com/app/answers/detail/a_id/32155

Game closes afterwards. Launcher works fine, though. Do I need to run some winetricks?

I've got the same issue. Could it be a graphics driver issue? Maybe Wine needs a certain OpenGL version to be able to support DX11

You need to set the registry key HKLU --> Software --> Wine --> NEW KEY called "Direct3D" --> New DWORD --> MaxVersionGL (hex value of 40005)

Adam

Did you mean HKCU? Because I don't see HKLU. I already have the key HKCU->Software->Wine->Direct3D->MaxVersionGL = 40005

Are you sure it's the hex value? If I use it as a hex value (like here i.imgur.com/RSRMrii.png ) then I get this error: i.imgur.com/NhgOmTt.png

If I enter it as a decimal value, I still have the black screen. :/

With 2.7-staging it became much better!

I know can go into character selection, but have some missing ground textures. But some other ground textures are there! I totally see a progress here.

Though when I set the DWORD, I still get the DirectX error (see comment above). Any fix for this with proprietary nvidia?

With nvidia you don't need tor DWORD I found, but ground textures are messed up alas, I think this is an issue with the Nvidia drivers.
I actually just switched to an AMD card, and the issue is gone, ground textures are perfect and I can FINALLY play ESO again!
Picked up a cheap RX460 to use until the nvidia drivers work properly...not wasted money either, it'll go in my sons PC then!

Oh you lucky fucker. :D Well then I hope that there's soon a fix for the nvidia problem.

Also now I can be sure I don't need that DWORD.

Yeah, I'll put my nvidia card back in when that happens! I was going to upgrade sons PC anyway so he'll get this AMD card :D
I did have to disable distortion, and god rays too, or it crashes randomly, and ambient occlusion has to be off or the textures mess up but I can live with that, game still looks good.

Character select: i.imgur.com/5e3VnRb.jpg

Ingame: i.imgur.com/LTeqcNS.jpg

Oh I'm so jelaous. :D

Yes, disabling Ambient Occlusion covered some missing ground textures (and on armor), but still some ground is missing for me. I'm so excited that WINE possibly soon will make this game runnable. :)

Addenum: If you use the AMDGPU-PRO driver, you WILL need the dword, and yes it's 40005 in DECIMAL not hex.
The opensource plain AMDGPU works without but the pro needs it (I just installed AMDGPU-PRO today to test)
I should also mention, that I had BETTER performance using the open source drivers too!

With the latest wine (2.4+), the patch is no longer needed. If you are running the latest wine and are still getting green textures, submit a new bug with logs and screen shots.

While I am not getting the green textures, I'm still seeing corruption of the ground textures in game. Is this just me or is it the current state of the game under Wine?
Using Ubuntu Gnome 17.04 64Bit edition, Latest Nvidia drivers, WIne 2.6 (same issue with 2.4, 2.4 staging, 2.5 etc) same issue running wither the 32 or 64bit ESO client.

Seems similar for me too. I did post some findings here: bugs.winehq.org/show_bug.cgi?id=41213#c30 but the dev couldn't find something obvious or related to the initial issue, prompting me to
file a new bug report (which I didn't because of lack of free time). I think it's nvidia related.

Yes, that's the exact same issue I am having, using an Nvidia GTX 1050, Nvidia propietary driver (no choice really, under current ubuntu the 1050 isn't recognised by Nouveu even if I WANTED to use it)

Wine-Staging 2.3. I am using a 64-bit wineprefix, but I have tried a 32-bit one with no luck. I tried copying d3dcompiler_47 as well, and tried with and without DLL overrides for native d3dcompiler_47.

I am on Intel HD Graphics 4400 (Haswell Mobile/gen6).

There doesn't seem to be any abnormal things in the logs, just the normal d3d11 spew that others have reported here.

Anyway, the specific problem is that the logo videos go by, and the music plays, and I am able to login, but when the progress popup comes and it says "Logging in, requesting login...", the Elder Scrolls Online crash reporter comes up, and the Elder Scrolls Online window freezes, with the music still playing.

I had no problems on a skylake (gen9), but I was much happier with the fluidity of the game when I bought a Radeon RX480. If I have the chance this weekend, I'm going to try the new Wine version 2.4 to see if it fixes bug #41213. While I'm at it, I'll give my skylake a run as well.

I'm currently using the Padoka PPA with Ubuntu 17.04 if that helps.

Jason, seems 2.4 fixed the greenish ground issue for me ( without need to recompile with MAX_FRAGMENTS 32). I do still get the strange artifacts at the ground while moving that I sent you though.

You should file a new bug for the strange artifacts. Make sure that you include information like which video card, driver and version, and kernel version that you use. I would also include d3d debugging output. I use the following command:

WINEDEBUG=+d3d WINEPREFIX=~/.wine-eso wine explorer /desktop=eso,1280x1024 "Launcher/Bethesda.net_Launcher.exe" > debug.txt 2>&1

I finally got around to testing Wine 2.4 on my Radeon RX 480 using Mesa (padoka ppa) -- everything works as expected without needing my patch. I never got around to testing my Skylake, but it is still on my list of things to do. As far as my system is concerned, ESO now pretty much works out of the box (I didn't try it without the GL version override, I assume that is still an issue).

Is it because I have the Steam version?

I'm getting the same problem. I've got an ESO account linked through steam. Have you figured out a fix yet?

Unfortunatelly not. I have black ground texture at the character selection, so I don't want to go into world until I fixed that one. :)

I was able to play just fine, until I linked my steam account, and now it crashes on login. Graphics were actually working really well with AMD mesa drivers with a RX 480, and the MaxVersionGL fix.

There should be a folder with cache files in it (like item names, bla bla bla to not get them loaded from server everytime). Try to delete them. I remember at beta/launch that this solved some loading screen issues.

I had a look around, couldn't find much. The accounts show up as linked on the ESO account website too, I'm not sure clearing anything client side would fix that. I did some more digging there's no way to dissassociate them without contact support. Hoping a newer version of wine fixes the crash on login with steam accounts.

I've tried new 32-bit prefix, installed everything from scratch but I'm still getting black screen after pressing "Play" in launcher.

same issue for me
Ubuntu 16.04.2 LTS
wine-2.2
nvidia 375 driver.

The game works great with Mesa on a AMD RX480 after setting MaxVersionGL in the registry (HKCU\Software\Wine\Direct3D\MaxVersionGL) to 40005 (see
wiki.winehq.org/Useful_Registry_Keys).

I might be able to help if you post your logs or give more information about your setup.

Oops, I shouldn't have placed that URL in parens. Here it is again:
wiki.winehq.org/Useful_Registry_Keys

Did you install any DirectX or other packages with winetricks or similar?

Up until a recent game patch (I'm guessing homestead), I needed to install d3dcompiler_43 with winetricks. However, now d3dcompiler_47 is included with the game:
$ find -name d3dcompiler*
./The Elder Scrolls Online/game/client/x86/d3dcompiler_47.dll
./The Elder Scrolls Online/game/client/x64/d3dcompiler_47.dll

Oops, hit submit too soon. I meant to add that besides the registry hack mentioned above to work around Wine failing to use GL4+ with Mesa, the game works just fine with a fresh prefix. The ground textures are currently missing, but I submitted a patch that you can find attached to bug #41213 that works around that issue. The game is playable without the patch if you like the color green.

When I set the Registry key to 40004 (hexadecimal), ESO immediatelly crashes when trying to launch. I'll look into that later, as it crushed down my motivation again. :C

Thanks for your effort! Hopefully your commit gets accepted and ESO will be playable without hassle soon. :)

What errors are displayed right before the crash when you run the game from the command line? If you post your log to pastebin and put a link to it here, I might be able to better help.

Sure mate! This is what I get in the debug window when I debug-run it per PlayOnLinux: pastebin.com/1WTJW3eZ

I see two interesting errors in your log there:

err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
Have you tried running Mesa (Nouveau) like this says? Maybe a newer version of Nvidia's binary driver if available?

ERROR: ld.so: object '/usr/${LIB}/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
This might be a wine-staging issue since they carry the GTK3 patches. I don't have the gtk3-nocsd package installed and I don't get this message (but I don't run wine-staging). Try disabling the GTK3 option which I believe can be done via winecfg.

Nouvea is no option, as it cripples my performance. I think my nvidia version is up-to-date, as I game on Arch, always updated. :-)

Mh, no GTK option checked.

I realize that Nouveau may not be performant enough to actually game with, but it might be worthwhile to try it so that you can rule out the Nvidia binary driver as the issue. If you get the same issue with Nouveau, the problem is likely elsewhere.

Don't get me wrong, but I'd rather then wait until it finally runs out of the box. Just because I won't switch between Nouvea/proprietary just because when I want to run ESO.

But I appreciate your effort and help, you're the real man! :-)

I'll still fiddle a bit, especially when new WINEs get released.

Hey Jason, I'm back! :D I now use wine-2.5-staging (64bit) and it *would* start, though with a black screen. So I set the registry key to hexadecimal 40004 or 40005, always resulting in the following error directly after pressing play:

Your DirectX version is unsupported. Get Help:
help.elderscrollsonline.com/app/answers/detail/a_id/32155

Do you know how to solve this?

you need to use a dword

wiki.winehq.org/Useful_Registry_Keys

Si senor, I set it here:

HKCU\Software\Wine\Direct3D

I create a DWORD named "MaxVersionGL", check the hexadecimal radio box and set it to 40004

Or did I do wrong?

Ok, tested a bit more.

It doesn't matter if I set the DWORD or if I use staging/normal WINE or even 32/64 bit. Everytime I click Play in the launcher, ESO(64).exe starts, audio of the main menu starts playing, but the screen stays black. :/

(Testes with wine 2.5(-staging), both 32 and 64 bit, with and without the Registry DWORD)

I maybe have found a solution!

I did what Stanatis told here: appdb.winehq.org/commentview.php?iAppId=15787&iVersionId=34927&iThreadId=99669

Or in other words: copy the mentioned DLL into the directory where the eso64.exe resides and... BOOM! I have a picture as intended. :) Unfortunately the servers are now down for maintenance, so I can't check the ingame graphics. :D

Ok, I could test now. It runs!

Unfortunately I have the missing ground texture (and more) bug: i.imgur.com/EO8HWaC.jpg

The DWORD solution doesn't work, is there anything else to consider? I'm going to grind through the other comments again, but I guess I tried them all.

FYI just a status information

Tried it today with WINE 2.8, same issue with ground textures. I'm waiting for 2.8-staging to get downloadable per PlayOnLinux and then I try to fiddle with that.

Maybe its nvidia related then?

Maybe. If you are running the binary driver, maybe try switching over to Mesa (although nouveau isn't as capable as radionsi, so that might not help). If you post a copy of the output when running the game from the command line to dropbox and put a link to it here I might be able to help more.

I meant pastebin, but dropbox could work too.. Whatever

I was about to do it, but I managed to get it run.. I noticed the
err:d3dcompiler:compile_shader HLSL shader parsing failed.
part at the logfile, so what I did try:

cp The\ Elder\ Scrolls\ Online/game/client/x64/d3dcompiler_47.dll The\ Elder\ Scrolls\ Online/game/client/
winecfg -> Libraries -> d3dcompiler_47 -> Native (windows)

Graphics seem better than last time, missing ground textures still

Worked for me too. I don't think copying is needed though.

Great! glad I helped a little.
For me the copy seems that was needed since I tried first setting it to native and the result was the same, black screen.
So I tried copying it to the same dir with the executable just in case it didn't see it.
Notice that I didn't do any fresh install, just my old installation that it was working before.
You can test removing the dll from the client dir and test again, leave it under x64 dir (so your only setting would be the native dll through winecfg).
Try run the game again after.

This fixed it for me as well. Without copying the d3dcompiler_47.dll file, but setting d3dcompiler_47 to Native (Windows), ESO would just crash (an eso64.exe crash, not WINE crash) with no error (I didn't run from console, sorry) saying that ESO stopped working.

Video card: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1)
OS: Linux Mint 18.1 x86_64
WINE: wine-2.0-1-gbb58fbb with Jason Wood's texture patch applied. ;)

Eric, yes exact same behavior for me, seems both are needed.
Glad it helped

I should also note that without this fix, I do get the black screen issue as well. ;)

I should add that a 64-bit prefix works just fine for me.

I cannot get the game to launch. I have tried registry keys, new prefixes, etc. Anyone out there able to assist? I can't wrap my head around "Direct X version unsupported" or "Failed to initialize render device."

Fixed.. I was using string for registry entry and not dword. I have the weird bright green textures though. I will need to track down that patch.