Hello. I recently got the Humble Bundle with Natural Selection 2 included. I too am experiencing a crash after firing a weapon. No error log or warning.
Actually before playing i go in options menu and click two times on "display" and two times on "particles quality" and then on "back", usually it works.
C'mon guys... this is beyond sad. Even after you've been featured in the humble bundle, still the problem persists.
And no communication just exacerbates things. Are you working on this? Are you just ignoring it? Is a fix around the corner? Will I never be able to play NS2, *the game I paid money for*?
Honestly, if It hadn't been a gift from friends I'd already contacted Steam support and asked for a refund. My friends were tired of listening to me talk about how I loved NS1 and decided to do something nice for me, and their money just paid for boring loading screens and frustrating crashes...
shokksAway from KeyboardJoin Date: 2013-10-14Member: 188698Members
edited January 2014
+1 ! The topic was launched for so much time ! And any reactions from you ! And you want us to buy other games from you ? I know you're not a big equip ! But wait... 4 months and there isn't any fix.. Can you just explain it to the people who bouught your game ?
With the latest build I can finally load a map, but as soon as I try to shoot, down it goes.
I bought the game 7 MONTHS AGO and I STILL CANNOT PLAY IT.
I want to know if this bug is in fact being tackled... I feel completely ripped off and because I gave you guys time to fix everything I believe I've lost my right to a refund. It's seriously disappointing.
Soul_RiderMod BeanJoin Date: 2004-06-19Member: 29388Members, Constellation, Squad Five Blue
Can you supply more information on the problem? You may have a different issue as no-one else has complained about this since the latest build as far as I am aware.
Post a TechSupport zip file so it can be looked at please.
Can you supply more information on the problem? You may have a different issue as no-one else has complained about this since the latest build as far as I am aware.
Post a TechSupport zip file so it can be looked at please.
I've already uninstalled, and it's the same bug that's been reported everywhere. The latest build does not fix this, it fixed another issue which was related to the 3.12+ kernel (and the fix indeed works).
Do I get any guarantee it's going to be looked at by the devs and get an answer (not necessarily an inmediate solution) within a week? If so, I don't mind downloading it again and sending gdb output and stuff but I don't really want to waste my time.
I've tried to backtrace the problem with gdb, but with gdb everything works fine.
After closing gdb and NS2 and starting NS2 again, it works without gdb.
Can you supply more information on the problem? You may have a different issue as no-one else has complained about this since the latest build as far as I am aware.
Post a TechSupport zip file so it can be looked at please.
Allow me to disagree. No-one else has complained because its been like this for months, and ns2 takes 5+ minutes to load a map, and it still crashes. So people aren't exactly testing every 5 minutes.
But I was glad you told me it was fixed... but it's not -- Same issue: Load map. Go marine. Shoot. Crash.
Same here, the last update did allow me to get into the game (would crash while loading before), but now it crash as soon as I shoot.
Using kernel 3.14-rc3.
AnAkIn, Can, you post a sysinfo. Trying to narrow things down as much as possible.
Edit:
Also, can we try with low textures and with the decal lifetime at 0? I'm playing around with it now and that seems to be the difference between a stable ~2200M memory usage and it spiking fast.
Also, can we try with low textures and with the decal lifetime at 0? I'm playing around with it now and that seems to be the difference between a stable ~2200M memory usage and it spiking fast.
I believe that's my configuration right now (9800GT, you can't ask more of it).
AnAkIn: Have you tried going to an empty server, such as in training mode? My experience is that you can still spawn and walk around, the crash hits exactly when you try to shoot. In a pub everyone is shooting (surprise!), I guess that's why it happens even faster.
AsranielJoin Date: 2002-06-03Member: 724Members, Playtest Lead, Forum Moderators, NS2 Playtester, Squad Five Blue, Reinforced - Shadow, WC 2013 - Shadow, Subnautica Playtester, Retired Community Developer
Steam overlay is, from what i understand, actually some pretty hacky thing that somehow plugins into any opengl app. It might very well be that this goes bad in some instances, specially because opengl steam overaly is much younger than dx overlay on windows. Does steam have some kind of bugtracker to report this issue?
BTW why not to remove the shader and maps cache completely on the game update (it's to the devs of course)? It should be regenerated anyway and I can assume if it's creating issues. I looked up my directory and found there files with timestamps of Jan 20 while the latest build was released a couple of days ago.
All those crashes are inside the NVIDIA driver so it's being fed with invalid data. Could it be just outdated shaders from the cache? What else can be so different that it works on one installation and crashes on another? You may also try to create a separate user, install Steam and NS2 on it and try to shoot some skulks there. This way you can be pretty sure that no previous launches or other stuff hinders the game. The only place Steam and NS2 can write data is your homedir so create a clean one and see if it helps.
Comments
Please fix this devs.
Have Ubuntu 13.10 Lonovo Y500 i7 64 Bit and an Nvidia Geforce GT 650M.
Please can you fix it.
Kubuntu 13.10
Intel Core i5 2400
3gb ram
Nvidia GTX260
Thank you.
console:Segmentation fault
pid 6041 != 5985, skipping destruction (fork without exec?)
Game removed: AppID 4920 "Natural Selection 2", ProcID 5965
Nvidia GeForce 450 GTX
319 Driver from default Ubuntu repository
Game still crash when shooting
And no communication just exacerbates things. Are you working on this? Are you just ignoring it? Is a fix around the corner? Will I never be able to play NS2, *the game I paid money for*?
Honestly, if It hadn't been a gift from friends I'd already contacted Steam support and asked for a refund. My friends were tired of listening to me talk about how I loved NS1 and decided to do something nice for me, and their money just paid for boring loading screens and frustrating crashes...
No graphic setting will help.
LTS kernel doesn't work.
With the latest build I can finally load a map, but as soon as I try to shoot, down it goes.
I bought the game 7 MONTHS AGO and I STILL CANNOT PLAY IT.
I want to know if this bug is in fact being tackled... I feel completely ripped off and because I gave you guys time to fix everything I believe I've lost my right to a refund. It's seriously disappointing.
Post a TechSupport zip file so it can be looked at please.
I've already uninstalled, and it's the same bug that's been reported everywhere. The latest build does not fix this, it fixed another issue which was related to the 3.12+ kernel (and the fix indeed works).
Do I get any guarantee it's going to be looked at by the devs and get an answer (not necessarily an inmediate solution) within a week? If so, I don't mind downloading it again and sending gdb output and stuff but I don't really want to waste my time.
After closing gdb and NS2 and starting NS2 again, it works without gdb.
I haven't tested a complete restart.
Allow me to disagree. No-one else has complained because its been like this for months, and ns2 takes 5+ minutes to load a map, and it still crashes. So people aren't exactly testing every 5 minutes.
But I was glad you told me it was fixed... but it's not -- Same issue: Load map. Go marine. Shoot. Crash.
Here is the backtrace: http://vpaste.net/Ja8FY
And the core file is here: https://mega.co.nz/#!t85RzZhD!PqDtthyW4gcByx8IVbkX_SipajAhIEfeEzfm91KWxqs (sha1sum db3e676a6c8105670ddbf43269c71b8ad5a14759)
There's no techsupport binary in the ns2 linux directory, so I'm at a loss as to how this info can be generated.
I'm willing to help debug this, but you have to tell us what you need. I *DO* want to play NS2. I just wish you wanted me to play NS2 too.
~/.config/Natural Selection 2/log.txt
~/.config/Natural Selection 2/system_options.xml
the output from something like sysinfo to give us a driver version and hardware config
I have seen this bug occasionally. Of course, it seems that if I have gdb attached it never seems to happen.
log.txt: http://pastebin.com/04pFdp7c
system_options.xml: http://pastebin.com/Gn86yJbZ
sysinfo.txt: http://pastebin.com/eErqcbCX
I just upgraded to 331.38 to see if it made any difference but still have the issue, but that's why the core dump I took earlier has an older version.
I'll try attaching gdb before I hit the bug, see if it still crashes that way.
If it helps, i'm willing to allow a ns2 dev to debug this remotely on my machine.
A less detailed, more recent backtrace:
Using kernel 3.14-rc3.
Edit:
Also, can we try with low textures and with the decal lifetime at 0? I'm playing around with it now and that seems to be the difference between a stable ~2200M memory usage and it spiking fast.
Here's my backtrace:
Seem like there is a bug in the Nvidia drivers, or in how the game calls some OpenGL functions.
Not sure what kind of sysinfo you need, but I guess that's enough:
ArchLinux 64bit.
Nvidia 334.16 with a GeForce GT 540M.
Linux Kernel 3.14-rc3.
I believe that's my configuration right now (9800GT, you can't ask more of it).
AnAkIn: Have you tried going to an empty server, such as in training mode? My experience is that you can still spawn and walk around, the crash hits exactly when you try to shoot. In a pub everyone is shooting (surprise!), I guess that's why it happens even faster.
Tested on a training map, as soon as i fired it quite to my desktop.
Quite annoying since I paid out to be a supporter too.
Not sure why that would make it crash?
Also removing the config-folder and backtracing with gdb didn't the job for him. (His backtrace was exactly the same: http://forums.unknownworlds.com/discussion/comment/2185180/#Comment_2185180 )
My game works so far since my last post.
+1 no difference when disabling overlay, crashes in the same manner.
All those crashes are inside the NVIDIA driver so it's being fed with invalid data. Could it be just outdated shaders from the cache? What else can be so different that it works on one installation and crashes on another? You may also try to create a separate user, install Steam and NS2 on it and try to shoot some skulks there. This way you can be pretty sure that no previous launches or other stuff hinders the game. The only place Steam and NS2 can write data is your homedir so create a clean one and see if it helps.