Crysis 1 crashes first level #783
Comments
Please actually do that. That said, the game did was working fine a while ago, please test if it works with an older DXVK version (such as 0.70). |
|
I've never done am apitrace before, please be patient, I also tried the approach to get those three x64 files from the wiki, where it talks about, if you have trouble with an apitrace put these in the folder with the game.exe. When I did that, I get this output with dxvk dlls as biltin: when it says "DO NOT use DXVK together with apitrace!" does that mean to set the dxvk dlls to builtin, in the winecfg window? |
|
Just tested this on my AMD rig and the game runs fine, so I don't think an apitrace would be particularly useful here. Have you tried running it in a clean wine prefix with just d3dcompiler and dxvk installed (i.e. without PlayOnLinux magic)? For future reference, you'd need the msvc-latest build of apitrace in order to record D3D10 traces. |
|
I did make a new wineprefix, just now actually. The playonlinux, is just the location of the wineprefix, I did not use the playonlinux program. I made a new wineprefix, win64, installed latest dxvk, and d3dcompiler with winetricks, copied over the game folder, from the old prefix. Tried running it, same stop point. I then used winetricks to install 0.70 dxvk, and same problem. Since it runs on AMD, is there a way I could make the game think I have an AMD system instead of Nvidia? |
|
@Teuwu Can you please try a different Wine version with a clean prefix? Wine 3.21 fixed a possible 3.20 regression in Crysis Warhead and maybe Crysis 1 was also affected but wasn't reported. |
|
Can confirm that this game hangs on my Nvidia rig with both the 396.54.09 and 415.something drivers. No idea why. |
|
@Teuwu Playonlinux wine builds do not have vulkan enabled. They are working on a new build system for that. So I hope you got your wine version from somewhere else (or maybe it has changed recently?). |
|
@ImperatorS79 on my system setup ~/.PlayOnLinux is where I have a 1TB HDD mounted as game storage, its just LOCATION I get my wine builds from the official winehq repo, or build them myself, for crysis 1 + dxvk, I've only used the official winehq builds from their ubuntu 18.04 repo, normally staging builds. changing the vender and device IDs in the dxvk.conf, file no change still crashes. I tried using the winehq-devel 3.21, as I don't yet have winehq-staging-3.21 only 3.20 for staging so far I also just tried the 390.89.0 Nvidia driver, and still no go, just crash as in OP. The tests mentioned in this post were run from a clean wineprefix just dxvk 0.93 and d3dcompiler. |
|
I tested the GOG version (64 bit) with Proton 3.16-4, Proton 3.16-7 (Beta) and Wine-4.1 (Staging) + dxvk70. It hangs in all three with dx10 mode when loading a game. I'm using an AMD RX570 with Mesa 18.3.2 |
|
@itaranto your issue is that you don't have the d3dx libraries installed, use |
That worked! Thanks! One little detail, I first installed d3dx10_43 over the existing installation, that didn't worked. The map loaded correctly with the "Press any key to continue" button, but after I pressed that I got a black screen. So, I re-created my prefix and installed the libraries in this order: And... that worked like a charm! I tested with everything at "Very High", really good FPS. Thanks, you are awesome! |
|
I've found that - repeatedly - installation of whole directx9 via winetricks, + manually setting up d3dcompiler_* up to version 47, is required for Crysis 1 expansions, Warhead, to work. It also affect the most popular mod on the engine, MechWarrior: Living Legends (but in the end, it works, awesomely!) |
|
On my system Crysis (from GOG) hangs on startup but when I run a benchmark batch file or make it load a level directly from a batch file like so System information EDIT: Problem was caused by calling |
No. |
|
Not sure what you mean but that's the driver version reported by DXVK (ok, minus the "Nvidia" text). The Nvidia driver itself just says 430.50. |
|
ok a lot has changed since my opening post. but I can now say that the game works. I copied all the data from my last system to start crysis, the wineprefix reports to have DXVK version 0.93 so really old! the wine version I have setup to launch wine with is 4.12.1 (I'm assuming from winehq) also obviously old. my libraries override from winecfg are: *d3d10 (native) so I'm thinking that the addition of d3dcompiler_43 is what makes makes this game work. i'm also running the GoG 32bit version. |
|
so I started with a clean wineprefix (wine 4.21 staging) I then used winetricks to install d3dcompiler_43, and the game would load fine, I quit at the scene where the people are in the airplane, before the skydive. to test again created a clean a prefix, installed dxvk d3dx10_43 tried loading the first level, got a crash few seconds in tried 32 & 64, then I installed d3dcompiler_43 conclusion d3dcompiler_43 and d3dx10_43 are required. Closing. |
|
Hi, I've created a clean wineprefix, executed Here are some logs: Here is the terminal output: |
|
It's still using the Wine implementation of d3dcompiler so that didnt work. |
What do you mean? Should i download the d3dcompiler_43.dll and put it into game dir? My wine overrides are the following: |
|
And you are sure thats the correct prefix thats also getting used for the game?
|
|
yes, im sure that i did use the correct wineprefix. Edited: I've tested with a downloaded d3dcompiler_43.dll and it will crash while loading now, not even showing "press key to play" |
|
@AlexanderWKoenig Are you using the GOG version, or the Steam version? I had this problem with the GOG version (I think it only affected the 64bit binary), but I got it on Steam and it seems to work fine. |
I've just tested the 32bit binary, and I dont know which version of the game it its. It just happened to be on my hard drive ;-) |
|
I believe the Steam version only has the 32bit binary. The GOG version has both 32bit and 64bit. I Haven't noticed any performance differences between the two, but I think DXVK still has issues with 32bit games. Not sure about the original physical version, or the Origin version. |
I launch the game, get to the main menu, load the first level, after the first part in the cave after the ship opens, there is the first white screen, this is the point at with the game crashes. The game runs ok in dx9 mode. This is the GOG.com version of the game, I've also tried with the version from the original DVD and same deal.
yes, I do have d3d_compiler43 as an override.
These are the commands I use to start the game:
export DXVK_HUD=devinfo,fps,version
export WINEPREFIX=~/.PlayOnLinux/wineprefix/crysis_warhead_gog/
cd ~/.PlayOnLinux/wineprefix/crysis_warhead_gog/drive_c/GOG\ Games/Crysis/Bin64
wine Crysis.exe -dx10
I'm just not sure what I'm doing wrong, as doitsujin showed it working with the version that introduced dx10 support.
Software information
Name of the game, settings used etc.
Crysis 1, everything lowest
System information
Apitrace file(s)
Log files
Crysis64_d3d10.log
Crysis64_d3d11.log
Crysis64_dxgi.log
Crysis_d3d11.log
Crysis_dxgi.log
The text was updated successfully, but these errors were encountered: