I just saw an article on Phoronix that Team Fortress 2 got a big update to the OpenGL renderer. The update includes support for Texture Streaming over OpenGL, which apparently reduces VRAM usage considerably and brings it in line with the Direct3D 9 Renderer. Sounds like this is exactly the reason so much more VRAM is used on Linux. Any chance you guys are going to ever get this code? http://www.phoronix.com/scan.php?page=ne...rer-Update
01-01-2016, 13:56 (This post was last modified: 01-01-2016, 14:00 by sulman.)
On an Nvidia 550 ti with 1GB VRAM, tried 352.*, 355.*, 358.* drivers on my Gentoo box. No real difference in driver performance for Insurgency on my box.
I discovered I can run everything exactly as on Windows with the exception of shaders, which I have on medium. I lose cosmetic parts of the skybox (didn't notice until someone pointed this out) and the fancy lighting on the weapon in first-person, but otherwise it looks pretty much identical to Windows. Shader is the one setting that makes the difference for me.
Using nvidia-smi I ran it using the loop option with different shader configs and concur it is definitely VRAM filling up that causes the tank in FPS, specifically running shaders on high most of all. Textures help, but they're not as significant as shaders. With medium shaders VRAM runs around 80-90%, and I think caching is not affecting performance at this number; at high shaders VRAM is maxed and FPS goes to single digits, presumably as cache bandwith cannot keep up.
I can live with it until I bother upgrading the GPU, God knows when that will be...
17-01-2016, 10:04 (This post was last modified: 17-01-2016, 10:06 by t3kg33k.)
I was referred to this thread from the Steam community.
I am running Fedora 23 with Gnome 3.18. I'm trying gaming for the first time on Steam. I was able to install the Steam client with no issues using Fedy. Steam launches and all is well. I was also able to install Insurgency with no issues. When I launched Insurgency for the first time I got the OpenGL error message I have seen others post. I was able to proceed and the game launched. I then proceeded to join a server I have played many times from my Favorites but the map download hangs. I tried this on several attempts for various maps on the same server and others, all with the same result, download starts then hangs. Sometimes a quarter through the download process sometimes all the way through just before starting the game.
I would really love to play this game on my Fedora build without having to reboot into my Windows 10 build that I use for gaming as I am always in Fedora for my day-to-day computing and prefer to use Linux over Windows.
Here are my specs:
So i decided that i'll post here. I have the same small issue as the guy on the link above. The white box in the left top corner is slightly annoying. Super annoying is the crashing of the client.
Hardware to reproduce the bug:
- 1 screen with 4:3 (1280x1024)
- 1 screen with 16:9 (1920x1080) - TV connected via HDMI
When i turn my TV on and turn it off after i'm not using it anymore 'xrandr' still reports it as 'connected'. Why is this important you ask? Well it is important because when i start Insurgency it shows the splash screen (bug #1 or is it #2?) which means its in 16:9 mode. Otherwise (4:3) the splash screen is not shown.(bug #2.5?)
So the next logical step would be to change the ratio settings right? Of course. We change it back to 4:3, click Apply and all is good again BUT WAIT! Bug #3 is here, advanced video settings are all on High which my lil' APU can't handle. So now we need to change them back to medium/low and hit Apply again. No crash for now until ... we click on Server browser. Bug #4, our client crashes.
Using Ubuntu 14.04 with radeon drivers (opensource drivers).
Other than that the game works as a charm. Kudos for porting to Linux.
This game crashes for me nearly every time I start it. It almost always happens at the main menu or the game selection menu. If I try 3-4 times, eventually it will not crash. It also crashes if I Alt-Tab out of the game and then back into the game. I have 29 dump files. Are these auto-uploaded or would you like me to upload them somewhere?
Debian/stretch w/ nvidia GTX 465. Many of the crashes happen in the nvidia driver but no other games crash for me. Here's the segfault lines from dmesg:
[937179.031898] insurgency_linu: segfault at 0 ip (null) sp 00000000ba5b527c error 14 in insurgency_linux[8048000+1000]
[937208.944920] insurgency_linu: segfault at 4 ip 00000000f62080ff sp 00000000f49e1510 error 4 in libnvidia-glcore.so.340.93[f4d23000+18ea000]
[939187.403213] insurgency_linu: segfault at 4 ip 00000000f61af0ff sp 00000000f4988510 error 4 in libnvidia-glcore.so.340.93[f4cca000+18ea000]
[939200.445258] insurgency_linu: segfault at 4 ip 00000000f61ab0ff sp 00000000f4984510 error 4 in libnvidia-glcore.so.340.93[f4cc6000+18ea000]
[944832.397458] insurgency_linu: segfault at 0 ip (null) sp 00000000bacb127c error 14 in insurgency_linux[8048000+1000]
[944846.295806] insurgency_linu: segfault at 4 ip 00000000f62360ff sp 00000000f4a0f510 error 4 in libnvidia-glcore.so.340.93[f4d51000+18ea000]
[997645.443660] insurgency_linu: segfault at 0 ip (null) sp 00000000b733027c error 14 in insurgency_linux[8048000+1000]
The command interface still doesn't work properly, if you open it, you can't close it anymore and you also can't select the commands. You have to wait until you die or open the game console kill yourself.
Also I still sometimes get a white square in the top left corner, not sure what's up with that.
Otherwise it works flawlessly, even Day of Infamy. Good job guys!
I attached the dump from my most recent crash. Hopefully those are useful now. These crashes really discourage me from even starting up the game anymore, but I'm not sure what's causing them. Any ideas?
I have a problem running Insurgency in my computer:
-Ubuntu 16.04 LTS 64-bit
-8 GB RAM
-Intel HD 4600 graphic integrated video card.
The problem is that every time I try to join a server the game crashes and closes just before finishing loading. After that I have to kill the process. I have found that if I enter to the solo mode (the tutorial) before trying to join a server, and stay there for a while, then go back to the main menu and try to join a server everything works perfect. I don't have any problem doing this, but may be it can be fixed. I have tried steam cache game integrity, and disable steam overlay while in-game. But it doesn't seem to be the problem.