OOTP Developments Forums - View Single Post

theDutchman · 03-13-2002, 10:03 PM

[quote]This could be because it doesn't seem to be effecting some PC's... so its still unclear if this is an OOTP problem or a PC problem... or some combination thereof. A member of the development team posted in this thread and mentioned that his CPU was only at 68% while running the game...<hr></blockquote>

1. If it were a PC problem, it would do this while running other software, it doesn't.

2. Chances are, the guy running at 68% did not actually look at current CPU usage but at what percent of his resources were free. If I am not mistaken, resources free deals with RAM and generally implies that you have quite a bit of programs running at startup. It seems like a CPU hog, but it's actually a RAM bottleneck.

I am certain that a lack of response from the development team is because they aren't sure what to do at this point. It could be disasterous if they said they were working on the problem and then couldn't find a solution. So chances are they are looking into it but just aren't mentioning it.

Give them some time, they seem like a very dedicated bunch that won't leave any stones unturned. At least that is my impression.

03-13-2002, 10:03 PM	#72
theDutchman Bat Boy Join Date: Jan 2002 Posts: 17	[quote]This could be because it doesn't seem to be effecting some PC's... so its still unclear if this is an OOTP problem or a PC problem... or some combination thereof. A member of the development team posted in this thread and mentioned that his CPU was only at 68% while running the game...<hr></blockquote> 1. If it were a PC problem, it would do this while running other software, it doesn't. 2. Chances are, the guy running at 68% did not actually look at current CPU usage but at what percent of his resources were free. If I am not mistaken, resources free deals with RAM and generally implies that you have quite a bit of programs running at startup. It seems like a CPU hog, but it's actually a RAM bottleneck. I am certain that a lack of response from the development team is because they aren't sure what to do at this point. It could be disasterous if they said they were working on the problem and then couldn't find a solution. So chances are they are looking into it but just aren't mentioning it. Give them some time, they seem like a very dedicated bunch that won't leave any stones unturned. At least that is my impression.