My first CTD, not"A" key related

Avatar · 04-20-07, 01:33 PM

Hello,
I have installed v1.2 and everythings ok.
I went to main.cfg and changed the Dev. options to "No."
I went to my graphics card GPU and changed the Hz to 75Hz.
I was playing against a large convoy, one that had about 10 ships(DD's included).
It was at night, visability nil, and in rain. My crew couldnt even see a ship that was very close, thats how dark it was.
I was experiencing considerable loss of frame rate, I guess due to the rain, ships, etc., when looking at the convoy. This is strange because before I had no problem with convoys and frame rate.
I have a geforce 6800ultra
Play on medium settings
Have a Pent. 4 HT 3.6 GHz
Anyway, A CTD happened after I sank 3 ships in the convoy.
I went back to my original settings, changed the Dev options to "Yes" but didnt change the Hz. and I have not experienced a CTD. Well, I havent come across any big convoys yet.

Finally, my questions:
1. Does changing the Dev options have any effect on gameplay?
2. Do you think that with a 6800 I could have inadvertantly cause the CTD with changing my Hz?

The only other CTD was by pressing "a" before patch 1.2 came out. Now "a" works fine.
Thanks for any help.

AVGWarhawk · 04-20-07, 01:41 PM

Quote:

Finally, my questions:
1. Does changing the Dev options have any effect on gameplay?
2. Do you think that with a 6800 I could have inadvertantly cause the CTD with changing my Hz?

1. Do not know but some say it helps with stutters. I have not touched mine. I experienced a CTD much the same. High demand on the computer. I just cleaned up the computer and replayed the senerio. No CTD. Played 4 hours straight, no CTD.

2. I changed my Hz last night to 75Hz. No issues or CTD.

I just think the large demand did you in and it was just a bad luck CTD. I say clean up rig(defrag etc). When you get into the heavy situations like that, keep the bouncing around with the camera and screens at a minimum. I know I have a habit of clicking inside/outside paning around etc.

Avatar · 04-20-07, 01:44 PM

Thanks for the quick reply!
I'll do that tonight, and I may look into freeing up some space for the "thinking" part of the computer. CTRL+ALT+DEL and look what processes are doing what.
thanks again.

jdski · 04-20-07, 08:15 PM

I've had a few CTD unrelated to the "A" problem too. I was clicking mouse buttons after comming out of TC I believe. One taught me to save more frequently.

AVGWarhawk · 04-20-07, 08:19 PM

What I find the best to do when clicking up a screen or coming out of TC. Give the computer a few seconds before you start pressing other keys and commands. For instance, I hit F5 to get to the bridge. Page comes up quickly, I give a second or two then start using the binocs, TBT or just scanning the horizon smelling the salt air.

04-20-07, 01:33 PM	#1
Avatar Commodore Join Date: Sep 2002 Location: Way out there Posts: 603 Downloads: 24 Uploads: 0	My first CTD, not"A" key related Hello, I have installed v1.2 and everythings ok. I went to main.cfg and changed the Dev. options to "No." I went to my graphics card GPU and changed the Hz to 75Hz. I was playing against a large convoy, one that had about 10 ships(DD's included). It was at night, visability nil, and in rain. My crew couldnt even see a ship that was very close, thats how dark it was. I was experiencing considerable loss of frame rate, I guess due to the rain, ships, etc., when looking at the convoy. This is strange because before I had no problem with convoys and frame rate. I have a geforce 6800ultra Play on medium settings Have a Pent. 4 HT 3.6 GHz Anyway, A CTD happened after I sank 3 ships in the convoy. I went back to my original settings, changed the Dev options to "Yes" but didnt change the Hz. and I have not experienced a CTD. Well, I havent come across any big convoys yet. Finally, my questions: 1. Does changing the Dev options have any effect on gameplay? 2. Do you think that with a 6800 I could have inadvertantly cause the CTD with changing my Hz? The only other CTD was by pressing "a" before patch 1.2 came out. Now "a" works fine. Thanks for any help.

04-20-07, 08:19 PM	#5
AVGWarhawk Lucky Jack Join Date: Jun 2005 Location: In a 1954 Buick. Posts: 28,253 Downloads: 90 Uploads: 0	What I find the best to do when clicking up a screen or coming out of TC. Give the computer a few seconds before you start pressing other keys and commands. For instance, I hit F5 to get to the bridge. Page comes up quickly, I give a second or two then start using the binocs, TBT or just scanning the horizon smelling the salt air. __________________ “You're painfully alive in a drugged and dying culture.” ― Richard Yates, Revolutionary Road

04-20-07, 01:44 PM	#3
Avatar Commodore Join Date: Sep 2002 Location: Way out there Posts: 603 Downloads: 24 Uploads: 0	Thanks for the quick reply! I'll do that tonight, and I may look into freeing up some space for the "thinking" part of the computer. CTRL+ALT+DEL and look what processes are doing what. thanks again.

04-20-07, 08:15 PM	#4
jdski Gunner Join Date: Apr 2005 Posts: 95 Downloads: 8 Uploads: 0	I've had a few CTD unrelated to the "A" problem too. I was clicking mouse buttons after comming out of TC I believe. One taught me to save more frequently.