EverQuest (205710)

[Rabcor]

Compatibility Report

• Name of the game with compatibility issues: EverQuest Free-to-Play
• Steam AppID of the game: 205710

System Information

• GPU: 980-Ti
• Driver/LLVM version: 396.54.09
• Kernel version: 4.18 (Manjaro)
• Full System Info: https://gist.github.com/Rabcor/3c1d3443564644dfa2b0e37e85182b71
• Proton version: 3.16-4 Beta

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

Symptoms

• The game's graphics and interface are broken unless d3dx9_43 is installed.
• Some users report difficulty opening the Launcher (It failed the first time I tried to launch it, but worked the second)
• Loading times are unrealistic (in the range of 5-20 minutes), the game is unplayable, additionally performance was horrible even in menus (<10fps).
• The game supposedly needs WMI to be installed, but WMI can only be installed on 32-bit prefixes via winetricks/protontricks. Installing WMI will likely fix the above mentioned issue.

Additional Info:

Lutris seems to have found some sort of workaround to install WMI on a 64-bit prefix which is used to install EverQuest on Lutris. They use the installer, and then simulate a reboot after it's completed (user must press ok to reboot on prompt that comes after installation of it) the installer for it seems to be outdated however, as the game can't properly finish it's install.

[FreedomFaighter]

Edit: 5.0-10 with d3dx9_43.dll is also working

LaunchPad (the EverQuest launcher) is working with Proton 8.0-1 and the mentioned d3dx9_43.dll can be installed with protontricks without the white window that sometimes appears in place of the launchpad window appearing

[kai4785]

When playing Everquest Live, some textures appear to fail to render, and models appear as white. Shadows seem to work so they appear ghostly. It appears that it's mostly with what appear to be the very oldest textures that have been in the game for 20+ years. This has been reported in a few places on Reddit as well: https://www.reddit.com/r/everquest/comments/199dhsy/texture_issues_with_dx11_update_linux_via_steam/ https://www.reddit.com/r/everquest/comments/1ahs9gc/weaponsshields_are_rendering_as_plain_white/ https://www.reddit.com/r/everquest/comments/1cwgqwz/old_models_on_linux/

You can replicate this by launching the Free to Play version of the game, disabling new character models, and choosing a server. The next screen is the character select, and your "old" models will be untextured and appear white.

My system: Ubuntu 20.04 Steam Proton 9.0-1 NVIDIA GeForce RTX 2060 Driver version 525.105.17

Comments from dxvk suggest this is a problem in WINE wrt WindowsCodecs.dll.

[Rabcor]

Well, project1999 works quite well through lutris if anyone comes here wondering. EQ Live seems like it's dying.

[Czahrien]

I submitted an issue for the white textures over at https://bugs.winehq.org/show_bug.cgi?id=56755 with a small patch that seems to fix the issue for me.

[kai4785]

Proton Experimental [bleeding-edge] build works for me as of today.

[arazilsongweaver]

EverQuest's mouse pointer seem to be offset by the height of the title bar when entering the character selection screen in full screen windowed mode.

This problem can be resolved for the session by hitting ALT+ENTER to cycle (true) full screen mode.

Arch Linux / KDE Plasma 6.1 Wayland Proton Experimental AMD Radeon 780M / AMD Radeon RX 7700S Mesa 24.1.2 Linux 6.9.5-arch1

[arazilsongweaver]

You may encounter issues with various text labels being cut off if the "Arial" font is unavailable. Proton seems to default to "Liberation Sans" as an alternate which has slightly wider characters than Arial. To fix this situation, either install the "Arial" font from a Microsoft Windows font package or switch the user interface font (in Options / General) to "Noto Sans" or a similar narrow sans serif font.

[kisak-valve]

Selective rendering in EverQuest

Issue transferred from https://github.com/ValveSoftware/Proton/issues/8309. @Qiset posted on 2024-12-11T20:54:57:

Compatibility Report

• Name of the game with compatibility issues: EverQuest F2P
• Steam AppID of the game: 205710 build id: 739123

System Information

• GPU: RX 560
• Video driver version: amdgpu
• Kernel version: Linux 5.10.0-33-amd64 x86_64
• Link to full system information report as Gist: https://gist.github.com/Qiset/a6bbdb3240a396715dcac4a46984233d
• Proton version: 7.0-6

I confirm:

• [ x] that I haven't found an existing compatibility report for this game.
• [ x] that I have checked whether there are updates for my system available.

No such file was created. Is this perhaps because the game runs with no errors it just has rendering problems but doesn't see that as an error?

Symptoms

Rendering of certain terrains within the game fails. Examples are the land and water in the Ocean of Tears ( solid black and solid green, respectively) or the land in North Ro or South Ro (also solid black). Certain items are also not rendered correctly such as the Words of Darkness or The Harvester (both of which render completely white). I'm not sure of the date of this occurrence, since there was a gap of about a year between now and when I previously played this game.
The only reference to this issue was on the Everquest web site in the comments. Someone suggested that it might be caused by the drivers especially if it was an Nvidia gpu. I was using a GT 1030 Nvidia card so I switched out the card to this RX 560. The same problem occurs with both.

Reproduction

This issue is present every time I run the game. I've verified that it doesn't occur when running the game in Windows 11 only when running it on linux.

[Qiset]

I upgraded my graphics card to a GeForce GTX-1070. It still has the same problem. I went through all the various version of the proton compatibility. Experimental, Hot Fix, and 9.0-4 failed to run giving the error that no 3D devices found. 8.0-5 claimed that my video card wasn't good enough to run the game. 7.0-6 runs the game but still gives the rendering problem. I noticed that this problem is not assigned to anyone. What does that mean? How is it going to get fixed?