ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.62k stars 1.07k forks source link

Crysis 2 - Maximum Edition (108800) #849

Open ttyborg opened 6 years ago

ttyborg commented 6 years ago

Works perfectly.

Distro: Ubuntu Mate 18.04.1 Kernel: 4.15.0-33-generic Resolution: 1920x1080 CPU: Intel Core i5-8600 GPU: GTX 1070, Nvidia proprietary driver 396.54 RAM: 16GB

pszabo75 commented 6 years ago

Doesn't work on my machine.

Distro: Fedora 28 Kernel: 4.17.18-200.fc28.x86_64 Resolution: 1920x1080 CPU: Intel Core i5-8350u GPU: GeForce MX150 with 2GB RAM, Nvidia driver: 396.45 RAM: 16GB

The game throws an error message about a falsely identified video card then freezes at the Crytek splash screen. Here's part of the log: ActivateProfile profileName default Running machine spec auto detect (32 bit)...

SteveHeist commented 6 years ago

@pszabo75 Wait a second, your saying you have an MX150 but your machine spec auto detect says you have a GTX 470? Might that be your issue?

SteveHeist commented 6 years ago

I'm really not sure how to go about fixing it if it is, but that's very possibly the problem.

ttyborg commented 6 years ago

@pszabo75 Just to clarify, is that a notebook, and if it is, what brand and model?

pszabo75 commented 6 years ago

This is a notebook. A Lenovo T480 with Geforce MX150. I have the proprietary Nvidia driver installed. The Nvidia control panel identifies the GPU correctly. Native Linux games installed from Steam identify the GPU correctly. And yes, according to the logs and the error message that pops up after launching Crysis 2, it seems to be identifying it as a GTX470.

BLaDZer commented 6 years ago
System:    Host: blad-pc Kernel: 4.18.4-1-MANJARO x86_64 bits: 64 Desktop: Xfce 4.12.4 
           Distro: Manjaro Linux 
CPU:       Topology: 6-Core model: AMD FX-6100 bits: 64 type: MCP L2 cache: 2048 KiB 
           Speed: 1542 MHz min/max: 1400/3300 MHz Core speeds (MHz): 1: 1521 2: 1521 3: 1567 4: 1683 
           5: 1518 6: 1568 
Graphics:  Device-1: AMD Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] driver: amdgpu 
           v: kernel 
           Display: x11 server: X.Org 1.20.1 driver: amdgpu unloaded: modesetting 
           resolution: 1360x768~60Hz 
           OpenGL: 
           renderer: AMD Radeon HD 7800 Series (PITCAIRN DRM 3.26.0 4.18.4-1-MANJARO LLVM 6.0.1) 
           v: 4.5 Mesa 18.1.6

Game works almost fine(except random fps drops which may caused by ntfs driver or maybe not).

At least there is one bug - gamma can't be changed. On windows this option change the whole system gamma/brightness.

rednaxela600 commented 6 years ago

EDIT again: After being linked to #813 to resolve driver issues, everything seems to work just fine. Just user error for me.

EDIT: Indeed I am an illiterate idiot! I used the more correct PROTON_USE_WINED3D11=1 and Crysis 2 rendered everything correctly. Since using OpenGL d3d11 over DXVK d3d11 worked, I'm unsure if the problem is in the vulkan mesa driver, dxvk, or simply the muxless switchable graphics setup. I did have to launch steam with "env DRI_PRIME=1" for the amd card to work. Performance was decent albeit lower than my hopes, but the game felt sluggish in a non-framerate related way I have a tough time describing. On the other hand using PROTON_NO_D3D11=1 to force dx9 made the performance flawless, even on Ultra settings (1920x1080)!

OLD POST: Only partially works for me. -Cutscenes appear as pure magenta/pink. -Font/Text does not render correctly they appear as rectangles with size varying appropriately by letter.

The rest of any scene appears to render correctly though performance is questionable. As font does not work I cannot determine my settings, I struggled to navigate the menu to start a new game even. I didn't play far enough for combat so there may be more problems, but that didn't appear to be the case.

I attempted to use "Set Launch Options" for wined3d11 and nod3d11 and results did not change. Either I did it wrong (far from impossible) using wined3d11=1 %command%, or crysis defaulted to dx9 for me to begin with. Using DRI_PRIME=1 crysis determined the 8970m was a Radeon HD 7800, which I don't believe to be a bug as I also believe the 7970m,8970m are just desktop 7800s or at least very close. I know this because it gives me the same unsupported card error I believe pszabo75 is receiving.

(If more info is needed, I'm still inexperienced with linux, so please tell me what commands I would need to run)

OS: Linux Mint 19 Cinnamon 64-bit CPU: i7-3630qm GPU: Intel HD 4000 + Radeon HD 8970M (4GB) muxless setup Driver: Mesa 18.3.0

glxinfo.txt

atm-florian commented 5 years ago

Broke with proton 4.2-1. Work really fine with previous proton version. With 4.2-1, at launch, it try to install a patch and cannot find games files where to install patch, so game not launch any more

kisak-valve commented 5 years ago

Hello @atm-florian, please opt into Steam's beta client and/or go to Steam -> Library dropdown -> Tools and install Proton 4.2 from the list.

If that has no effect, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Also, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

rednaxela600 commented 5 years ago

@atm-florian is right, just tested myself. 3.16-8 works well with tiny bugs, but 4.2-1 does exactly as they described. I have 4.2-1 installed from tools as well, so that's not the issue. It's a little bizarre, but for some reason the game is searching the entire Z: drive (I assume that's because the game files are in the steamapps folder still instead of in the prefix where the C: drive would be). That did not seem to be an issue before, but something has the game convinced it suddenly needs to download a patch, like it can't see its own files or something. I'm going to include a log with a successful 3.16-8 launch as well.

System Information:System_Information.txt Proton_Log_4.2-1:steam-108800.log Proton_Log_3.16-8:steam-108800_3.16.log

kisak-valve commented 5 years ago

These appear to be lines of interest in the log:

warn:debugstr:OutputDebugStringA "WinHTTPChannel REQUEST_ERROR - error 12152, result API_RECEIVE_RESPONSE"
warn:debugstr:OutputDebugStringA "CoreAbstractDownloadJob::Tick - Job:\"CP_Guest_44(1)_ver3:;Crysis2Patch01\" is in error with code:20003... "
warn:debugstr:OutputDebugStringA "Job is in OS error 12152 state"
warn:debugstr:OutputDebugStringA "Download error 20003 (OS: 12152)"
atm-florian commented 5 years ago

Seems to be fix with proton 4.2-2 (still 4.2-1 into steam menu but ~/.steam/steam/steamapps/common/Proton 4.2/version says proton-4.2-2)

RiantAnda commented 3 years ago

I can't activate "High Res Textures" under "Advanced Graphics Options". Crysis2_HiRes I'm running Proton 6.3-5 and a Nvidia GPU.

There is an open bug at winehq Seems to be related to the GPU memory reported to the game. ~~I tried setting in dxvk.conf: dxgi.maxDeviceMemory = 1536 dxgi.maxSharedMemory = 1536 but this doesn't work.~~

I have the suspicion that the above setting is DX11 only, but we need this for DX9(error message at game startup displays the d3d9.customDeviceDesc setting), however this setting does not exist for D9VK, it seems?!?