QuovatisTeam InversionJoin Date: 2010-01-26Member: 70321Members, NS2 Playtester, Squad Five Blue
Yeah, I crash like crazy on Tram and get graphical artifacts, but I played a good 2 hours last night on Rockdown and didn't crash once, nor had any artifact problems. Something is wrong with the Tram map specifically.
Yes, the Tram map is bugged ever since Build 170 I believe it was. Have we got UWE to acknowledge that indeed Tram is bugged? I have not seen a single response from the team that they know Tram has issues.
Yes, I have sent in my logs from both the server side (Team #156 US WEST) and my gaming machine which is high end.
ScardyBobScardyBobJoin Date: 2009-11-25Member: 69528Forum Admins, Forum Moderators, NS2 Playtester, Squad Five Blue, Reinforced - Shadow, WC 2013 - Shadow
<!--quoteo(post=1843506:date=May 1 2011, 10:31 AM:name=Obraxis)--><div class='quotetop'>QUOTE (Obraxis @ May 1 2011, 10:31 AM) <a href="index.php?act=findpost&pid=1843506"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->If you guys could post up your logs with dxdiag logs too, or send them to max, he should be able to help eventually.<!--QuoteEnd--></div><!--QuoteEEnd-->
Aren't the logs (not dxdiag logs) submitted with the debug crash window? I've been hesitant to post crash logs on these forums or GS because 1) I've assumed they've already been sent with the debug window and 2) I usually have no way to reproduce the crash. It seems like physically emailing Max crash logs is only useful if I can include a way to reproduce them consistently.
<!--quoteo(post=1844093:date=May 4 2011, 09:24 PM:name=gamester_5)--><div class='quotetop'>QUOTE (gamester_5 @ May 4 2011, 09:24 PM) <a href="index.php?act=findpost&pid=1844093"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->Yes, the Tram map is bugged ever since Build 170 I believe it was. Have we got UWE to acknowledge that indeed Tram is bugged? I have not seen a single response from the team that they know Tram has issues.<!--QuoteEnd--></div><!--QuoteEEnd--> We think there may be some memory issues that are causing a lot of these problems. So, the bigger maps, such as Tram would exacerbate the problems, as we've seen this with our internal tests on some of the other large maps, as well. Probably not a Tram specific thing.
I dont crash when I am in ready room though(I can stay in there for hours), If it was memory leak I would think it would not matter where on the map you would be. It just that i soon as I choose marines or aliens I crash.
<!--quoteo(post=1843509:date=May 1 2011, 11:07 AM:name=Avalon)--><div class='quotetop'>QUOTE (Avalon @ May 1 2011, 11:07 AM) <a href="index.php?act=findpost&pid=1843509"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->That's not true at all. Overclocking, when done right, can be a huge boost to your applications, whether it be FPS in games, a decrease in rendering times, or decrease in media encoding, etc.
However, I would strongly recommend that those overclocked do try to play it stock, because I know that a lot who do try to overclock, don't do it properly, or don't test their stability properly. Even if other programs seem to run fine, it doesn't mean NS2 should run on your OC. It means you need to check your OC for better stability before ruling out your overclock as the culprit.
There's a multitude of programs out there that will stress your system, such as Prime95 or Linpack, and usually 12 hours of testing, error free, is a bare minimum.<!--QuoteEnd--></div><!--QuoteEEnd-->
It's also a huge strain on your CPU in most cases. You're cutting the life in half at least with a good overclock. This is due to electrophilic migration of the gate oxides in the FE channel. Eventually there's no switch there to flip and your processor dies. You don't have anything to worry about so long as it's a mild OC without a voltage increase. The instant you turn up the volts, you're slowly killing your CPU.
Comments
Yes, I have sent in my logs from both the server side (Team #156 US WEST) and my gaming machine which is high end.
Aren't the logs (not dxdiag logs) submitted with the debug crash window? I've been hesitant to post crash logs on these forums or GS because 1) I've assumed they've already been sent with the debug window and 2) I usually have no way to reproduce the crash. It seems like physically emailing Max crash logs is only useful if I can include a way to reproduce them consistently.
We think there may be some memory issues that are causing a lot of these problems. So, the bigger maps, such as Tram would exacerbate the problems, as we've seen this with our internal tests on some of the other large maps, as well. Probably not a Tram specific thing.
--Cory
However, I would strongly recommend that those overclocked do try to play it stock, because I know that a lot who do try to overclock, don't do it properly, or don't test their stability properly. Even if other programs seem to run fine, it doesn't mean NS2 should run on your OC. It means you need to check your OC for better stability before ruling out your overclock as the culprit.
There's a multitude of programs out there that will stress your system, such as Prime95 or Linpack, and usually 12 hours of testing, error free, is a bare minimum.<!--QuoteEnd--></div><!--QuoteEEnd-->
It's also a huge strain on your CPU in most cases. You're cutting the life in half at least with a good overclock. This is due to electrophilic migration of the gate oxides in the FE channel. Eventually there's no switch there to flip and your processor dies. You don't have anything to worry about so long as it's a mild OC without a voltage increase. The instant you turn up the volts, you're slowly killing your CPU.