GTA: San Andreas (12120) #143
Comments
kisak-valve
added
the
Whitelist Request
|
Did you try to use a controller in game? |
kisak-valve
changed the title
|
Also runs perfect, but with some strange issue. |
|
I also get random freezes during transitions (like leaving the house) and sometimes cutscenes. |
|
@flohag |
|
PROTON_NO_D3D11=1 don't work for me. But if is use PROTON_NO_ESYNC=1. GTA:SA seems to work fine. |
|
This game also runs flawless for me on Arch with Nvidia, Only issue is the controller, i use a XB1 controller, i can walk and look around, but none of the buttons seem to work. |
|
with the proton beta 4 the controller steam controller works for me. |
|
I was also getting random freezes during transitions, setting Game doesn't run perfectly though, since I've encountered some issues. Just like in GTA: VC I couldn't save game until I manually created Additionally, there is a problem with gameplay; namely in the mission "Cesar Vialpando" (bumping car) the animation of the arrows that signal when key is to be pressed is really choppy, as if its framerate was really low, to the point where pressing buttons at the right time is unlikely, making it close to impossible to pass the mission just by looking at the animation. After multiple tries I have yet to pass it; over a decade ago on windows I had no problems with easily passing the mission. Edit: in addition to choppy animation, up/down keys are switched, which further increases difficulty, but it seems that this problem also exists on windows in some(?) cases. |
|
After playing for 2h game crashed: https://gist.github.com/zetok/1b28f65bfeb2cdcc72ba2ad1c99a5628 |
|
I had also problems with the Mission "Cesar Vialpando" but activating the FrameLimiter fixed it for me. |
It didn't seem to have changed anything for me. I've turned in on during the mission though, perhaps that matters. Problem with choppy animation also affects the dancing mission, thankfully at least this one didn't have up/down keys switched. There was also a problem with the first mission outside of 1st city where one needs to take a photo with camera ("Badlands"). When I made the photo game froze. After that I've tried to take a photo outside of the mission, and it also froze the game. I'm guessing that the freeze has something to do with the game trying to save photo in I could beat the bumping car and dancing missions by pressing buttons according to the beat of the music rather than the animation, but the problem with game freezing after taking a photo doesn't seem to have any workaround. Until that gets fixed it doesn't seem like the game can be whitelisted. |
|
EDIT 1: Fixed some typos Here are my findings on my system (No mods installed): Specs (Full specs can be found here) I can launch and save the game, although there are visual defects, even though its not really a big deal for me (for now), it would be something that it might be worth to take a look at.
There would also be times where I launch the game and it would show a black screen for a while, and to resolve it was to force quit the game, or clicking on it until it would show the game intro. Also, when I would load/start a new game, it may freeze at the full loading bar causing me to force quit the game. |
|
I also noticed random crashes after certain loading screens. |
|
Initially had some problems with the mouse "locking" into constant movement. I am using a gaming mouse with tons of buttons, turned out changing to an older mouse solved it. Game now runs perfectly with the exception of the odd freeze during transitions/cut scenes. Mostly solved using suggestions in this thread. Running on Ubuntu 18.04, Nvidia 396.54. |
|
As of right now, on newest Proton 3.7-6 Beta and after some game updates "Badlands" mission can now be passed (game no longer freezes after taking a picture with camera). |
|
Camera goes to a top down view and spins when I enable gamepad in game settings. I'm using a DS4. https://gist.github.com/daasuharo/b18e39c1f39b372a3e73892748c2da28 |
|
@daasuharo me too (tm). With a steam controller configured as controller everything is 100% ok. When using a xbox like gamepad (uses xpad kernel driver), and steam to reconfigure that gamepad as a gamepad, it seems as if SA sees a different analog input which is hard to counter balance. When I configure steam to emulate mouse/keyboard SA works "fine". Of course the game requires a gamepad to play with, so it's not that fine. |
|
My experience has been the complete opposite - the game crashes after the title card is shown. How I managed to get it working was copying the game files to a new Wine prefix and running gta-sa.exe with cwd being in the same directory (otherwise the game files aren’t found). I also installed a bunch of stuff with winetricks, so I can’t pinpoint off the top of my head what the issue exactly was. Aside from all that, I get major stuttering (presumably) due to Edit: I use the integrated Intel GPU, so it could be a Mesa-specific problem by the looks of things. |
|
I am still getting lockups after certain loading screens. Ubuntu 18.04 |
|
Grand Theft Auto: San Andreas (12120) Issue transferred from #1630. Compatibility Report
System Information
I confirm:
steam-12120.log-Part_1 SymptomsThe game itself appears to run perfectly. The only problem is the game locks up (crashing) quite often and I can't really figure out why. It first froze seconds after clicking the new game button. After restarting I was able to get a good half hour in before the game crashed again. The longest stretch I've managed was about an hour. But it only locks in between cutscenes (like when you walk into a red circle to accept a new mission, or when the game first starts) and never when you have control of the character. If the crashing problem could be fixed then this game could easily be whitelisted. |
The thing is that GTA: San Andreas (vanilla, no mods; also both Steam an non-Steam versions) has this issue on Windows as well as far as I experienced. Not only Windows 10 but even 7 and possibly Vista. Starting the game again usually solves the problem but if certain saves after loading just won't work even if you try multiple times then there might be issue somewhere else (considering you did nothing extra that would make the save unloadable, f.e. duping missions etc). Just adding this as a little note for consideration. |
|
I also have phantom inputs but as described above this could be caused by my XBox One Controller (Afterglow Prismatic XBox One Controller) and/or my Gaming Mouse (Sharkoon SKILLER SGM1) maybe those devices are detected with some sort of wrong calibration. Game itself runs (as far as I can tell) with no graphic glitches nor crashes but because of the input problem I did not played it a lot. |
|
I'd like to chime in as San Andreas is my favourite game and I definitely think it should be whitelisted. Most of the issues that are described in this thread are present on Windows too. Specifically, the freezing when transitioning to and from interiors or cutscenes, and the phantom input when a controller is plugged in. The freezing is caused by extremely high frame rates at the point of transition and can be worked around by enabling the frame limiter ingame, although I don't recommend that as it caps the frame rate to a horrifying 25 FPS. The controller issues are because San Andreas predates Xinput and uses an older standard that is incompatible with modern controllers. Using a generic controller from the early 2000s should work fine, in theory (haven't tested with Proton, but have on Windows many years ago). Both of these issues can be very easily fixed with mods on Windows, and the same is true on Proton. Installing Ginput will solve your controller woes and also add controller button prompts to the game. Installing SilentPatch will solve the freezing and improve the overall stability of the game while restoring missing graphics from the console versions. With these mods installed I have achieved 100% completion in Proton, with my longest session lasting almost 10 hours. I did not experience a single crash. Furthermore, alt-tabbing San Andreas on Windows is a total mess, but with Proton it's no issue at all. To me, this makes the Proton experience actually much better than the native Windows experience. If that doesn't deserve to be whitelisted then I don't know what does. Literally the only issue I can think of is the fact that the intro video doesn't play. This can probably be solved by installing a video codec with protontricks. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
If it works in desktop mode, but not in steam compositor mode it's more like a steamos bug. Actually it's a steam client+steam os platform bug I think. |
|
Game works completely fine with proton 5.0-2. |
Do you use SteamOS for the test? |
|
@vladislavyuzbekov archlinux with kde. |
|
I know mods aren't supported at all, but now the game doesn't work anymore with Proton 5.0-3. It does launch but it gets stuck in this black screen, before the NVIDIA logo even shows up. So I have to alt-tab and run If I go back to Proton 4.11-12, however, the game works again with all mods I have. I'll post the log files here, but just by taking a quick look at it, I believe the issue seems related to the following error messages: Proton 5.0-3: 5.0-3_steam-12120.log |
|
Hmm, so I have this mod called Improved Fast Loader installed, but it was disabled (on purpose). What it does is skip all the intros and the loading screen, putting you directly in the game's main menu, right after you launch it. I went back to Proton 5.0-3 and enabled that mod. And bingo! Now I'm not getting any of those GStreamer warnings and the game runs mostly fine again:
I say mostly fine because, sometimes, the game will lock at 30 fps when I'm outside of the safe house. Sometimes that doesn't happen (like in the screenshot I just posted above)...
I'm also using Framerate Vigilate, which is supposed to lock your framerate at 60 fps and fix some fps-related bugs, so I'm almost sure this fps issue I'm having now, has something to do with the mods loading order in modloader. I'll just have to figure out the right order, I guess. Weirdly enough, this has never happened to me while I was actually beating the game at 100% using Proton 4.11-*. FWIW, here's a new log file for Proton 5.0-3 with Improved Fastloader enabled and also the fps issue not present: improved-fastloader_steam-12120.log |
Whitelist Request
System Information
LOG: Works great out of the box for me, posting log due to previous posts about bugs. |
|
Also faced bug with on-transition hang. With nvidia gt650m, with intel 7500u gpu, with dxvk or wine d3d, all setups has this bug. Don't known what the reason |
|
This would be a great time to mention using a window managers that is built with XCB, rather than the obsolete Xlib. https://wiki.archlinux.org/index.php/Comparison_of_tiling_window_managers#Comparison_table |
|
Doesn't run on my laptop with Proton 5.0-6. Haven't tried 5.0-7. It works on that box, however, with generic Wine64
|
|
Doesn't start on my desktop either. Haven't tried Wine. OS: Ubuntu 18.04.4 LTS
|
|
Hello @PopeFelix, Intel's Ivybridge chipset has incomplete 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 Alternatively, you can tell Proton to use wine's DirectX to OpenGL render path by adding Your nVidia GT 520 video card is part of the Fermi generation, which does not support Vulkan, but the Intel Haswell chipset in the i7-4770 does have experimental support. The same applies as written above. |
|
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 ***@***.***> 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
<#143 (comment)>,
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.
|
|
The Oibaf PPA provides bleeding edge builds of mesa, while kisak-mesa PPA has point releases. |
|
Installed Vulkan, installed OIBAF. No dice. Latest log attached. |
|
The log has the same indication as before, that Vulkan failed to initialize. Please copy your system information from Steam ( |
|
Thanks, can you check if |
|
Looks like I'm using DRI3. |
|
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 ***@***.***> 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
<#143 (comment)>,
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.
|
|
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) |
|
Much more stable on Proton 5.13. Tested Xbox One and PS4 controllers as well |
|
Hello, 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 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. |
kisak-valve
changed the title
|
@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.
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:
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". |
|
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. |
|
@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. Weird, I didn't find anyone with the issue. Have you an idea. |
This comment was marked as duplicate.
This comment was marked as duplicate.
and others
Tested with on Arch Linux with mesa 18.1.6-1
Launches without any errors or complications. Just works.
The text was updated successfully, but these errors were encountered: