search

ValveSoftware / Proton

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

Starfield (1716740) #7064

Open vercingetorx opened 1 year ago

vercingetorx commented 1 year ago

Compatibility Report

System Information

I confirm:

todo ## Symptoms

The game starts up and seems okay but when starting a new game the game freezes during first load. Experimental freezes and 8.0 crashes.

r4m0n commented 1 year ago

I'll live with 30 FPS on Low on a 2080 Ti for now...

stubkan commented 1 year ago

What does ''cat /proc/driver/nvidia/version'' output for you @benbot ? Cos when I installed 530 it installed 535.104 for me, and that didn't work for me.

lordsutch commented 1 year ago

Is anyone on an AMD card and have it not working?

Yep, 5950X + 6950XT, hanging shortly after E for New Game. Same report as OP, tried on both 8.0.3 and experimental.

Same here, I can confirm on 7700X and 6700 XT on Linux Mint 21.2 with both the "stock" 5.15.0-82 kernel and the 6.2.0-31 kernel and Mesa 23.0.4 using Proton-Experimental. The game crashes about 10-20 seconds after "Start New Game" and kills my login session, leaving an amdgpu page fault in my kernel log.

benbot commented 1 year ago

@stubkan im on a different distri than yours, so that command didn't work, but the 530 drivers are the only ones installed.

stubkan commented 1 year ago

@benbot It would help if you confirm the exact version number of 530, ie the latest is 530.41.03

https://www.cyberciti.biz/faq/check-print-find-nvidia-driver-version-on-linux-command/

benbot commented 1 year ago

@stubkan it was 530.41.03

I'm trying 535.54.03 now

benbot commented 1 year ago

Yeah 535.54.03 has the same issue as older drivers.

No crash, but painfully slow.

ghost commented 1 year ago

Downgraded the following packages linux-lts linux-lts-headers nvidia-dkms nvidia-utils lib32-nvidia-utils

Arch Linux Kernel 6.1.49-1-lts NVIDIA packages to 530.41.03

Resolved issue, only getting 30fps, but it sure beats no launch.

devourers commented 1 year ago

Have the same issue, tried custom GE (8-13), hotfix as of now, 8. With all 3 atfer "new game" it freezes and refuses to close (or even show my mouse when I Alt-tab). Tried leaving it open for ~10 minutes (as if may be it was loading really long and messed up threading so it appears stuck), but to no avail. Arch-Linux Latest stable NVIDIA driver (535.104.05-2) and kernel, RTX 4080.

WarBaby2 commented 1 year ago

Have the same issue, tried custom GE (8-13), hotfix as of now, 8. With all 3 atfer "new game" it freezes and refuses to close (or even show my mouse when I Alt-tab). Tried leaving it open for ~10 minutes (as if may be it was loading really long and messed up threading so it appears stuck), but to no avail. Arch-Linux Latest stable NVIDIA driver (535.104.05-2) and kernel, RTX 4080.

Same here, only on an RTX 2070... latest zen kernel and NVIDIA driver. I noticed that turning off the compositor made starting the game a bit smoother, but it still crashes after choosing new game.

rwiggins commented 1 year ago

Can confirm, 530.41.03 w/ linux-lts 6.1.49 works at ~30ish FPS (regardless of settings) and occasional minor graphical glitches. Lightly tested Proton Experimental, Experimental [bleeding-edge], and GE Proton 8-13, no observed differences. Going to wait for a fix -- 30 FPS is tolerable for a bit, but painful esp during combat.

On the latest 535, I did notice dropping the settings to low across the board got me past the loading indicator and to the first title intro for a new game, but the game froze shortly thereafter anyway with the same error. So the problem is at least partially affected by gfx settings, in my experience, but I have yet to find any magic setting that bypasses the issue.

g0dsCookie commented 1 year ago

NVIDIA RTX 3070, Linux 6.1.49 and nvidia-535xx didn't work for me either.

Downgrading to nvidia-525.116.04 fixed it and I could start playing with about 22-30 FPS - didn't test 530xx yet, though I guess performance will be about the same at around ~30 FPS.

bowes332frank commented 1 year ago

That is super new for M$.

WarBaby2 commented 1 year ago

That is super new for M$.

Yup, well, sadly we are in the middle of a "who the hell cares" nexus here... M$ doesn't care about Linux, NVIDIA doesn't care about Linux and BSG doesn't really care about NVIDIA.

CP2077 has been broken under Linux for most NVIDIA cards for a couple of months now...

bioxz commented 1 year ago

With an 6950XT on Arch using experimental I'm stuck with the "Graphics card does not meet minimal specification requirements." pop-up. Any idea how to circumvent that? OP mentioned he got the same message when using "PROTON_USE_WINED3D=1", I get it without any launch options.

zaemiel commented 1 year ago

Is anyone on an AMD card and have it not working?

Yep, 5950X + 6950XT, hanging shortly after E for New Game. Same report as OP, tried on both 8.0.3 and experimental.

Same here, I can confirm on 7700X and 6700 XT on Linux Mint 21.2 with both the "stock" 5.15.0-82 kernel and the 6.2.0-31 kernel and Mesa 23.0.4 using Proton-Experimental. The game crashes about 10-20 seconds after "Start New Game" and kills my login session, leaving an amdgpu page fault in my kernel log.

The same for me. I'm on Mint 21.2 with AMD Ryzen 9 7900 and RX 6700

Mashaaaaaaaaaaa commented 1 year ago

I have an RTX 3070 MaxQ. With 535 drivers, the game doesn't launch. With 530 or 525, the game launches, and I can start a new game, but it has atrocious performance and half the assets don't load - humans are missing limbs, walls are missing, etc.

Iymarra commented 1 year ago

Manjaro/Nvidia 3080ti with 535 drivers, game launches and I can click new game, but game crashes seconds after.

solarisfire commented 1 year ago

Arch Linux, latest Kernel, 3090 with 535, game launches, click new game, crash during loading... :'(

urbenlegend commented 1 year ago

If I have VKD3D_CONFIG=dxr11 enabled in my environment variables, Starfield will crash during shader compilation. Removing it will allow Starfield to get to the main menu, but attempting to launch a new game will cause an Xid error:

Sep 01 02:42:58 arch-desktop kernel: NVRM: Xid (PCI:0000:0c:00): 109, pid=5974, name=Starfield.exe, Ch 000000ce, errorString CTX SWITCH TIMEOUT, Info 0x1c066

Seems like this long-standing bug that Nvidia hasn't fixed yet: https://forums.developer.nvidia.com/t/multiple-cuda-rtx-vulkan-application-crashing-with-xid-13-109-errors/235459/1

WarBaby2 commented 1 year ago

If I have VKD3D_CONFIG=dxr11 enabled in my environment variables, Starfield will crash during shader compilation. Removing it will allow Starfield to get to the main menu, but attempting to launch a new game will cause an Xid error:

Sep 01 02:42:58 arch-desktop kernel: NVRM: Xid (PCI:0000:0c:00): 109, pid=5974, name=Starfield.exe, Ch 000000ce, errorString CTX SWITCH TIMEOUT, Info 0x1c066

Seems like this long-standing bug that Nvidia hasn't fixed yet: https://forums.developer.nvidia.com/t/multiple-cuda-rtx-vulkan-application-crashing-with-xid-13-109-errors/235459/1

Great... I guess it's time to set up dualboot then.

ntropy83 commented 1 year ago

If I have VKD3D_CONFIG=dxr11 enabled in my environment variables, Starfield will crash during shader compilation. Removing it will allow Starfield to get to the main menu, but attempting to launch a new game will cause an Xid error:

Sep 01 02:42:58 arch-desktop kernel: NVRM: Xid (PCI:0000:0c:00): 109, pid=5974, name=Starfield.exe, Ch 000000ce, errorString CTX SWITCH TIMEOUT, Info 0x1c066

Seems like this long-standing bug that Nvidia hasn't fixed yet: https://forums.developer.nvidia.com/t/multiple-cuda-rtx-vulkan-application-crashing-with-xid-13-109-errors/235459/1

Tho from this thread the error seems to persist since 525 and Starfield does launch on 525 and 530, tho it does not run good then what again could be related to the error

Blisto91 commented 1 year ago

For info https://github.com/HansKristian-Work/vkd3d-proton/issues/1678#issuecomment-1702489043

WarBaby2 commented 1 year ago

For info HansKristian-Work/vkd3d-proton#1678 (comment)

As I said: Dualboot... NVIDIA will do sh*t about this, as usual.

stubkan commented 1 year ago

@WarBaby2 Your last 3 posts are just complaining and are not very productive. It means people who come here looking for solutions or the developers who need these threads to help them find solutions have to scroll through more to find useful information.

mc711 commented 1 year ago

if you are crashing after selecting new or continue at main menu try this command

Steam Launch options: VKD3D_CONFIG=force_compute_root_parameters_push_ubo %command%

Lutris Configure -> System Options -> Command Prefix VKD3D_CONFIG=force_compute_root_parameters_push_ubo

WarBaby2 commented 1 year ago

@WarBaby2 Your last 3 posts are just complaining and are not very productive. It means people who come here looking for solutions or the developers who need these threads to help them find solutions have to scroll through more to find useful information.

Why? It's a valid solution. ;) Ok, sorry, your are right... had a long night.

Tried in the meantime to start via Flatpack Steam - no dice - and disconnected periphery devices - no change either.

stubkan commented 1 year ago

Ubuntu with rtx 2060 and 535.104

Tried with VKD3D_CONFIG=force_compute_root_parameters_push_ubo %command% but still has the freeze issue after clicking start at menu, unfortunately

Iymarra commented 1 year ago

Ubuntu with rtx 2060 and 535.104

Tried with VKD3D_CONFIG=force_compute_root_parameters_push_ubo %command% but still has the freeze issue after clicking start at menu, unfortunately

Same here, attempted but display seized/crashed as previous.

HugKitten commented 1 year ago

if you are crashing after selecting new or continue at main menu try this command

Steam Launch options: VKD3D_CONFIG=force_compute_root_parameters_push_ubo %command%

Lutris Configure -> System Options -> Command Prefix VKD3D_CONFIG=force_compute_root_parameters_push_ubo

This did not fix things for me on steam flatpak with nvidia-open drivers.

WarBaby2 commented 1 year ago

Ubuntu with rtx 2060 and 535.104 Tried with VKD3D_CONFIG=force_compute_root_parameters_push_ubo %command% but still has the freeze issue after clicking start at menu, unfortunately

Same here, attempted but display seized/crashed as previous.

Same.

Arch, RTX 2070 super, same driver.

What Proton version?

mc711 commented 1 year ago

i tested on steam deck with lutris-GE-proton8-14.

i noticed

"VKD3D_CONFIG_FLAG_FORCE_COMPUTE_ROOT_PARAMETERS_PUSH_UBO is not enabled"

in my logs so i found solution here https://github.com/HansKristian-Work/vkd3d-proton/issues/1617

after, game rebuilds shaders and launched into game. sorry if it doesnt work for you guys :(

stubkan commented 1 year ago

@urbenlegend

NVRM: Xid

Are you sure? Why do you think it's that line causing it? My error logs show no mention of NVRM: Xid.

Also my logs don't have FORCE_COMPUTE_ROOT mentioned in them. They all (working and not working) do have this - info:vkd3d-proton:vkd3d_bindless_state_get_bindless_flags: Forcing push UBO path for compute root parameters. so it seems like its already enabled for both working/not working?

I do get the vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4. line, as referenced on https://github.com/HansKristian-Work/vkd3d-proton/issues/1678#issuecomment-1702489043

After examining my older logs from when I ran it with 525 and successfully running the game and on older 535 drivers that error does not come up at all.

Perhaps it would be useful to compare logs and find what errors are in all of them

Running with 535.86 - does not work - https://pastebin.com/raw/rRJJF4bn Running with 525 - does work - https://pastebin.com/raw/qssKgzKR Running with 535.104 - does not work - https://pastebin.com/bQZjzefN

I did crop some of the first two logs out, since pastebin didnt like the size of them, so other peoples logs would be good to have

Katherine1 commented 1 year ago

I can confirm that the 525 driver branch does work, though with a mid-20 FPS

Arch Linux 525.116.04 from the nvidia-525xx aur package

falsechicken commented 1 year ago

i tested on steam deck with lutris-GE-proton8-14.

i noticed

"VKD3D_CONFIG_FLAG_FORCE_COMPUTE_ROOT_PARAMETERS_PUSH_UBO is not enabled"

in my logs so i found solution here HansKristian-Work/vkd3d-proton#1617

after, game rebuilds shaders and launched into game. sorry if it doesnt work for you guys :(

Thank you! I was using the same version of lutris-GE-proton and it was crashing on my PC after selecting new game and this fixed that.

IceReaper commented 1 year ago

Sadly installing 525 from AUR wont work on manjaro out of the box. Installing the package results in some dependency issues with nvidia-525xx-dkms .

benbot commented 1 year ago

@falsechicken what hardware are you on?

WarBaby2 commented 1 year ago

Sadly installing 525 from AUR wont work on manjaro out of the box. Installing the package results in some dependency issues with nvidia-525xx-dkms .

You have to downgrade the kernel and the kernel headers too... the driver alone won't work.

IceReaper commented 1 year ago

Sadly installing 525 from AUR wont work on manjaro out of the box. Installing the package results in some dependency issues with nvidia-525xx-dkms .

You have to downgrade the kernel and the kernel headers too... the driver alone won't work.

Im running a 6.1 kernel, which is marked as lts and recommended by manjaro. Also the nvidia package explicitely asks me which kernel i am running. After selecting the 6.1 kernel, it ends up with the dependency problem. As i can explicitely select 6.1 i was assuming it should work.

joeydesimone commented 1 year ago

OS: Arch Linux KERNEL: 6.4.12-arch1-1 CPU: Intel Core i9-10900K @ 3.70GHz GPU: NVIDIA GeForce RTX 3080 GPU DRIVER: NVIDIA 535.104.05 RAM: 32 GB

Note: Removed most of the repeating 1864.880:0130:01e8:warn:vkd3d-proton:d3d12_device_QueryInterface: {0742a90b-c387-483f-b946-30a7e4e61458} not implemented, returning E_NOINTERFACE. lines because it made the log too big for pastebin.

Running with 535.104 (both 8.0.3/Experimental) - crashes after selecting 'New game' - https://pastebin.com/CZk8Cb52

WarBaby2 commented 1 year ago

Sadly installing 525 from AUR wont work on manjaro out of the box. Installing the package results in some dependency issues with nvidia-525xx-dkms .

You have to downgrade the kernel and the kernel headers too... the driver alone won't work.

Im running a 6.1 kernel, which is marked as lts and recommended by manjaro. Also the nvidia package explicitely asks me which kernel i am running. After selecting the 6.1 kernel, it ends up with the dependency problem. As i can explicitely select 6.1 i was assuming it should work.

Ok, I'm not that familiar with Manjaro... afaik it uses some specially curated packages in places that might not work with AUR stuff?

Personally, I stay away from downgrading on mainline Arch, since it can break a whole host of other things if the kernel gets too "old"...

EDIT: But,. if you are using the lts kernel, did you also try using the NVIDIA-LTS drivers, not the dkms packages?

falsechicken commented 1 year ago

@falsechicken what hardware are you on?

RX 570, Ryzen 5 2600, Garuda Linux. There is still graphical issues. Some characters only have eyeballs rendered lol. But it starts now.

ntropy83 commented 1 year ago

Sadly installing 525 from AUR wont work on manjaro out of the box. Installing the package results in some dependency issues with nvidia-525xx-dkms .

You have to downgrade the kernel and the kernel headers too... the driver alone won't work.

Im running a 6.1 kernel, which is marked as lts and recommended by manjaro. Also the nvidia package explicitely asks me which kernel i am running. After selecting the 6.1 kernel, it ends up with the dependency problem. As i can explicitely select 6.1 i was assuming it should work.

Manjaro has the tool mhwd to manage nvidia drivers, you should look that up and use that.

jcgit1 commented 1 year ago

I can't get past the copyright/Bethesda logo. Crashing to desktop here - Ubuntu 23.04, Ryzen 5800x3d, 7900XTX. 

2091.573:012c:0274:err:seh:call_stack_handlers invalid frame 000000013F86E440 (000000013F672000-000000013F770000)
2091.573:012c:0274:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception.
wine client error:274: Assertion failed: !succ->pred_back_edge || succ->pred_back_edge == &entry, file ../src-vkd3d-proton/subprojects/dxil-spirv/cfg_structurizer.cpp, line 2058

Assertion failed: !succ->pred_back_edge || succ->pred_back_edge == &entry, file ../src-vkd3d-proton/subprojects/dxil-spirv/cfg_structurizer.cpp, line 2058

write: Bad file descriptor
2091.620:00e0:02bc:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
2091.639:0030:02c0:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
2091.639:0030:02c4:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
2091.639:0030:02c8:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
2091.640:0030:02cc:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
2091.640:0030:02d0:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
pid 19401 != 19400, skipping destruction (fork without exec?)

steam-1716740.log

Katherine1 commented 1 year ago

Personally, I stay away from downgrading on mainline Arch, since it can break a whole host of other things if the kernel gets too "old"...

Personally, I'm not too worried at the moment. 525 isn't old enough for me to require an older kernel than the one currently on Arch, and this is a temporary measure. I'll just have to be careful about updates until then.

HansKristian-Work commented 1 year ago

2087.373:012c:0130:info:vkd3d-proton:vkd3d_config_flags_init_once: VKD3D_CONFIG='dxr11,dxr'.

It's probably the DXR shaders causing issue here. I haven't seen those without it. A bit confusing though, does the game even have ray tracing?

djdairy commented 1 year ago

A bit confusing though, does the game even have ray tracing?

The game does not feature ray tracing, no.

benbot commented 1 year ago

@Katherine1 what kind of fps are you getting. I get <20 on 525 even with a 4090

Katherine1 commented 1 year ago

I'm on a mobile 3080ti and I'm getting between 20-30fps on ultra settings with fsr2 enabled.

It's not great, but it's playable.

EDIT: From what I understand, the poor performance is due to a compute bug with nvidia drivers, so it's CPU-bound. What's your CPU? Mine's an Intel i9-12900H

kisak-valve commented 1 year ago

For visibility,

@HansKristian-Work posted at https://github.com/HansKristian-Work/vkd3d-proton/issues/1678#issuecomment-1702489043:

NV 535 stable is clearly bugged here. 525.47.35 at least seems to work though ...

Performance on NV currently is known to be extremely poor due to being completely CPU bound. This is caused by lack of us enabling NV_device_generated_compute on NV due to a driver bug. #1639 for details. When the beta driver updates, it should start running much better.

On Mesa desktop, please ensure that:

I tried to look around a bit at the Ubuntu stock kernels, and it appears that none of that distro's stock kernels include https://lists.freedesktop.org/archives/amd-gfx/2023-June/094648.html which was noted in https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24774 and should be the mentioned kernel regression. That would be something for an Ubuntu kernel package maintainer to either rebase their kernel on a newer patch release or backport the kernel fix.