rec.autos.simulators

> Not the cars..... the game.
> Seems the littlest things cause serious problems.
> Examples:

> 1.) In Paint Shop, I selected the magnifying tool, then changed my mind
and
> clicked on it again, thinking this would de-select it.  Crashed.

> 2.) Again, in Paint shop, I had the rectangle tool selected, and after
> finishing what I wanted to change, went to the magnifier.  Crashed.

> 3.) Wrecked out of a race at Dover, hit escape and watched the replay.
> After I'd seen what I wanted I hit escape again, clicked no..... crashed.
> After trying to replicate this I found that (at least on my system and a
> friend's) whenever the race is exited while a replay is running it causes
a
> crash.

> 4.) Major wreck happened in front of me at Bristol..... looked like it had
> to involve half the field  :-)
> I slowed down to about 60 mph and went high to drive around it, and all of
a
> sudden the frame rate (which is usually mid to high 20's, even during a
> wreck) dropped way down..... slowed further..... then fell even more, to
> approx. 2 or 3 f/sec.  Then the system crashed.

> 5.) Same sort of thing as in #4 happened at 'dega.

> In all cases the computer totally locked up.  I hit the Win key, tried to
> [Alt]+[Tab] back to Windows, then tried giving it the three finger salute
> many times, but there was *no* response from the system, and I had no
> recourse but to hit the power button, and then upon restart wait as scan
> disk is completed before I could get back to Windows.
> Unfortunately, I get no error message to help indicate what the problem
is.

> Am I doing something wrong, or is N3 in need of a patch of some sort?

> My system:

> 64MB RAM
> 3Dfx Voodoo Banshee w/ 16MB
> Creative Sound Blaster AudioPCI 64D

> If anyone can help me figure out what's going on, it would be greatly
> appreciated, as its getting to the point that I'm afraid to run the game
> :-(

> Most crashes that I've heard about were due to overclocked systems,
usually
> the video card.

> I was experimenting with my Asus V3800 non-ultra (which I rarely do - I'm
> not much into overclocking) and if I pushed it too far, N3 got very
> unstable.

> If you are pushing things, you might want to experiment with putting them
at
> the factory defaults and see what happens.

> -Larry

> > Not the cars..... the game.
> > Seems the littlest things cause serious problems.
> > Examples:

> > 1.) In Paint Shop, I selected the magnifying tool, then changed my mind
> and
> > clicked on it again, thinking this would de-select it.  Crashed.

> > 2.) Again, in Paint shop, I had the rectangle tool selected, and after
> > finishing what I wanted to change, went to the magnifier.  Crashed.

> > 3.) Wrecked out of a race at Dover, hit escape and watched the replay.
> > After I'd seen what I wanted I hit escape again, clicked no.....
crashed.
> > After trying to replicate this I found that (at least on my system and a
> > friend's) whenever the race is exited while a replay is running it
causes
> a
> > crash.

> > 4.) Major wreck happened in front of me at Bristol..... looked like it
had
> > to involve half the field  :-)
> > I slowed down to about 60 mph and went high to drive around it, and all
of
> a
> > sudden the frame rate (which is usually mid to high 20's, even during a
> > wreck) dropped way down..... slowed further..... then fell even more, to
> > approx. 2 or 3 f/sec.  Then the system crashed.

> > 5.) Same sort of thing as in #4 happened at 'dega.

> > In all cases the computer totally locked up.  I hit the Win key, tried
to
> > [Alt]+[Tab] back to Windows, then tried giving it the three finger
salute
> > many times, but there was *no* response from the system, and I had no
> > recourse but to hit the power button, and then upon restart wait as scan
> > disk is completed before I could get back to Windows.
> > Unfortunately, I get no error message to help indicate what the problem
> is.

> > Am I doing something wrong, or is N3 in need of a patch of some sort?

> > My system:

> > 64MB RAM
> > 3Dfx Voodoo Banshee w/ 16MB
> > Creative Sound Blaster AudioPCI 64D

> > If anyone can help me figure out what's going on, it would be greatly
> > appreciated, as its getting to the point that I'm afraid to run the game
> > :-(

> Not the cars..... the game.
> Seems the littlest things cause serious problems.
> Examples:

> 1.) In Paint Shop, I selected the magnifying tool, then changed my mind and
> clicked on it again, thinking this would de-select it.  Crashed.

> 2.) Again, in Paint shop, I had the rectangle tool selected, and after
> finishing what I wanted to change, went to the magnifier.  Crashed.

> 3.) Wrecked out of a race at Dover, hit escape and watched the replay.
> After I'd seen what I wanted I hit escape again, clicked no..... crashed.
> After trying to replicate this I found that (at least on my system and a
> friend's) whenever the race is exited while a replay is running it causes a
> crash.

> 4.) Major wreck happened in front of me at Bristol..... looked like it had
> to involve half the field  :-)
> I slowed down to about 60 mph and went high to drive around it, and all of a
> sudden the frame rate (which is usually mid to high 20's, even during a
> wreck) dropped way down..... slowed further..... then fell even more, to
> approx. 2 or 3 f/sec.  Then the system crashed.

> 5.) Same sort of thing as in #4 happened at 'dega.

> In all cases the computer totally locked up.  I hit the Win key, tried to
> [Alt]+[Tab] back to Windows, then tried giving it the three finger salute
> many times, but there was *no* response from the system, and I had no
> recourse but to hit the power button, and then upon restart wait as scan
> disk is completed before I could get back to Windows.
> Unfortunately, I get no error message to help indicate what the problem is.

> Am I doing something wrong, or is N3 in need of a patch of some sort?

> My system:

> 64MB RAM
> 3Dfx Voodoo Banshee w/ 16MB
> Creative Sound Blaster AudioPCI 64D

> If anyone can help me figure out what's going on, it would be greatly
> appreciated, as its getting to the point that I'm afraid to run the game
> :-(

>Not the cars..... the game.
>Seems the littlest things cause serious problems.
>Examples:

>1.) In Paint Shop, I selected the magnifying tool, then changed my mind and
>clicked on it again, thinking this would de-select it.  Crashed.

>My system:

>64MB RAM
>3Dfx Voodoo Banshee w/ 16MB
>Creative Sound Blaster AudioPCI 64D

>If anyone can help me figure out what's going on, it would be greatly
>appreciated, as its getting to the point that I'm afraid to run the game
>:-(

>I have the same problem.  If I finish a qualifying run or just decide I
want
>to get out of the car, I hit escape and then it locks.  It happened before
>in Multi while the host was selecting a track, and happened in Multi when I
>finished a Qualifying run and got second :(.

>My system is:
>Celeron 333 (not overclocked)
>Diamond Monster Fusion 16mb Banshee PCI (not overclocked)
>96mb SyncDram
>A3d Sound Card

>========================
>Adam Zerlin
>GT Insider Webmaster
>http://www.racesimcentral.net/
>================================
>GT International Championship Organizer
>http://www.racesimcentral.net/***.com

>> Most crashes that I've heard about were due to overclocked systems,
>usually
>> the video card.

>> I was experimenting with my Asus V3800 non-ultra (which I rarely do - I'm
>> not much into overclocking) and if I pushed it too far, N3 got very
>> unstable.

>> If you are pushing things, you might want to experiment with putting them
>at
>> the factory defaults and see what happens.

>> -Larry

>> > Not the cars..... the game.
>> > Seems the littlest things cause serious problems.
>> > Examples:

>> > 1.) In Paint Shop, I selected the magnifying tool, then changed my mind
>> and
>> > clicked on it again, thinking this would de-select it.  Crashed.

>> > 2.) Again, in Paint shop, I had the rectangle tool selected, and after
>> > finishing what I wanted to change, went to the magnifier.  Crashed.

>> > 3.) Wrecked out of a race at Dover, hit escape and watched the replay.
>> > After I'd seen what I wanted I hit escape again, clicked no.....
>crashed.
>> > After trying to replicate this I found that (at least on my system and
a
>> > friend's) whenever the race is exited while a replay is running it
>causes
>> a
>> > crash.

>> > 4.) Major wreck happened in front of me at Bristol..... looked like it
>had
>> > to involve half the field  :-)
>> > I slowed down to about 60 mph and went high to drive around it, and all
>of
>> a
>> > sudden the frame rate (which is usually mid to high 20's, even during a
>> > wreck) dropped way down..... slowed further..... then fell even more,
to
>> > approx. 2 or 3 f/sec.  Then the system crashed.

>> > 5.) Same sort of thing as in #4 happened at 'dega.

>> > In all cases the computer totally locked up.  I hit the Win key, tried
>to
>> > [Alt]+[Tab] back to Windows, then tried giving it the three finger
>salute
>> > many times, but there was *no* response from the system, and I had no
>> > recourse but to hit the power button, and then upon restart wait as
scan
>> > disk is completed before I could get back to Windows.
>> > Unfortunately, I get no error message to help indicate what the problem
>> is.

>> > Am I doing something wrong, or is N3 in need of a patch of some sort?

>> > My system:

>> > 64MB RAM
>> > 3Dfx Voodoo Banshee w/ 16MB
>> > Creative Sound Blaster AudioPCI 64D

>> > If anyone can help me figure out what's going on, it would be greatly
>> > appreciated, as its getting to the point that I'm afraid to run the
game
>> > :-(

>I have the same problem.  If I finish a qualifying run or just decide I
want
>to get out of the car, I hit escape and then it locks.  It happened before
>in Multi while the host was selecting a track, and happened in Multi when I
>finished a Qualifying run and got second :(.

>My system is:
>Celeron 333 (not overclocked)
>Diamond Monster Fusion 16mb Banshee PCI (not overclocked)
>96mb SyncDram
>A3d Sound Card

>========================
>Adam Zerlin
>GT Insider Webmaster
>http://www.racesimcentral.net/
>================================
>GT International Championship Organizer
>http://www.racesimcentral.net/***.com

>> Most crashes that I've heard about were due to overclocked systems,
>usually
>> the video card.

>> I was experimenting with my Asus V3800 non-ultra (which I rarely do - I'm
>> not much into overclocking) and if I pushed it too far, N3 got very
>> unstable.

>> If you are pushing things, you might want to experiment with putting them
>at
>> the factory defaults and see what happens.

>> -Larry

>> > Not the cars..... the game.
>> > Seems the littlest things cause serious problems.
>> > Examples:

>> > 1.) In Paint Shop, I selected the magnifying tool, then changed my mind
>> and
>> > clicked on it again, thinking this would de-select it.  Crashed.

>> > 2.) Again, in Paint shop, I had the rectangle tool selected, and after
>> > finishing what I wanted to change, went to the magnifier.  Crashed.

>> > 3.) Wrecked out of a race at Dover, hit escape and watched the replay.
>> > After I'd seen what I wanted I hit escape again, clicked no.....
>crashed.
>> > After trying to replicate this I found that (at least on my system and
a
>> > friend's) whenever the race is exited while a replay is running it
>causes
>> a
>> > crash.

>> > 4.) Major wreck happened in front of me at Bristol..... looked like it
>had
>> > to involve half the field  :-)
>> > I slowed down to about 60 mph and went high to drive around it, and all
>of
>> a
>> > sudden the frame rate (which is usually mid to high 20's, even during a
>> > wreck) dropped way down..... slowed further..... then fell even more,
to
>> > approx. 2 or 3 f/sec.  Then the system crashed.

>> > 5.) Same sort of thing as in #4 happened at 'dega.

>> > In all cases the computer totally locked up.  I hit the Win key, tried
>to
>> > [Alt]+[Tab] back to Windows, then tried giving it the three finger
>salute
>> > many times, but there was *no* response from the system, and I had no
>> > recourse but to hit the power button, and then upon restart wait as
scan
>> > disk is completed before I could get back to Windows.
>> > Unfortunately, I get no error message to help indicate what the problem
>> is.

>> > Am I doing something wrong, or is N3 in need of a patch of some sort?

>> > My system:

>> > 64MB RAM
>> > 3Dfx Voodoo Banshee w/ 16MB
>> > Creative Sound Blaster AudioPCI 64D

>> > If anyone can help me figure out what's going on, it would be greatly
>> > appreciated, as its getting to the point that I'm afraid to run the
game
>> > :-(

>Well since the original poster also has a banshee card, maybe
>N3 has a problem with those???

>Are you guys using the latest 3dfx drivers and Direct X 6.1?

>>Not the cars..... the game.
>>Seems the littlest things cause serious problems.
>>3.) Wrecked out of a race at Dover, hit escape and watched the replay.
>>After I'd seen what I wanted I hit escape again, clicked no..... crashed.
>>After trying to replicate this I found that (at least on my system and a
>>friend's) whenever the race is exited while a replay is running it causes a
>>crash.
>I've watched a few replays (to see what idiot crashed into me) and
>never saw this problem.

>On Tue, 21 Sep 1999 07:03:29 -0500, "Greg Cisko"

>>Well since the original poster also has a banshee card, maybe
>>N3 has a problem with those???

>>Are you guys using the latest 3dfx drivers and Direct X 6.1?

>Monster II 12 meg and an AGP 16 meg with the latest drivers and mine
>crashes like crazy.

>>On Tue, 21 Sep 1999 07:03:29 -0500, "Greg Cisko"

>>>Well since the original poster also has a banshee card, maybe
>>>N3 has a problem with those???

>>>Are you guys using the latest 3dfx drivers and Direct X 6.1?

>>Monster II 12 meg and an AGP 16 meg with the latest drivers and mine
>>crashes like crazy.

>Huh, I just ran 10% races at Richmond, Darlington, Martinsville & Las
>Vegas. Each time I started in the rear and worked my way forward.
>Not one crash. Ever...

> Check the N3 readme file.... I believe I read in there that N3 has
> some issues with Banshee cards?  I don't have N3 at work so I can't
> confirm for sure.

> Dave Ericson
> MomoBoy online
> JDB Racing

>> Not the cars..... the game.
>> Seems the littlest things cause serious problems.
>> Examples:

>> 1.) In Paint Shop, I selected the magnifying tool, then changed my
>> mind and
>> clicked on it again, thinking this would de-select it.  Crashed.

>> 2.) Again, in Paint shop, I had the rectangle tool selected, and
>> after
>> finishing what I wanted to change, went to the magnifier.  Crashed.

>> 3.) Wrecked out of a race at Dover, hit escape and watched the
>> replay.
>> After I'd seen what I wanted I hit escape again, clicked no.....
>> crashed.
>> After trying to replicate this I found that (at least on my system
>> and a
>> friend's) whenever the race is exited while a replay is running it
>> causes a
>> crash.

>> 4.) Major wreck happened in front of me at Bristol..... looked like
>> it had
>> to involve half the field  :-)
>> I slowed down to about 60 mph and went high to drive around it, and
>> all of a
>> sudden the frame rate (which is usually mid to high 20's, even
>> during a
>> wreck) dropped way down..... slowed further..... then fell even
>> more, to
>> approx. 2 or 3 f/sec.  Then the system crashed.

>> 5.) Same sort of thing as in #4 happened at 'dega.

>> In all cases the computer totally locked up.  I hit the Win key,
>> tried to
>> [Alt]+[Tab] back to Windows, then tried giving it the three finger
>> salute
>> many times, but there was *no* response from the system, and I had
>> no
>> recourse but to hit the power button, and then upon restart wait as
>> scan
>> disk is completed before I could get back to Windows.
>> Unfortunately, I get no error message to help indicate what the
>> problem is.

>> Am I doing something wrong, or is N3 in need of a patch of some
>> sort?

>> My system:

>> 64MB RAM
>> 3Dfx Voodoo Banshee w/ 16MB
>> Creative Sound Blaster AudioPCI 64D

>> If anyone can help me figure out what's going on, it would be
>> greatly
>> appreciated, as its getting to the point that I'm afraid to run the
>> game
>> :-(

>>Huh, I just ran 10% races at Richmond, Darlington, Martinsville & Las
>>Vegas. Each time I started in the rear and worked my way forward.
>>Not one crash. Ever...

>The computer crashes, not the car/driver.