Halaman Toko
Saints Row IV
Semua Diskusi Screenshot Ilustrasi Siaran Video Workshop Berita Panduan Ulasan

Saints Row IV

Halaman Toko
Lihat Statistik:
Pencapaian Global
Saints Row IV > Diskusi Umum > Rincian Topik
 Topik ini telah disematkan, kemungkinan topiknya penting
[V] UncleSam 4 Jan 2016 @ 10:43am
[LINUX] Saints Row IV Troubleshooting FAQ
SRIV Linux FAQ

If you're having trouble with the game please read through this FAQ to see if your problem has already been addressed. As always if you find new work-arounds or fixes for problems you encounter please post them so we can verify and add them to the FAQ for others to use.

Question: The game is stuttering badly is there any way to fix this?
Answer: This could be a number of different things, but many users have fixed this issue by lower the lighting detail in the settings menu.

Question: Help! I’m getting “Missing executable” when I try to start he game!
Answer: Right click the game in your library, select properties and click on the “Local Files” tab. Once you’re there select “Verify Integrity of Game Cache”

Question: I have missing and incorrect textures! Is there a fix?
Answer: AMD terrascale generation hardware has some problems with the newest AMD driver release. To fix this users need to install Catalyst 15.9 rather than the newest drivers.

Question: I’m getting strange red dots / Pixel artefacts is there any fix?
Answer: Pixel artefacts will happen if AA settings and/or texture sharpening are forced on in the Nvidia Control Panel

Question: Why does my Intel GPU work on windows but not Linux?
Answer: The Windows drivers for Intel GPU’s support DirectX 10 features. The equivalent of this in OpenGL is 4.1, however, the Intel GPU drivers for Linux currently only support OpenGL 3.2. Intel graphics are currently unsupported.

Question: I’m crashing and have an Nvidia GPU what can I do?
Answer: There have been reported problems with Nvidia 358.16 Drivers in relation to steam. Try using 352 or 355 series drivers.

Question: Do you support MESA drivers?
Answer: MESA drivers are currently not supported

Question (NVIDIA): I’m getting strange color issues in game. What’s wrong?
Answer (NVIDIA): Players need to make sure they are using the 352 or 355 series drivers. The 340 series has a bug which can cause color issues in game.

Question: I’m getting bad performance issues, what can I do to fix the problem?
Answer: Make sure you are running the game at the native resolution for your screen.
< >
Menampilkan 1-15 dari 282 komentar
Mikachu 7 Jan 2016 @ 4:10am 
If you're using nvidia, you can try changing __GL_THREADED_OPTIMIZATIONS from 1 to 0 in the saintsrow4 script, it changes the fps from 3 to 30 for me.
#1
Sinedio 7 Jan 2016 @ 5:11am 
I'm curious, what CPU does your machine have?
#2
[Linux] Nasra 8 Jan 2016 @ 1:53pm 
No problems with SRIV, this game works like a charm ! Thanks to devs !
#3
Madruga 8 Jan 2016 @ 4:43pm 
with phenon x6, 8 gb ram, asus gtx 750 ti 2 gb, i still have frame rate around 20 fps, even on low graphics settings
#4
Nobody 9 Jan 2016 @ 1:15am 
Oh good
#5
Tajer 11 Jan 2016 @ 4:38am 
It's interesting that they say stuttering can be caused by "many issues" but then only mention one. I get awful framerates on my i5 with GTX 970, even with lighting off. Turning off threading optimization makes it slower. I shouldn't have to run it on low to get close to 60 fps.
#6
Brother Ray 12 Jan 2016 @ 10:04pm 
On high resoltions (2560x1920) I get black borders around a small box during cutscenes. Only the small box in the center has viewabale rendering.
#7
Brother Ray 12 Jan 2016 @ 10:26pm 
Also the rendering using OpenGL is implemented poorly. The models' skeletons are clunky and grab on to clothing at strange angles and places. The level of detail on some objects are far different from others. General render quality seems low, comparable to DX8, but effects such as sparks and explosions are modern enough. Shaders seem grainy and unpolished.

Of course, I've never played this game on Windows, but SR V looked great, so I'd expect this one to at least match it.

What gives? It'd be OK if it was at least consistant.
#8
Ariva 09 13 Jan 2016 @ 4:46am 
12eweq
#9
mitch074 17 Jan 2016 @ 2:37pm 
OK, so I finished the game (SR4), using Mesa drivers (11.2 daily snapshots) + Linux kernel 4.4 final on a Radeon R9 270 2Gb running at 2560x1440. Using Mesa allowed me to run GALLIUM_HUD, and prevented my computer to crash - using Catalyst 15.9 and latest yielded instabilities and performance wasn't much better.

The troubles I had:
- after 1 or 2 hours of playing, I would regularly get "hangs" that lasted from 1 to 5 seconds; gameplay would resume after that, but framerate would go down badly. This happened mainly when running for a long time and crashing many elements; it could be either keyboard- or driver-related. Other reports I've read seem to disculp the drivers though.
- I got a couple app crashes. Those were caught and reported by the game's exception catcher.
- especially on later missions, NPCs would sometimes fail to trigger the next part of their scripts, forcing me to fail the mission and start anew. The same, some key elements would pop in at completely goofy locations, again forcing me to fail the mission and restart.
- Although game was playable, performance was NEVER stellar; I would get 25fps at 1280x720, low details, on the same scene that got me 20fps at 2560x1440, maximum details. VRAM usage (on Xfce4) would always be around 1.1 Gb.
Terakhir diedit oleh mitch074; 17 Jan 2016 @ 2:38pm
#10
DirtyCamper 18 Jan 2016 @ 7:14am 
Hi, I have fglrx 15.9 and kernel 3.18.16 on debian/jessie with most of the system on FCoE bcache-d on a local SSD. I have a steam controller and a steam link.
Diposting pertama kali oleh mitch074:
The troubles I had:
- after 1 or 2 hours of playing, I would regularly get "hangs" that lasted from 1 to 5 seconds; gameplay would resume after that, but framerate would go down badly. This happened mainly when running for a long time and crashing many elements; it could be either keyboard- or driver-related. Other reports I've read seem to disculp the drivers though.
I've seen the stalls too. I've played 50% of the game using the steam link, but except for audio lag up to 10s and input lag, it works. The stalls I've seen were always local. I thought it might have been my FCoE, but now I know it isn't.
I've seen other stalls combined with fglrx and a 1000Hz usb gaming mouse, but that was a game engine ♥♥♥♥ up.
This game however automagically continues (audio and video in sync) as if the stall never happened. Just a lost 5s.
Diposting pertama kali oleh mitch074:

- Although game was playable, performance was NEVER stellar; I would get 25fps at 1280x720, low details, on the same scene that got me 20fps at 2560x1440, maximum details. VRAM usage (on Xfce4) would always be around 1.1 Gb.
I play it on 1280x720 on high quality settings. I don't know how to snoop the FPS though.
#11
mitch074 18 Jan 2016 @ 2:26pm 
Diposting pertama kali oleh DirtyCamper:
Hi, I have fglrx 15.9 and kernel 3.18.16 on debian/jessie with most of the system on FCoE bcache-d on a local SSD. I have a steam controller and a steam link.
[...]
I've seen the stalls too. I've played 50% of the game using the steam link, but except for audio lag up to 10s and input lag, it works. The stalls I've seen were always local. I thought it might have been my FCoE, but now I know it isn't.
I've seen other stalls combined with fglrx and a 1000Hz usb gaming mouse, but that was a game engine ♥♥♥♥ up.
This game however automagically continues (audio and video in sync) as if the stall never happened. Just a lost 5s.
[...]
I play it on 1280x720 on high quality settings. I don't know how to snoop the FPS though.

The stalls : yes, the game deals with them automatically. I had the game crashing hard on me a couple times though.

Playing : I use keyboard+mouse.

FPS : as I use the Mesa drivers (NOT fglrx), I can make useof the driver's built-in Gallium HUD which allows real-time incrustation of stuff like GPU temp, use and frequency, VRAM usage, FPS... With graphs.

Your report seems to confirm that whatever troubles I havewith the game aren't related to the driver.
#12
Kandarihu 18 Jan 2016 @ 3:33pm 
So anyway, I have been unable to access the Community Site for the sake of uploading characters. From my research, this problem IS specific to the Linux port. And the devs are working on fixing it.
Terakhir diedit oleh Kandarihu; 18 Jan 2016 @ 3:34pm
#13
Smoggylamb #FixTF2 23 Jan 2016 @ 2:16pm 
Which build of Linux do you recommend?
I would NOT recommend installing the fglrx drivers on Ubuntu 14.10 or newer, because it permanently locks you out of your operating system afterward.
#14
DirtyCamper 25 Jan 2016 @ 2:59am 
Diposting pertama kali oleh Destroy Them With Tables:
Which build of Linux do you recommend?
I would NOT recommend installing the fglrx drivers on Ubuntu 14.10 or newer, because it permanently locks you out of your operating system afterward.
That's more like being a noob or not. If you want a recommended one, just use steamos.
Steamos is debian/jessie derived, just like Ubuntu 15.04.
#15
< >
Menampilkan 1-15 dari 282 komentar
Per halaman: 1530 50

Saints Row IV > Diskusi Umum > Rincian Topik
Tanggal Diposting: 4 Jan 2016 @ 10:43am
Postingan: 282

Pedoman dan Aturan Diskusi