

eas drm borked it

After starting the game, the audio changes during the loading process, causing the bass to become less noticeable. The solution is to switch to the correct Playback Stream (in my case, Easy Effects Sink) at the system level.
Once the game loses focus and switches to windowed mode via Alt + Tab, it becomes impossible to return to fullscreen mode. However, the game remains fully playable without any issues.

Works good (singleplay)
Played with Proton 9.0-4. EA app autoinstalls correctly.

The game runs very well by default at a smooth 60fps. When I opened the game for the first time, it automatically selected a community template for input controls, which made the stick to have a weird drift. After I selected the official template and restarted the game, everything was fine. The settings that I used are:
- Screen Resolution: 1280x800
- High Resolution Textures: On
- Motion Blur: High
- Shadow Level: High
- Headlight Shadows: On
- Ambient Occlusion: Medium
- Reflection Level: High
- VFX Detail: High
- Geometry Detail: Medium
- Light Scattering: On
- Super Sampling: Off
I highly recommend giving this one a go. Due to the easy nature of getting into a race, you should have no issues playing only 1 or 2 if you're short on time. The game doesn't have a proper story aside from beating the Most Wanted list.
There's one last thing that I want to add. I'm pretty sure that the game has an input lag to some extent, because it was a bit tricky to control cars at high speed. After a quick search on google, my assumption turned out to be true but hopefully , others have found a fix. So, if you're having issues with controls, you may want to try out those suggestions.

Any anti-aliasing (or supersampling) drops the framerate
Crashed during settings change
Couldn't get the contrast and brightness just right; would either be too washed out or dark
Unsupported
if you want to mute your microphone, you need to change it to some dumb input

Switchimg to Proton 7.0-6 allowing the correct installing of EA app. After installation, switching to Experimental to launch the game.

sometimes ea app fvcks it up and start the game in window mode, other than that works well w/o problem.
just "enable steam input"
it wont play w/o the internet

Switching windows permanently disables fullscreen until the game is relaunched. Might be possible to work around with Gamescope (not supported on my hardware) or enabling desktop mode in winecfg, didn't test.
I used Sarek because of my old GPU, it probably works on regular Proton as well, or at least GE (Sarek incorporates GE patches). I might submit a report with regular Proton/GE and a different GPU later.

OOTB works fine
Unfocusing the game will make it windowed with no fix to return back to Fullscreen
Do not use SteamInput, use the game own controller support
EA App is fixed
MESA_VK_DEVICE_SELECT=1002:1681! %command%
Doesn't seem to work with Nvidia drivers, had to force integrated amd igpu for Mesa

PROTON_USE_WINED3D=1 %command%
- Download game from: https://archive.org/details/NFSMW_BlackEdition
- Mount the iso at /mnt/nfsmw ( or anyware you like ), let call it as dvdPath
- On steam, go to add a game/add a non-steam game and look the the dvdPath/AutoRun.exe
- At the game property, go to compatibility and select ge-proton9-22
- Run AutoRun.exe
* if it fails in the first time after you put the serial number, just run the AutoRun.exe again;
- After the instalation, do not try to run the game;
- In the game properties change the target to dvdPath/Patch/nfwmwpatch1.3.exe
- Run the patch;
- Locate the game prefix on steam ( usually at: %USER%/.steam/steam/steamapps/compatdata/) look the the last modified folder;
- Inside the prefix folder go to : /pfx/drive_c/Program Files (x86)/EA GAMES/Need for Speed Most Wanted/
- Copy and replace the speed.exe from dvdPath/Patch/speed.exe
- In the launch options set : PROTON_USE_WINED3D=1 %command%
- Select the target as speed.exe from your full prefix path. Ex: `/home/retro/steam-games/compatdata/<your-game-prefix-here>/pfx/drive_c/Program Files (x86)/EA GAMES/Need for Speed Most Wanted/speed.exe`
- Launch the game;
If you want to use the WidescreenFix:
Extract the content inside your game prefix. Ex: "/home/retro/steam-games/compatdata//pfx/drive_c/Program Files (x86)/EA GAMES/Need for Speed Most Wanted/"

EA Launcher sucks. This game is a waste of $3 and I wish I set my money on fire instead.
Installed a version without DRM.

The game is totally unplayable in my experience. Textures and shaders are tremendously broken.
PROTON_USE_WINED3D=1 %command%
The car engine kept crackling and chopping.
The game shaders are completely blacked out, the textures turned extremely grainy.
The game doesn't save my progress at all.

PROTON_NO_ESYNC=1 WINEDLLOVERRIDES="dinput8.dll=n,b" %command%
Opens in fullscreen, but focusing another window causes the game to change to windowed, and there's no way (including keyboard shortcuts) to re-establish fullscreen without relaunching the game
Steam says controllers are not supported but with Steam Input, all of the ones I've tried have worked perfectly

If you alt-tab at any point, the game will force itself into windowed mode and there is NO way of getting back into proper full screen.
Controller frequently kept disconnecting. Also, enable Steam Input in the game's settings under the "Controller" tab. Otherwise it will not detect ANY controller at all.
Previous reports mention that using Proton 7.0-6 would fix the EA app issues. It didn't for me. What ended up working was Glorious Eggroll Proton, which launched the EA app properly and let me launch the game.
Once it got going, the only other issue I saw was that it couldn't read my name from the EA app for some reason and showed me as an auto-generated string of characters.
Besides that, the game ran fine, minus the full screening and controller issues.

First you'll need to launch this game in Proton 7.0-6 in order to get the EA App to install properly.
The EA App installer will crash instantly if you try to run the game under Proton Experimental for the first time. First, you'll need to run proton 7.0-6 in order to get the EA App installer to launch properly. Once you install the EA App under proton 7.0-6, then you'll be able to launch the game with Proton Experimental. I've experienced no gameplay issues with Proton Experimental.

Doesn't work, as in previous report
As in previous report
In terms of running the game through Steam, nothing changed. However, I was able to find a certain workaround, which I am sadly not able to share - if I did, EA would send a hitman after me, because it involves doing very immoral things like: actually owning the game without useless launchers, DRM and kernel level anticheats (I mean, the last one doesn't apply to this game, but in general). I will however say that after attempting said workaround the game works perfectly in regular Wine 9.19 without additional tweaks (so it would probably work in regular Proton as well). It works so well in fact, that I think I will apply this workaround to any other EA game I might want to play in the future.
Let me just end this report with this completely unrelated quote from the owner of a certain game distribution platform related to ProtonDB.
Piracy is almost always a service problem [...].
Gabe Newell, 2011
What you do with this information is up to you.
Similar issues to others. Attempted all proton versions and EA App would crash every time.

A black launcher window appears for a split second, then crashes
Tried:
- Proton GE
- Proton 7.0-6
- Proton Experimental
- Running the game from an NTFS partition
- Unsetting LANG/setting LANG=en_US.UTF-8
- The NixOS launch options (just to see if anything happens)
A few times during tinkering the launcher didn't crash (not sure what caused that), in those cases it says "Preparing game..." and loads infinitely (waited about 15 minutes).
I also tried running the game on two other PCs with similar software setups, one with Intel iGPU and one with AMD GPU. They don't work in the same way.

for var in $(printenv | awk -F= 'length($2) > 2000 {print $1}'); do export $var=$(echo ${!var} | rev | cut -c 1-2000 | rev); done ; %command%
Ever since the update, this is the standard solution to get past whatever bugs out the EA launcher. Other than that, it works as it should.

EA App crashes with half a second of launching, game never starts.
Used to work out of the box with Origin Launcher, but doesn't work now with the stupid EA App. I also tried with Proton Experimental, same results.

for var in $(printenv | awk -F= 'length($2) > 2000 {print $1}'); do export $var=$(echo ${!var} | rev | cut -c 1-2000 | rev); done ; %command%
I must credit the launch options to the user "SuperSamus" on GitHub, found their comment on issue #6766 from Nov. 2023, on Valves' proton repository. Worked completely flawlessly after the addition of that for NixOS.

Game opened without needing to install the ea launcher in desktop mode. Runs at a smooth 60fps with max settings, so limit to 60.
When launching the game for the first time the left stick drifted to the right. The issue was fixed when opening the game for a second time.
Functions without any big hassle. May require a reboot of the game after the initial setup to get the controls working right.

I can't found fullscreen option, the game run in window
The game has no support for gamepad, and for some reason, my gamepad worked without Steam Input mapping. I felt a short delay while control de car direction!
The game start with no sound when I use the default Steam's Proton (maybe it use Xact for sounds). So I needed to change from experimental version to GE-Proton7-54

Overall unplayable. - Laggy inputs - unable to race properly due to extremely low FPS - no fullscreen mode. Everything else seems to work
very low FPS rate + laggy inputs

for how small the playerbase is now it was a miracle that I was able to find a lobby other than that it ran great on my galaxybook and pc (both use intel cpus and graphics)
This game is OLD so it runs like a champ, even with EA's BS. Still the fun game I love and it runs on linux

Worked fine
Worked fine on my system without any issues

The only thing to note is that the EA app is a bit tedious at first and may crash. I found the best version of Proton is 6.3-8, it works flawlessly afterwards.
I haven't tested multiplayer but I presume it will work as it found a few players. Very playable on Intel integrated graphics (i5 8250u) using Fedora KDE, 900p and 768p low settings is the sweet spot.
Switched to older version just for installation. Also, had to change $LANGUAGE from Polish (pl_PL.UTF-8) to en_US.UTF-8 so that the installer doesn't return error 81-12B2

Vous devez lancer le jeu avec une connexion internet pour EA app, une fois en jeu, vous pouvez couper votre connexion.
Rien à signaler.
On dirait que ce jeu est fait pour le steamdeck !
60 fps constant, graphismes à fond et il ne chauffe pas, avec une batterie qui dure.
Il ne faut pas mettre d'antialiasing, sinon il se bloque à 30 fps.
Je recommande fortement de l'acheter pour des sessions solo (comme dans un train).

Здебільшого, гра встановлюється за принципом "запустив та грай", значних проблем не було помітно.
TDP 8-9
Потрібно було використати сенсорний екран або мишу, щоб натиснути на кнопку "Продовжити" у EA App.
В дуже рідкісних випадках, проїжджаючи тунелі та закриті місця, ефект луни давав потріскування та тимчасове пропадання звуку. Траплялося дуже рідко.
Внутрішньоігрові ролики (які на рушії програються) зламані, все інше: без проблем.
Зовнішній геймпад від XBOX гра сприймає як клавіатуру.
Іноді показує помилку підключення до серверів ЕА. Проте, через кілька спроб, підключення встановлюється.

Worked out of the box (when it was installed on ext4 drive. If installed on NTFS drive, tinkering is required)
Stutters a bit.
For it to work out of the box, you should install it on ext4 drive (in my experience). If you want to still install it on NTFS drive, you will have to make a soft link of compatdata folder on NTFS drive to compatdata folder (generally) on home drive.

Not working. EA app crash on start.
EA app will open blank window for 2 seconds then it crashes.

Runs fine, except for the crash in Emerson Beltway.
When alt-tabing, the game will go windowed and it won't be back to fullscreen until restarted.
One of the races crashes frequently (Emerson Beltway). I found that waiting a bit at the beginning to avoid getting into the pack helps quite a lot. It's the only race with this problem, the rest of the game is perfectly fine.
The game doesn't really feel fluid even if mangohud displays a stable 60fps. I guess it's an engine problem, not really related to Proton.
mangohud gamemoderun %command%
Speaker setup sometimes gets switched from 7.1 to 5.1 on startup. Doesn't happen during gameplay.
Just like on Windows, unfocusing causes the game to switch from fullscreen to windowed. There's no option in-game to fix it.
Turn off Steam Input.
Previous save from my Windows days got wiped. Possibly because I had replaced EA App with Origin, this might have messed up EA's cloud save. Make a backup if you can.
Just like on Windows, playing the game with Above 4G Decoding and/or Resizeable BAR causes massive frame loss. I'm mentioning this because, for whatever reason, some idiot has decided to recommend activating these on Linux Gaming wiki.

Game won't run at all if you are offline, I think it has to do with the EA app launcher thingy. The moment you turn on wi-fi, it works just fine.
Fullscreenborderless=true
Could not maximise or fullscreen after(fixable)
Same as Windows. Game is on Peer 2 Peer so it may depend on lobby.
Fullscreen fix: I'm on KDE Plasma so it may be different for other DEs. -Alt+F3 or click icon in top-left corner -More options -Configure Special Window Settings -Add properties -Click fullscreen -Exit the "Select Properties" window -Change from "Do Not Affect" to "Force" -Click OK The game should be fullscreen now.
After loading main menu it just closes game without any error windows. Steam Deck, default proton settings.
Default controller preset caused the menus to keep scrolling right so I changed it to a generic controller layout to fix it
60fps solid with no dips
Mix of high/medium settings
I had 0 issues