Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grand Theft Auto IV (12210) #350

Open
zetok opened this issue Aug 24, 2018 · 159 comments
Open

Grand Theft Auto IV (12210) #350

zetok opened this issue Aug 24, 2018 · 159 comments
Labels
Game compatibility - Unofficial Games not expected to work without issues Mesa drivers Possibly involves an issue with a Mesa video driver Regression Confirmed working on an older version of Proton

Comments

@zetok
Copy link

zetok commented Aug 24, 2018

gtaiv-crash.log
steam-system-info.txt

Distro: Gentoo Linux

@mirh
Copy link

mirh commented Aug 24, 2018

Seems similar to this, which in turn might be due GFWL.
A workaround for the moment is XLiveLess.

@kisak-valve kisak-valve added the Game compatibility - Unofficial Games not expected to work without issues label Aug 24, 2018
@vanyasem
Copy link

The game refuses to launch for me giving me a black screen. XLiveLess is installed

@Houtworm
Copy link

The installation goes fine, then it asks me about a Xbox account, I just hit play and then i get this error

schermafdruk van 2018-08-25 15-12-20

@vanyasem
Copy link

vanyasem commented Aug 26, 2018

@Houtworm, please read the comment above about XLiveLess. GFWL doesn't work on wine and probably never will.

@mirh
Copy link

mirh commented Aug 26, 2018

Source?
AFAIK the current blockers are only LiveID service not initializing (which could have benefited a lot of the last work on msi installers) and WPF (which should have some very dirty workaround, at least).

@ardje
Copy link

ardje commented Aug 27, 2018

I did get GTA IV to work using playonlinux. xliveless should be used as always.
It was rather straight forward until I started to apply patches needing to get any controller to work. Then it stopped working :-(.
Anyway: GTA IV should work more or less out of the box by installing the xlive.dll using the steam recipe on PoL (not the GTA IV recipe, as that is outdated).

I hope Proton will have an xliveless option in the future.

Anyway my problem is almost the same as I started with EFLC. EFLC should display a menu to select which of the two stories you want to play before starting the game itself. That menu is black.

@vanyasem
Copy link

What's your GPU / OS? @ardje

@ardje
Copy link

ardje commented Aug 28, 2018

@vanyasem : GTA IV EFLC is working for me now (tm) on a GPD WIN 2 using padoka PPA. It only starts from the desktop client though, starting it from big picture gives me black screen. And I need big picture to translate the controller to something sane :-(. I need some more testing though.
This is using the 3.7.4-beta proton if I recall correctly... I will play with it some more tonight.
Note that being able to run it on the WIN 2 is an achievement as a lot of (linux) games ignore the rotated status of the screen and assume the 720x1280 rotated means 720 horizontal and 1280 vertical.
I also will test GTA IV EFLC on my steam machine by starting another wm in the .xsession and use the desktop client.

@vanyasem
Copy link

vanyasem commented Aug 29, 2018

@mirh Source: winehq. Note on the bottom of the page.

Games for Windows - LIVE does not work under Wine. GFWL components will crash any game that use the service. The only thing to do about it is to cut XLive out using XLiveLess Patch.

I probably won't find a comment by one of Wine maintainers about GFWL support, but considering it has been a lot of time since that note was initially created, you probably get the idea.

@ardje
Copy link

ardje commented Aug 29, 2018

Oh, wait, I am not using padoka, but oibaf, and that's a guy/repo who packages upstream mesa for stable ubuntu releases on a daily basis.
GTA EFLC seems to just take ages to get to the selection screen I've now seen. I should time it, it looks like 5...10 minutes in big picture mode.
The GPD WIN 2 is based on an intel SoC with a 720x1280 portrait display rotated landscape. It has no rotated scanout features, so all rotation is done in software. The specs: intel M3, intel HD 615, 8GB memory, xbox like gamepad.

On my steammachine with steamos beta, I just reboot it, because it never finishes installing. I think I should install it using desktop mode and see what happens. The steam machine is an i5 with a GTX960M with 3GB VRAM.
On the WIN2 I have major problems using the controller pad, but that might be due to not compiling the kernel correctly. It's not related to GTA at least.
About GFWL, I never knew anything other than to install xlive.dll to get rid of it.
I think installing social club from the GTA site should fix most of these.
But I don't know how proton integrates. Personally I would just use some base image and use a unionfs like fs layer on that. Or each game should have it's separate fixed up environment (like playonlinux).

@ardje
Copy link

ardje commented Aug 29, 2018

About GFLW: a lot of howtos for windows is about how to disable GFLW. It's not just a problem for people using wine, it's a generic problem.

@ardje
Copy link

ardje commented Aug 29, 2018

About the very long wait: I found this: https://www.reddit.com/r/GTA/comments/8ff35v/gta_iv_game_stays_on_a_black_screen_for_about_a/

It seems that it looks really like GTA IV EFLC is working properly.

@zetok
Copy link
Author

zetok commented Aug 29, 2018

Game keeps crashing during the benchmark (Options→Graphics→Benchmark).
gtaiv-benchmark-crash.log

@vanyasem
Copy link

vanyasem commented Aug 29, 2018

I tried waiting for 11 minutes with no success. I am using the -windowed option. Could you please upload a screenshot?

Also there is a new folder in GTA IV directory called steam_shader_cache, which seems related to the fact that I have pre-compiled shaders on in Steam settings. Do you have that enabled?

@mirh
Copy link

mirh commented Aug 29, 2018

I probably won't find a comment by one of Wine maintainers about GFWL support, but considering it has been a lot of time since that note was initially created, you probably get the idea.

Means [less than! random guy ≠ wine] nothing.
It's just microsoft gaming dep had a sort of reverse-NIMBY crisis and decided to implement everything they could via this or that windows service (which just about nobody would or does use).
And people seem so much like not even caring that in 3 years nobody noticed bugs getting fixed either.

I just cannot understand for the love of me, what people think wine objective would even be.

About GFLW: a lot of howtos for windows is about how to disable GFLW. It's not just a problem for people using wine, it's a generic problem.

That's because games come bundled with outdated runtimes, which cannot even get to the stage of updating without misbehaving on newer windows. But in my experience this can solve *all* problems.

p.s. I'm impressed that M3-7Y30 (corresponding broadly to a QX9300 plus HD4670) can bring "gta 4 working faster than a slideshow" territory on that tdp

@zetok
Copy link
Author

zetok commented Aug 29, 2018

@vanyasem
Before launching the game (in -windowed mode), I did 2 things:

# process doesn't seem to be useful? game ~works anyway
while :; do pkill -9 'gta4Browser.exe' ; sleep 2; done

# speeds up game startup (almost instant), drops all the outgoing connections
iptables -A OUTPUT -o eth0 ! -d 127.1 -j DROP

Framerate is horrible though, and there's a graphical glitch next to minimap:

screenshot

@vanyasem
Copy link

Do you all have AMD GPUs or has someone succeeded in launching the game on an nvidia GPU? I feel like nvapi issue might be related here. Though it doesn't work for me even on latest wine staging, so unlikely, still worth noting.

The game is constantly eating one core of my CPU, staying at the black screen. I disabled intro videos just in case, but that didn't help.

@DissCent
Copy link

I have the same problem as @vanyasem - xliveless is installed (used this before, so I know how to do it), but no matter what I do (killing gta4browser.exe, setting specific options), the screen just stays black (and one of my CPU cores goes to 100% usage).
This is on Arch Linux with NVIDIA 396.54

@Mattia98
Copy link

Mattia98 commented Sep 2, 2018

Me too. Have the same problem as @vanyasem and @DissCent
NVIDIA 396.54 drivers on GTX 1050m XUbuntu 18.04
@zetok's workaround does not work for me.

@ardje
Copy link

ardje commented Sep 4, 2018 via email

@Gravarty
Copy link

Gravarty commented Sep 4, 2018

okay i'm new to this steam proton thing, where do i have to put those wine fixes to block the gta4browser.exe? I tried to put it inside the user_settings.py but that just breaks all games.

@lazanet
Copy link

lazanet commented Sep 5, 2018

I managed to get the game working fine by copying xliveless (from lutris repo) to the game folder, and then blocking tv.rockstargames.com (because that subdomain has misconfigured ip address at the moment, and game is stuck at disclaimer screen trying to connect to it) by applying following command:
sudo sh -c "echo '127.0.0.1 tv.rockstargames.com' >> /etc/hosts"

Nasty workaround (because of Rockstar's negligence towards GTAIV PC port), but it works.

@Mattia98
Copy link

Mattia98 commented Sep 6, 2018

What you suggest, @lazanet , seems to be for a separate issue. The first workaround is obvious and is for skipping GFWL. The second is for skipping activation and getting stuck at the disclaimer screen. The problem is that some of us are not even getting to the disclaimer screen. Can you please share your specs so that we can rule out some stuff? Tnx :-*

@instabilis
Copy link

@Mattia98 I've managed to get EFLC running on nvidia by copying nvapi files from my system installation of wine (wine 3.14) to the corresponding directories in the Proton (Proton Beta 3.7-5) installation.

cp /usr/lib64/wine/nvapi64.dll.so ~/.local/share/Steam/steamapps/common/Proton\ 3.7\ Beta/dist/lib64/wine/nvapi64.dll.so
cp /usr/lib64/wine/fakedlls/nvapi64.dll ~/.local/share/Steam/steamapps/common/Proton\ 3.7\ Beta/dist/lib64/wine/fakedlls/nvapi64.dll
cp /usr/lib/wine/nvapi.dll.so  ~/.local/share/Steam/steamapps/common/Proton\ 3.7\ Beta/dist/lib/wine/nvapi.dll.so
cp /usr/lib/wine/fakedlls/nvapi.dll ~/.local/share/Steam/steamapps/common/Proton\ 3.7\ Beta/dist/lib/wine/fakedlls/nvapi.dll

@vanyasem
Copy link

vanyasem commented Sep 7, 2018

For Arch the paths to wine libs differ:

cp -v /usr/lib64/wine/nvapi64.dll.so ~/.local/share/Steam/steamapps/common/Proton\ 3.7\ Beta/dist/lib64/wine/nvapi64.dll.so
cp -v /usr/lib64/wine/fakedlls/nvapi64.dll ~/.local/share/Steam/steamapps/common/Proton\ 3.7\ Beta/dist/lib64/wine/fakedlls/nvapi64.dll
cp -v /usr/lib32/wine/nvapi.dll.so  ~/.local/share/Steam/steamapps/common/Proton\ 3.7\ Beta/dist/lib/wine/nvapi.dll.so
cp -v /usr/lib32/wine/fakedlls/nvapi.dll ~/.local/share/Steam/steamapps/common/Proton\ 3.7\ Beta/dist/lib/wine/fakedlls/nvapi.dll

@vanyasem
Copy link

vanyasem commented Sep 7, 2018

Related to #165

@vanyasem
Copy link

vanyasem commented Sep 7, 2018

Can confirm, that fixes both GTA IV, and GTA EFLC for me
2018-09-07-231824_3840x2067_scrot

The game performs very poorly though, I get around ~19 FPS in 4k maxed out. Specs: https://gist.github.com/vanyasem/f787469ec8c50cdd3728340ef4c73269

@vanyasem
Copy link

vanyasem commented Sep 7, 2018

I only saw some occasional graphics glitches, and shuttering during cutscenes (vsync off). The game runs pretty well by itself.
2018-09-07-234309_384x349_scrot

@kisak-valve
Copy link
Member

GTA 4 refuses to work

Issue transferred from #6098.
@sprmcell posted on 2022-08-17T09:39:01:

Compatibility Report

  • Name:
    Grand Theft Auto IV
  • Steam AppID of the game:
    12210

System Information

CPU: Ryzen 3 3100
GPU: NVIDIA GT610 2048MB
RAM: 16GB
Kernel: Zen Kernel 5.17.5
Proton: All version tried

I confirm:

  • [*] that I haven't found an existing compatibility report for this game.
  • [*] that I have checked whether there are updates for my system available.

Log

Steam Log

Symptoms

Game used to launch to a black screen with no audio
as shown here

Now its refuses to launch
as shown here

Troubleshooting steps

  • Yes i did reinstall
  • Yes i did change proton versions
  • Yes my drivers are up to date
  • Yes i changed launch options

@kisak-valve
Copy link
Member

Hello @sprmcell, looking at your hardware, the NVIDIA GT 610 is part of the Fermi generation of NVIDIA video cards. The video drivers for this card generation never exposed support for Vulkan, and the NVIDIA 390 series driver is older than the support cutoff for Proton. Sorry, but both of those details makes your system is unsupported by Proton in general for all games.

@mirh
Copy link

mirh commented Aug 17, 2022

If only #1749 had been merged...

@kisak-valve
Copy link
Member

GTA IV: Colour flickering on Proton Experimental

Issue transferred from #6265.
@lukelmy posted on 2022-10-24T08:29:30:

Compatibility Report

  • Name of the game with compatibility issues: Grand Theft Auto IV: The Complete Edition
  • Steam AppID of the game: 12210

System Information

  • GPU: AMD 6900 XT
  • Driver/LLVM version: AMDGPU stack 22.20
  • Kernel version: 5.15.0
  • Proton version: Proton Experimental

I confirm:

  • that I haven't found an existing compatibility report for this game.
  • that I have checked whether there are updates for my system available.

Symptoms

When starting game with Proton Experimental, colour flickering can be observed. However, images are normal when using Proton 7.0-4. The problematic shader module is found with Renderdoc. If NAN judgement is added before extended instruction NMin(or NClamp) instead of only NMin(or NClamp) in the spirv-dis of problematic shader module, the image is normal. Guessing it's a SPIR-V generated issue.

colour_flickering

The original spirv-dis and the modified spirv-dis of the problematic shader module on Proton Experimental are listed as follows:
spv_pass.txt
spv_fail.txt

Reproduction

  • Start a new game

@mbriar commented on 2022-10-24T12:47:10:

This is expected if you use the proprietary vulkan driver, which does not support VK_EXT_attachment_feedback_loop_layout (yet?). It shouldn't happen with RADV, which is also the recommended driver for proton in general.

@lukelmy
Copy link

lukelmy commented Nov 2, 2022

I tried to build 32bits RADV(22.3.0-devel), and I found that colour flickering still existed on Proton 7.0 and images were normal on Proton Experimental. Is this normal?

@Blisto91
Copy link

Blisto91 commented Nov 3, 2022

Yes. The vulkan extension that helps with the issue isn't enabled in the dxvk 1.10.x branch, which is what proton 7.0 is using. But it is on master, which is what experimental is using.

@paperlyly
Copy link

I have the same rendering problem, showing a colored diagonal line, what should I do to fix it?
i use proton-ge and i'm on intel

@Blisto91
Copy link

Blisto91 commented Apr 4, 2023

I'm thinking it will be resolved on Intel ANV once this MR has been merged and is available https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17892

@Midou36O
Copy link

Midou36O commented Apr 4, 2023

I have the same rendering problem, showing a colored diagonal line, what should I do to fix it? i use proton-ge and i'm on intel

I fixed this last year by using these env vars in the steam launch options

INTEL_DEBUG=norbc,nohiz %command%

@paperlyly
Copy link

paperlyly commented Apr 4, 2023

Replying to #350 (comment)

gets stuck on black screen, Do you think I can fix it somehow?

@Blisto91
Copy link

Blisto91 commented Apr 5, 2023

If the environment variables give a black screen don't use them.
I do not have a Intel GPU atm to test this personally sadly.

@Midou36O
Copy link

Midou36O commented Apr 5, 2023

With the env var:
image
Without the env var:
image

@paperlyly I'm not sure what could cause the black screen, but i'd probably check the proton logs for the game ( PROTON_LOG=1 %command%) to see if there isn't some error in there. The log should be in your home folder.

(PS: One thing i noticed is that you no longer get those artifact at the expense of some FPS boost, i had 60fps without the fix and now get 45fps with the fix.)

@Blisto91
Copy link

Blisto91 commented Apr 5, 2023

If you want and there isn't already a issue it would be nice to make one at the mesa repo.

@paperlyly
Copy link

paperlyly commented Jul 10, 2023

@Midou36O I already got it to work, I was not using it as an env var, it works although with worse performance, and quite a bit of instability, sometimes the game does not run and it stays loading forever, sometimes it does but it closes

I'm using wined3d, because with vulkan I can't get it to work without those lines in a stable way

Does anyone know if updating the table to 23 resolves it?
I'm on debian 12, where table 22 is still used, but I don't know if it's worth looking for some way to update, what's more, I don't even know how to use table 23 in debian

@a99984b1799
Copy link

a99984b1799 commented Aug 19, 2023

I'm on NixOS 23.11 kernel 6.4.8, 5900x, RTX 3070 535.86.05. I've tried Proton Experimental and 8.0-3.

The game gets to various stages of launching, but never runs. It sometimes gets stuck on

Running install script (Microsoft DirectX)

or

Running install script ()

And ps will show this:

Z:\home\i\.local\share\Steam\steamapps\common\Steamworks Shared\_CommonRedist\DirectX\Jun2010\DXSETUP.exe /silent

Killing this process results in Social Club opening immediately, which itself gets stuck on

Installing prerequisite: Rockstar Games Social Club...

The status bar moves to the right and then never progresses. Around this time it also launches RockstarErrorHandler.exe, though nothing appears on screen:

C:\Program Files\Rockstar Games\Launcher\ThirdParty//Crashpad//RockstarErrorHandler.exe --no-rate-limit --attachment=attachment_launcher.log=C:\users\steamuser\AppData\Local\Rockstar Games\Launcher\CrashLogs\launcher.log --database=C:\users\steamuser\AppData\Local\Rockstar Games\Launcher\CrashLogs\ --metrics-dir=C:\users\steamuser\AppData\Local\Rockstar Games\Launcher\CrashLogs\ --url=https://submit.backtrace.io/bob/[redacted]/minidump --annotation=format=minidump --annotation=token=[redacted] --initial-client-data=[redacted]

Attached is the logs of attempting to run the game with Proton Experimental. The logs are trimmed, it originally contained many thousands more lines of 124251.070:013c:0140:fixme:d2d:d2d_geometry_sink_AddArc iface 000000000D756918, arc 000000000012E870 stub! interspersed with the uiautomation logs seen at the bottom.

steam-12210.log

@a99984b1799
Copy link

a99984b1799 commented Aug 19, 2023

There's some degree of regression between Proton 7 and Proton 8 here. Running Proton 7.0-6 gets through the RGSC installer fine, then fails here:

Screenshot_20230819_135233

Edit: If you leave RGSC to try and install prerequisites in Proton 8+, it will eventually timeout and offer to continue without installing anything. Doing so brings me to the login page, where entering my credentials results in further infinite loading.

Screenshot_20230819_140619

@a99984b1799
Copy link

The game is working perfectly for me now on Proton 8. It appears the big pain point is RGSC.

@tati-frog
Copy link

There is a bug in the independent radio (the radio for playing your own mp3 files) where it will not play anything. If you add audio files into C:/users/steamuser/Documents/Rockstar Games/GTA IV/User Music and then click in Settings->Audio->Complete Scan it will do a scan and detect the files but the independent radio will play a radio announcer, also if you click on Complete Scan many times and fast gstreamer will create a lot of threads and get to a resources no available error and the game will just freeze.

I didn't dig too much into it, but I found that wmvcore might be related.

@NikoBellicRU
Copy link

The game opens and it's "playable" but theres a jitter / stutter that happens about every second and it doesn't show in the graph, only way i found to almost fix was disabling core 3 or 4 in powertools, setting the min cpu frequency to the mas 3500mhz also seemed to help.

Using the steam deck stable / preview and proton 8 /experimental ( 7 wont even pass the rockstar launcher)

@ClaudeLib
Copy link

The game runs without issues for me and performs rather well, but opening the RGL overlay by pressing Home reveals that it thinks that it's on an end-of-life operating system and may stop running on Jan 30th, 2024. The OS is Arch-based ChimeraOS, Proton version is 8.0-4.
20231217155717_1
steam-12210.log

@kisak-valve
Copy link
Member

Hello @ClaudeLib, #37 (comment) notes that message shows unconditionally regardless of OS.

@ClaudeLib
Copy link

Whoops, my bad. Thank you.

@PeterKriegtNenWolf
Copy link

For me, there seems to be a problem with DLLs not loading.
When launching through Steam, the Rockstargames-launcher opens two loading windows of Rockstargames-Launcher. After the second one closes nothing happens really; the game doesn't launch. In steam the "Play"-button is available after a few seconds.

The logs of R*G-Launcher show, that it exited with Code 0xc0000135 (3221225781).

[2024-01-30 22:47:08.837] [DISPLAY] [ 1276] [gamelaunch] Game exited with code 0xc0000135 (3221225781)
[2024-01-30 22:47:08.838] [DISPLAY] [ 1276] [crashdetection] Game left no exit file.
[2024-01-30 22:47:08.838] [ ERROR ] [ 1276] [crashdetection] Exit code 0xc0000135 indicates a fatal game exit (reason: STATUS_DLL_NOT_FOUND)

Looking for related entries in the Proton-logs it indicates to file WMASF.DLL not being loaded:

1557.281:04fc:0500:err:module:import_dll Library WMASF.DLL (which is needed by L"C:\windows\system32\WMVCore.DLL") not found
(...)
1557.282:04fc:0500:err:module:import_dll Library WMVCore.DLL (which is needed by L"Z:\home\myuser\.local\share\Steam\steamapps\common\Grand Theft Auto IV\GTAIV\GTAIV.exe") not found
(...)
1557.288:04fc:0500:err:module:LdrInitializeThunk Importing dlls for L"Z:\home\myuser\.local\share\Steam\steamapps\common\Grand Theft Auto IV\GTAIV\GTAIV.exe" failed, status c0000135

There are several dlls with that name in the compatdata-folder for that game - upper- and lowercase are different between them but none was all uppercase.

/home/myuser/.local/share/Steam/steamapps/compatdata/12210/pfx/drive_c/windows/syswow64/WMASF.dll
/home/myuser/.local/share/Steam/steamapps/compatdata/12210/pfx/drive_c/windows/syswow64/wmasf.dll

After renaming one of them to the correct case from the logs (WMASF.DLL), the game launched normal as expected.

This occurred on several versions of proton (Proton 8.0-5, experimental, GE-Proton8-27).
Hope this helps / makes it easier to find a proper solution.

@rdlf4
Copy link

rdlf4 commented Feb 8, 2024

Reinstalled the game for another playthrough, but I can no longer even get to the episode selection screen.
The Rockstar launcher has been updated and now to get to launching the game, I need to go through this login screen, which makes my right trackpad non-responsive; Also, I cannot summon the keyboard with STEAM+X. Screenshot_20240207_180540

In other words, as long as one doesn't have a physical keyboard to use with their Steam Deck, which is my case, I cannot fill out those text boxes, thus I can't launch the game. Way to go Rockstar.

@shubhisroking
Copy link

image
anyone else having this issue?
proton 8 btw

@rdlf4
Copy link

rdlf4 commented Mar 31, 2024

image anyone else having this issue? proton 8 btw

Have Steam check the game files. That happened to me as well, and it turned out to be Rockstar's stupid launcher, which needed an update. After that has been taken care of, you'll need a physical keyboard (or a virtual one that isn't from Valve) to be able to input text, and fill out your email address and password -- yes, they'll ask for it again. I find it amazing, not to say infuriating that Valve still lets publishers get away with their bloated launcher and all the crap they can throw our way just because we paid for a copy of their game and want to play it. I should have cracked the f---ing launcher and spare myself the trouble, Rockstar is that full of sh-t.

@JustCauseWhyNot
Copy link

JustCauseWhyNot commented Jul 1, 2024

Its failing to launch for me. Here's my steam-12210.log. I launch the launcher and after that it just never shows a window.

@JustCauseWhyNot
Copy link

To add I've ran a version of gta4 that didn't require launching the r* launcher. That copy of gta4 works for me when ran with UMU-Proton-9.0-2.

@LemonHeadOnGit
Copy link

Replying to #350 (Comment)

wmvcore has something to do with Independence FM skipping songs after around 30s. When the song gets loaded into memory and/or parsed for metadata/info, this fixme is printed:

36873.873:05b8:06dc:fixme:wmvcore:header_info_GetAttributeIndices iface 03226948, stream_number 0, name L"Duration", lang_index 00000000, indices 00000000, count 377EFD7C, stub!
36873.873:05b8:06dc:fixme:wmvcore:header_info_GetAttributeIndices iface 03226948, stream_number 0, name L"Duration", lang_index 00000000, indices 11EE6630, count 377EFD7C, stub!
36873.873:05b8:06dc:fixme:wmvcore:header_info_GetAttributeByIndexEx iface 03226948, stream_number 0, index 52685, name 00000000, name_len 377EFD7C, type 377EFD6C, lang_index 00000000, value 377EFD70, size 377EFD68, stub!

Using GE-Proton fixes this somewhat, however a new issue is introduced where the song can get sped up (or sometimes jump further ahead than it should) if you switch between stations.

On a side note, it is impossible to "render" (or rather export) a gameplay clip from the in-game editor. This appears in the logs as soon as the export freezes, leading to a quiet exit back to the clip timeline:

39353.484:0a9c:0aa0:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\mlang.dll" : builtin
39353.484:0a9c:0aa0:trace:loaddll:free_modref Unloaded module L"C:\\windows\\syswow64\\WMVSENCD.dll" : native
39353.484:0a9c:0aa0:trace:loaddll:free_modref Unloaded module L"C:\\windows\\syswow64\\WMVXENCD.dll" : native
39353.484:0a9c:0aa0:trace:loaddll:free_modref Unloaded module L"C:\\windows\\syswow64\\WMVENCOD.dll" : native
39353.484:0a9c:0aa0:trace:loaddll:free_modref Unloaded module L"C:\\windows\\syswow64\\wmspdmoe.dll" : native
39353.485:0a9c:0aa0:trace:loaddll:free_modref Unloaded module L"C:\\windows\\syswow64\\wmadmoe.dll" : native

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Game compatibility - Unofficial Games not expected to work without issues Mesa drivers Possibly involves an issue with a Mesa video driver Regression Confirmed working on an older version of Proton
Projects
None yet
Development

No branches or pull requests