Have try Prototype & Prototype 2 for me not work :(

yeah same for me, I'm unable to make it work

Prototype 2 still not launching :(

Prototype 2 still not launching :(

works with winXP compatibility and with xaudio2_3="native"

@bear-bulloff could you provide some more info? are you running with lutris or steam proton?

@bear-bulloff could you provide some more info? are you running with lutris or steam proton?

Tested with both Steam Proton 6.3.6 and system wine-staging 6.17. Very strange game behaviour. With xaudio2_3="native" an error pops up, but when you press ok the game works, but no sound. If xaudio2_3="builtin" then the game hangs. If run with a third party prefix the game works without errors and with sound

steam-10150.log

.

Compatibility Report

• Name of the game with compatibility issues: Prototype 2
• Steam AppID of the game: 115320

System Information

• GPU: AMD Radeon RX 580
• Driver/LLVM version: Mesa 21.2.4/ LLVM 12.0.1
• Distro version: Arch Linux
• Link to full system information report as Gist:
• Proton version: experimental-6.3-20211027

I confirm:

• [ ] 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

• Crash after launching the Game.

Reproduction

• Start the game.

Logs

• steam-115320.log

Notes

• Retest for CEG DRM.

With Proton: 1635544687 experimental-bleeding-edge-6.3-1836-20211029-paf96ce-w8a5bac-d1b1206-v430c77, the Game Starts, but be aware the Game has lots of Bugs. See Prototype 2 at pcgamingwiki

Seems I do something wrong, this is all I get from starting the game:
steam-115320.log

Seems I do something wrong, this is all I get from starting the game: steam-115320.log

You need to use the "bleeding-edge" Beta of proton-experimental. Additional to that, you can try to rename/remove the game´s prefix directory and let the Steam Client verify your game files.

I'd love to play the game, but it just crashes at startup no matter what I try...

So, got finally bleeding-edge compiled.
Still getting next to nothing in the log.
steam-115320.log

Hi,

here is the output:
steam-output.txt

Seems something weird is happening, because if I understand correctly, it tries to use proton 6.3-3.
But in the GUI I had configured my bleedingedge version, but even before that it was configured to
use 6.3-7.

Was too late, saw your comment appearing.

Read now quietly the log again and /home/dslinuxuser/.local/share/Steam/steamapps/compatdata/115320/tracked_files
was missing.
Created it with "touch /home/dslinuxuser/.local/share/Steam/steamapps/compatdata/115320/tracked_files", after that
it starts and can load my save from 7~ years ago.
Have to play a bit and check if it works.

Wow, you did it Proton development team.
Was finally able to try Prototype 2 with Proton bleeding edge.
Had to do at least the following stuff:

• unplug all USB gamecontrollers
• set these launch options: PRESSURE_VESSEL_RELAUNCH_CONTAINER=1 PROTON_LOG=1 WINEDLLOVERRIDES="xaudio2_3=b" taskset -c 0,1 %command% windowed

With taskset and 1 core the game would just loop in loading screen.
With taskset and 2 cores it started to work.

This game is from the standpoint of a developer a piece of garbage, has so many errors, bugs and problems.
But now, with Proton bleeding edge and this monster of launch options I am finally able to play Protoype 2 again.

Tinkered a bit.
Game controller won't work, but this was already a problem with Windows 7, game code is bad.

But "windowed" is not needed, so the launch options look like this:
PRESSURE_VESSEL_RELAUNCH_CONTAINER=1 WINEDLLOVERRIDES="xaudio2_3=b" taskset -c 0,1 %command%

I would say, only the launch options need to be altered to this and the issue can be closed.

@DSLinuxUser The PRESSURE_VESSEL_RELAUNCH_CONTAINER option was set by default to 1 since about a year ago. Additionally, several months ago, this option has been completely removed, effectively hard coding it to 1 without the ability to disable it.

So if it works with PRESSURE_VESSEL_RELAUNCH_CONTAINER=1, even without it should definitely works too.

Thanks for clarification.
You are right, just changing to "taskset 0,1" is enough.

could I provide some more details? this still isn't working... I'm on arch linux, Ryzen 9 cpu, GPU is a 1080

Also unable to launch with GE Proton or Proton Experimental using taskset 0,1 %command%.

From comments on ProtonDB it seems to suggest that the version purchased and installed through Steam is a little different to ones that have come from key sellers? Although I'm unsure how that can be a difference, surely they are the same repository?

1. Had to change the parameter to PROTON_USE_WINED3D=1 WINEDLLOVERRIDES="xaudio2_3=b" taskset -c 0,1 %command% , seems that one update broke something so that Vulkan can't be used.
2. Because of the whole nature of this game, either Radical or Activision had to create a cut version for multiple countries.
   My version, which is the German cut, has various problems some other versions don't experience.
   Thankfully to the community, Wine, DXVK and Valve, the German version can be played again.
   Well for Linux, on Windows it is broken.

Most stable is the English uncut version.
I would guess the reseller gave you a key for one of the cut versions and it just does not want to start.
You can try some of the fixes mentioned on PCgamingwiki, but don't expect guaranteed success:
https://www.pcgamingwiki.com/wiki/Prototype_2#Issues_fixed

Thanks, I tried those full parameters, but still a CTD as soon as I start.

Interesting about the different regions, I'm trying to run it on the Steam Deck, and I don't have any peripherals installed, not sure what else I can try.

Ah, Steam Deck, that is critical information.
You already saw the comment about the peripherals. Good.

Now to the bad part: this game "will never work on the Steam Deck".
On Linux and Windows this game either crashes on start or straight won't accept any input,
if peripherals are connected.
So, in order to be able to start the game, you would need to open the Steam Deck and remove:

• thumb sticks
• touch pads
• all buttons (shoulder, dpad, etc)
• maybe even the touch interface

After that, maybe, maybe the game will start and or work and now you could plug in
Keyboard/Mouse to be able to play it.
Yes, this is "impossible" from a convenient standpoint and I would not do it either.
Sadly, but Radical/Activison screwed Protoytype 2 code wise even more up than Prototype 1.

I see, thanks for the feedback

The game works perfectly for me, though I did use a 'community patch'
It worked out of the box, with my dualshock 4 controller detected and mapped correctly.
However, it did crash trying to load the videos, changing the operating system to windows 7 from 10 fixed that as well.

🛠️ Proposed Fix: Limit CPU Cores for Prototype 2 (App ID 115320)

Description:

Prototype 2 (App ID 115320) experiences crashes during startup when run on systems with multiple CPU cores or hyper-threading enabled. This issue has been observed on both Windows and Linux platforms using Proton. A common workaround involves limiting the game's CPU affinity to a specific number of cores.

proton:

default_cpu_limit = {
"19900": 16, # Far Cry 2
"298110": 16, # Far Cry 4
"20920": 16, # The Witcher 2: Assassins of Kings Enhanced Edition
"35130": 16, # Lara Croft and the Guardian of Light
"55150": 16, # Warhammer 40,000: Space Marine
"204450": 16, # Call of Juarez: Gunslinger
"15620": 8, # Warhammer 40,000: Dawn of War II
"20570": 8, # Warhammer 40,000: Dawn of War II – Chaos Rising
"56400": 8, # Warhammer 40,000: Dawn of War II – Retribution
"618970": 4, # Outcast – Second Contact
"10150": 8, # Prototype
"115320": 8, # Prototype 2
"2229830": 1, # Command & Conquer and The Covert Operations
}