GTA: San Andreas (12120)

[Veske]

Tested with on Arch Linux with mesa 18.1.6-1

Launches without any errors or complications. Just works.

System Information

  PROCESSOR:          Intel Core i5-4570 @ 3.60GHz
    Core Count:       4
    Extensions:       SSE 4.2 + AVX2 + AVX + RDRAND + FSGSBASE
    Cache Size:       6144 KB
    Microcode:        0x25
    Scaling Driver:   intel_pstate powersave

  GRAPHICS:           MSI AMD Radeon RX 470/480/570/570X/580/580X 8192MB
    Display Driver:   modesetting 1.19.1
    Monitor:          BenQ xl2411t
    Screen:           1920x1080

  MOTHERBOARD:        ASUS B85-PLUS
    Memory:           16384MB
    Chipset:          Intel 4th Gen Core DRAM
    Network:          Realtek RTL8111/8168/8411

  DISK:               128GB Samsung SSD 840 + 1000GB Seagate ST1000DM010-2DM1 + 1000GB Seagate ST1000DM003-1CH1
    File-System:      btrfs
    Mount Options:    relatime rw space_cache ssd subvol=/ subvolid=5
    Disk Scheduler:   CFQ

  OPERATING SYSTEM:   Arch rolling
    Kernel:           4.18.3-arch1-1-ARCH (x86_64)
    Desktop:          GNOME Shell 3.28.3
    Compiler:         GCC 8.2.0

[PopeFelix]

I don't have Vulkan installed; I'll install it try again on both boxen. As for Mesa, is there a reason I should choose kisak over OIBAF or the converse?

On Thu, Apr 30, 2020 at 11:30 AM kisak-valve notifications@github.com wrote:

Hello @PopeFelix https://github.com/PopeFelix, Intel's Ivybridge chipset has experimental support for Vulkan, which might run, but you will most likely encounter driver bugs. Please verify you have vulkan drivers installed for your video chipset with something like apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386 and install them if they are not already. Also, you may benefit from using a newer build of mesa from a PPA like oibaf https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers or kisak-mesa https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa.

Alternatively, you can tell Proton to use wine's DirectX to OpenGL render path by adding PROTON_USE_WINED3D=1 %command%, but this is expected to come with a significant performance penalty and is not considered supported.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/143#issuecomment-621962454, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABGUGCQKEIQBDYNGIBDYCTRPGRQTANCNFSM4FRBCL7A .

-- Kit Peters, W0KEH GPG public key fingerpint: D4FF AA62 AFEA 83D6 CC98 ACE5 6FAE 7E74 7F56 ED1D Hello to any and all NSA, DEA, or other government or non-government agents reading this email. Tell me about your life; I'll tell you about mine.

[kisak-valve]

The Oibaf PPA provides bleeding edge builds of mesa, while kisak-mesa PPA has point releases.

[PopeFelix]

Installed Vulkan, installed OIBAF. No dice. Latest log attached.

steam-12120.log

[kisak-valve]

The log has the same indication as before, that Vulkan failed to initialize. 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.

[PopeFelix]

https://gist.github.com/PopeFelix/efa5727b0f0ed3a1633f35aaaf13ec21

[kisak-valve]

Thanks, can you check if LIBGL_DEBUG=verbose glxinfo | grep DRI3 outputs a line with libGL: Using DRI3 for screen 0? I suspect that X is using DRI2 with nouveau and the Intel ANV vulkan driver requires DRI3 to render.

[PopeFelix]

Looks like I'm using DRI3.

took@oscar:~$ LIBGL_DEBUG=verbose glxinfo | grep DRI3 
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/took/.drirc: No such file or directory.
libGL: using driver nouveau for 4
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/took/.drirc: No such file or directory.
libGL: pci id for fd 4: 10de:1040, driver nouveau
libGL: MESA-LOADER: dlopen(/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so)
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/took/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/took/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/took/.drirc: No such file or directory.
libGL: Using DRI3 for screen 0

[PopeFelix]

Oh, that was on my desktop that has the Haswell processor and nvidia graphics . I haven't tried the laptop (Ivybridge processor / Intel graphics) yet; I'll report back when I do.

On Thu, Apr 30, 2020 at 7:43 PM kisak-valve notifications@github.com wrote:

Thanks, can you check if LIBGL_DEBUG=verbose glxinfo | grep DRI3 outputs a line with libGL: Using DRI3 for screen 0? I suspect that X is using DRI2 with nouveau and the Intel ANV vulkan driver requires DRI3 to render.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/143#issuecomment-622193493, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABGUGCUP6NDY7Y45YI5CF3RPILJPANCNFSM4FRBCL7A .

-- Kit Peters, W0KEH GPG public key fingerpint: D4FF AA62 AFEA 83D6 CC98 ACE5 6FAE 7E74 7F56 ED1D Hello to any and all NSA, DEA, or other government or non-government agents reading this email. Tell me about your life; I'll tell you about mine.

[kisak-valve]

I think we've made a reasonable attempt to troubleshoot this riddle before reaching out for more help. The last guess I'm going to throw out there is that you might get lucky trying xf86-video-modesetting instead of xf86-video-nouveau, but I don't know if that'll have any effect or cause other troubles.

Can you reach out to the nouveau / ANV devs and see if there's a known issue going on here? (https://www.mesa3d.org/bugs.html)

[doublez13]

Much more stable on Proton 5.13. Tested Xbox One and PS4 controllers as well

[blackdevil72]

Hello, I have some problems with this game. Out of the box it gets installed, start and begin a new game flawlessly.

Unfortunately problems arise during the game. I get huge FPS drops from 60 FPS (or more with no frame limiter) down to 3 to 10 FPS. Same result with Proton Experimental, 5.13-4, 5.9-GE-8-ST.

Thinking it was a bugged game related problem I tried to mod/patch the game following this guide : https://steamcommunity.com/sharedfiles/filedetails/?id=720460154 In this case, the came start up normally up to menu, but when trying to start a new game of load a save at the end of the loading screen it goes black screen and crash.

Another thing that happen in both case is that the game doesn't load the visuals for the R* logo on start up but play the song normally, then goes to black screen and I have to alt-tab to show the game main loading screen.

You'll found attached proton logs for both cases and my system info.

steam_sys_info.txt

steam-12120_no_mod.log

steam-12120_moded.log

[guihkx]

@blackdevil72 Keep in mind that GTA:SA is a mess even on Windows.

That being said, I'd recommend against playing without the FPS limiter, because you're likely to experience a lot of random crashes and weird bugs.

Another thing that happen in both case is that the game doesn't load the visuals for the R* logo on start up but play the song normally, then goes to black screen and I have to alt-tab to show the game main loading screen.

If I remember correctly, that's because Wine's implementation of the Media Foundation Platform (mfplat) is not fully complete, so in some cases it won't be able to reproduce these intro videos.

I don't play GTA:SA anymore, but I still have it installed. I was able to beat the game just by playing on Wine, but not without a lot of random crashes and deadlocks.

Finally, I'd recommend downgrading your GTA:SA copy to v1.0 first, then installing a couple of mods:

• Silent's ASI Loader - So you're able to use mods
• ModLoader - Load/unload mods on demand, without having to directly replace game files
• SilentPatch - This one fixes A LOT of game bugs
• Widescreen Fix - Self-explanatory
• (Optional) Framerate Vigilante - So you're able to play with 60 fps.

There are some other great mods as well on mixmods.com.br (it's a brazilian site, but most posts are translated to English too), but I'd say these are the "essential ones".

[blackdevil72]

Thank you for your answer.

But that is exactly what I already did.

I knew that disabling FPS limiter isn't something to do. I just wanted to see what happen to that FPS drop when it was, and it is still there with it enabled or not.

Downgrading and modding has been done too. See second part of the problem.

[flowHater]

@guihkx Thanks for tips. I tried, but I think i would have to downgrade the game to an anterior version. But I preferred to install Grand Theft Auto: San Andreas – Definitive Edition Simply have to replace file in the install directory. Easier than setup one by one each mods. But even when I has only SilentPatch, the mouse get out the screen to go on my other monitor. Without, on vanilla version, I don't get the issue. I could reproduce with only SilentPatch + Silent's ASI Loader.

Weird, I didn't find anyone with the issue. Have you an idea.