[Solution Found] Crash @ loading screens

TinCan

The avid forum reader may have noticed I was having trouble running the game since build 190. I suspected it had something to do with the code that uses multi-threading that allows the client and server code to run simultaneously but I figured it wasn't my fault. It turns out it was all my fault. < embarrassed face> I am posting in case it might help others.

<b>Description of problem:</b>
When trying to start a map the loading screen appears and it seems to stall right then. No zoom effect, No dots ...., nothing. 40-45 seconds later the picture changes and then a second later it crashes. The game ran ok before build 190.

<b>Solution</b> (at least for me):
<u>ENABLE Hyper-Threading in your BIOS</u>
That's right, Hyper-threading was turned off in my BIOS. Research revealed that DELL defaults to OFF. Even though my CPU was capable of Hyper-threading it was not using the technology. After turning it on in the BIOS WinXP found new hardware and updated the drivers and required a restart. You can imagine my joy when the map loaded! WOOT! OK off to play for the first time post gorilla.

player

It's your fault you hadn't enabled Hyper-Threading? I haven't enabled it either, no issues to report. Perhaps it was a driver-issue of some kind, that was coincedently resolved the same time you changed the BIOS-settings.

TinCan

<!--quoteo(post=1911178:date=Mar 8 2012, 04:14 AM:name=player)--><div class='quotetop'>QUOTE (player @ Mar 8 2012, 04:14 AM) <a href="index.php?act=findpost&pid=1911178"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->It's your fault you hadn't enabled Hyper-Threading? I haven't enabled it either, no issues to report. Perhaps it was a driver-issue of some kind, that was coincedently resolved the same time you changed the BIOS-settings.<!--QuoteEnd--></div><!--QuoteEEnd-->
You have a single core and Hyper-threading is turned off and it runs? interesting. Perhaps you are right the driver update may have fixed the snag. I guess I could test by turning it off now but I can't see any reason not to have it on now that I have been made aware.

I'm curious do you see two processors listed in your device manager?

endar

You didn't specify it was a single core machine, slight distinction there.

player

It doesn't matter:

Single-core, no HTT: Runs multi-threaded code without issue.
Single-core, with HTT: Runs multi-threaded code without issue.
Multi-core, no HTT: Runs multi-threaded code without issue.
Multi-core, with HTT: Runs multi-threaded code without issue.

yimmasabi

Whatever at least NS2 Should have warn us about that.
On the otherhand there is no problem in all games in my desktop (Skyrim, MW3, Guild Wars, Forsaken World, Anno, X3 TC, ....)
Why NS2 has this problem?

Thanx TinCan. Im gonna check it soon, too busy now :D

TinCan

Looks like Max fixed this:
<!--quoteo--><div class='quotetop'>QUOTE </div><div class='quotemain'><!--quotec-->NS2|B206|Changelog Summary
...
Fixed crash when running the game on a single core machine.
...<!--QuoteEnd--></div><!--QuoteEEnd-->
So that's a good thing!

Max

<!--quoteo(post=1930683:date=Apr 27 2012, 07:45 AM:name=TinCan)--><div class='quotetop'>QUOTE (TinCan @ Apr 27 2012, 07:45 AM) <a href="index.php?act=findpost&pid=1930683"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->Looks like Max fixed this:

So that's a good thing!<!--QuoteEnd--></div><!--QuoteEEnd-->
Indeed I did. I'm sorry I missed this thread.