N4: Just got it. CTD and freezing. Any suggestions?

Hi, I am playing it in 32-bit color at 1024x768. My desktop is set at 1280x1024 in 32-bit color at the max refresh rate for my monitor (75mhz). It looks gorgeous and runs extremely smooth. But I have only tried it twice - both on Daytona. 1st time, it crashed to the desktop. I realized that I had my desktop set at 16-bit, and the game at 32 so I chalked the crash up to that and changed my desktop to 32. Restarted Daytona and got further - but this time it froze, with the sound of the engine running. Had to reboot. I thought my system was pretty stable. Are there some things I should try to get it to just run without a problem? I have a friend coming over tonight who can't wait to see N4 and I don't want him to see my system crashing all the time with it <g> System specs: Athlon 700 256MB RAM (although the original is 128 PC-100, and then I added another 128 of PC-133 from Crucial a few months ago) Hercules GeForce Prophet 2 GTS Pro (64meg DDR) with Hercules 6.35 drivers Direct X 8.0a Win98SE All CH Stick, throttle, pedals (not using those). Shoot - I know I am forgetting some spec as usual :-) Thanks, -paul

Knew it! Playing it in D3D at standard options. -pw

Quoted text (33 lines)

> >I am playing it in 32-bit color at 1024x768. My desktop is set at >1280x1024 in 32-bit color at the max refresh rate for my monitor >(75mhz). > >It looks gorgeous and runs extremely smooth. But I have only tried it >twice - both on Daytona. 1st time, it crashed to the desktop. I >realized that I had my desktop set at 16-bit, and the game at 32 so I >chalked the crash up to that and changed my desktop to 32. Restarted >Daytona and got further - but this time it froze, with the sound of >the engine running. Had to reboot. > >I thought my system was pretty stable. Are there some things I should >try to get it to just run without a problem? I have a friend coming >over tonight who can't wait to see N4 and I don't want him to see my >system crashing all the time with it <g> > >System specs: > >Athlon 700 >256MB RAM (although the original is 128 PC-100, and then I added >another 128 of PC-133 from Crucial a few months ago) >Hercules GeForce Prophet 2 GTS Pro (64meg DDR) with Hercules 6.35 >drivers >Direct X 8.0a >Win98SE >All CH Stick, throttle, pedals (not using those). > >Shoot - I know I am forgetting some spec as usual :-) > >Thanks, > >-paul

With the Geforce you should probably be using 16-bit OpenGL for best performance, but if you want to use D3D make sure to select the (TnL HAL) labeled device. You'll also want to be sure that you're using the latest drivers for everthing in your system, including your motherboard BIOS and AGP chipset drivers. Check www.geforcefaq.com for other tips to optimize your system and prevent freezes and crashes in games. Eric "pw" <[email hidden]> wrote in message news:989vqb$uq4$[email hidden]...

Quoted text (11 lines)

> It looks gorgeous and runs extremely smooth. But I have only tried it > twice - both on Daytona. 1st time, it crashed to the desktop. I > realized that I had my desktop set at 16-bit, and the game at 32 so I > chalked the crash up to that and changed my desktop to 32. Restarted > Daytona and got further - but this time it froze, with the sound of > the engine running. Had to reboot. > > I thought my system was pretty stable. Are there some things I should > try to get it to just run without a problem? I have a friend coming > over tonight who can't wait to see N4 and I don't want him to see my > system crashing all the time with it <g>

My system just froze when it loaded your post!!! Use 16-bit for both unless you have a monster of a system. Marc. "pw" <[email hidden]> wrote in message news:989vqb$uq4$[email hidden]...

Quoted text (35 lines)

> Hi, > > I am playing it in 32-bit color at 1024x768. My desktop is set at > 1280x1024 in 32-bit color at the max refresh rate for my monitor > (75mhz). > > It looks gorgeous and runs extremely smooth. But I have only tried it > twice - both on Daytona. 1st time, it crashed to the desktop. I > realized that I had my desktop set at 16-bit, and the game at 32 so I > chalked the crash up to that and changed my desktop to 32. Restarted > Daytona and got further - but this time it froze, with the sound of > the engine running. Had to reboot. > > I thought my system was pretty stable. Are there some things I should > try to get it to just run without a problem? I have a friend coming > over tonight who can't wait to see N4 and I don't want him to see my > system crashing all the time with it <g> > > System specs: > > Athlon 700 > 256MB RAM (although the original is 128 PC-100, and then I added > another 128 of PC-133 from Crucial a few months ago) > Hercules GeForce Prophet 2 GTS Pro (64meg DDR) with Hercules 6.35 > drivers > Direct X 8.0a > Win98SE > All CH Stick, throttle, pedals (not using those). > > Shoot - I know I am forgetting some spec as usual :-) > > Thanks, > > -paul >

Quoted text (8 lines)

>With the Geforce you should probably be using 16-bit OpenGL for best >performance, but if you want to use D3D make sure to select the (TnL HAL) >labeled device. You'll also want to be sure that you're using the latest >drivers for everthing in your system, including your motherboard BIOS and >AGP chipset drivers. Check www.geforcefaq.com for other tips to optimize >your system and prevent freezes and crashes in games. > >Eric

Okay will try 16-bit OpenGL. It is just so beautiful and fluid in 32-bit D3D. Will also look for that TnL HAL option (it's in the game, right?). I think there is something up with the Daytona track and my system. I tried the Martinsdale track for about a half-hour last night after the freeze ups and CTDs from Daytona. Not a single lock-up or crash! I always keep my drivers up to date. Thanks Eric, -paul

Quoted text (16 lines)

> > >"pw" <[email hidden]> wrote in message >news:989vqb$uq4$[email hidden]... >> It looks gorgeous and runs extremely smooth. But I have only tried it >> twice - both on Daytona. 1st time, it crashed to the desktop. I >> realized that I had my desktop set at 16-bit, and the game at 32 so I >> chalked the crash up to that and changed my desktop to 32. Restarted >> Daytona and got further - but this time it froze, with the sound of >> the engine running. Had to reboot. >> >> I thought my system was pretty stable. Are there some things I should >> try to get it to just run without a problem? I have a friend coming >> over tonight who can't wait to see N4 and I don't want him to see my >> system crashing all the time with it <g> >

"pw" <[email hidden]> wrote in message news:98b298$uga$[email hidden]...

Quoted text (14 lines)

> > >With the Geforce you should probably be using 16-bit OpenGL for best > >performance, but if you want to use D3D make sure to select the (TnL HAL) > >labeled device. You'll also want to be sure that you're using the latest > >drivers for everthing in your system, including your motherboard BIOS and > >AGP chipset drivers. Check www.geforcefaq.com for other tips to optimize > >your system and prevent freezes and crashes in games. > > > >Eric > > Okay will try 16-bit OpenGL. It is just so beautiful and fluid in > 32-bit D3D. Will also look for that TnL HAL option (it's in the game, > right?). >

No outside the game actually in the 3dsetup menu option. In the pulldown menu box. dh

i was getting ctds pretty quick but i kicked my cas latency up from 2 to 3 and that cleared it up. (works at 2 in quake3 go figure) chris

On Sat, 10 Mar 2001 00:30:28 GMT, [email hidden] wrote: >i was getting ctds pretty quick but i kicked my cas latency up from 2 >to 3 and that cleared it up. (works at 2 in quake3 go figure) > >chris How would I do that? -pw