I have been hosting N3 races for a while now, and have been plagued with
random (and all to often) "system lockups". I have read all the message
threads about this issue, and have tried ALL the suggestions offered.
I feel that my lock ups have been resolved! I am setting the "starting
field size" at 2 entries higher than my "max players". Like this...
allowing 20 racers, but setting the field size to 22. I am not using AI,
just the extra 2 slots.
I hosted for about 5 hours Friday and 4 hours on Saturday.... PC crash free!
It was great!
-Paul (ScanManCable on WON)
My reply address is false.
Please post replies to this news group.
If you need to e-mail me, it's
scan-man at home dot com
Paul,
I noticed that on friday, there was a time where won.net looked to be down for
a brief amount of time. (no one anywhere in any of the areas) Then, just a
minute later, there were races coming online one by one. I didn't think
anything about it at the time. But now, with your post, I realized that I have
not had any N3 lockups since then.. Friday or Saturday.. Maybe its fixed? :-)
Hitch-Hiker
Quoted text (18 lines)
> I have been hosting N3 races for a while now, and have been plagued with > random (and all to often) "system lockups". I have read all the message > threads about this issue, and have tried ALL the suggestions offered. > I feel that my lock ups have been resolved! I am setting the "starting > field size" at 2 entries higher than my "max players". Like this... > allowing 20 racers, but setting the field size to 22. I am not using AI, > just the extra 2 slots. > I hosted for about 5 hours Friday and 4 hours on Saturday.... PC crash free! > It was great! > -Paul (ScanManCable on WON) > My reply address is false. > Please post replies to this news group. > If you need to e-mail me, it's > scan-man at home dot comHey Paul. We've been doing the same thing with our servers and it seems to have
stopped the lock-ups. Don't know if this was the problem but it is working.
Quoted text (18 lines)
> I have been hosting N3 races for a while now, and have been plagued with > random (and all to often) "system lockups". I have read all the message > threads about this issue, and have tried ALL the suggestions offered. > I feel that my lock ups have been resolved! I am setting the "starting > field size" at 2 entries higher than my "max players". Like this... > allowing 20 racers, but setting the field size to 22. I am not using AI, > just the extra 2 slots. > I hosted for about 5 hours Friday and 4 hours on Saturday.... PC crash free! > It was great! > -Paul (ScanManCable on WON) > My reply address is false. > Please post replies to this news group. > If you need to e-mail me, it's > scan-man at home dot comHumm.... you are correct. Maybe WON fixed the PC crash problem, and I just
happened to change my set up at the same time.
Either way, I'll be VERY happy if hosting is stable!
-Paul
My reply address is false.
Please post replies to this news group.
If you need to e-mail me, it's
scan-man at home dot com
> Well.... I thought I was onto something with the max player VS field size
> issue, but I got another hard lock up this afternoon when hosting N3 again.
> :-(
Hard lockup, Or boot out to windows screen? Hard lockup my be system conflict..
I had my join in number set to accept 32 cars all day!! AND had my field start
size set at 28! Trying to see if the slowest qualifiers would not be allowed to
race.. Unfortunately, always had more than 4 leave before qualifying had
ended. But I have not had connection loss (boot to windows) since last
Thursday! :-) If Papy did something, IT WORKED! It also seems that about
4-5 of the 30 that join me are using the "t_play2" car.
I'm a happy camper!
Hitch-Hiker
Well.... I thought I was onto something with the max player VS field size
issue, but I got another hard lock up this afternoon when hosting N3 again.
:-(
Curiously it was about 1/2 second after a second racer entered the session
**using the "t_play2" car**. Coincidence, or bug?? I think I read about
someone else experiencing host lock ups when there were 2 players using that
car.
-Paul
My reply address is false.
Please post replies to this news group.
If you need to e-mail me, it's
scan-man at home dot com
My multiplayer N3 PC crashes have always been hard lock up. The screen
freezes and the mouse and keyboard are dead. Nothing short of hitting the
reset button on the PC brings it back to life. I am running with glide 2.56
and all the manufacturers latest drivers. I get absolutely NO lock ups when
racing off line.
BTW, my lock ups always seem to happen right after someone joins the
session.
Glad to hear that you had a successful day of racing!
System specs:
Dell P2-450 128meg ram
BlackMagic Voodoo2 12 meg
Nvidea TNT 16 meg
Sound Blaster Live
--
-Paul
My reply address is false.
Please post replies to this news group.
If you need to e-mail me, it's
scan-man at home dot com
I was allowing max 12 drivers and my field size was 2. Had no problem at
all. My pc lock up (had lock up) when one of the drivers disconnected. I
have a theory: maybe someone logged on at the same as the guy
disconnected and that cause the number of drivers to go over the limit
of 12.
The field size is the number of AI that appear when you get on the track
with during the practice session.
Ex: I started a server, set the field size to 2. There was 2 cars on the
track. Mine, and car #143 (with my name also). When someone else joined,
car #143 changed to that driver's car # and with that driver's name.
Ex 2: I started a server, set the field size to 5. There was 5 cars
sitting in the pits (including mine), with the name of the drivers
corresponding to the names found in multi.lst. Please note that at that
point, I was the only human player on the server.
Conclusion: I think the field size has no real bearing on the quality of
the connection. It just alters the number of AI cars that appear
initially (even though I left the AI drivers box unchecked).
Philster
