Some readables kill framerate?

[Weasel]

Apologies if this has already been discussed. I did a quick search and didn't turn up anything.

It seems like certain readable items are causing a huge drain on my framerate whenever they're in view. I don't mean the version that comes up when I've frobbed them to read, but the object in the world when they're visible anywhere on my screen. It seems like there's at least one in every mission I've played, while the majority of them are fine.

 

Outpost is the mission in which I actually managed to narrow down the issue to a readable. The note on the desk in the Bishop's room causes massive slowdown, even with the candle taken away and with bloom turned off. If I stand on the desk, my framerate is fine in all directions except looking straight down. If I crouch in front of the desk, my framerate is fine in all directions until I stand up. If I look at just the chair, just the corner table, just the banner, etc., my framerate is fine.

 

In the training mission, I encounter the same thing when I look at the book on the pedestal in the center.

 

 

In the Saint Lucia demo, was there a readable in the basement? I remember a framerate issue in one particular spot, but I didn't figure out what the cause was there. I can go back and check if need be.

 

I haven't played Chalice or Crown yet, but I can report on those once I have played them.

[Mortem Desino]

Huh. That's extremely peculiar. And you mean to say that no other readables in that FM cause slowdowns? I may have to take a look at that particular model and/or guicode.

 

What is in your PC rig? (I'm particularly interested in graphics card, CPU, RAM, and OS)

[Weasel]

Huh. That's extremely peculiar. And you mean to say that no other readables in that FM cause slowdowns? I may have to take a look at that particular model and/or guicode.

 

What is in your PC rig? (I'm particularly interested in graphics card, CPU, RAM, and OS)

 

Actually, there may have been other readables that did cause slowdown. I just know that many of them did not. I think the training mission may have had others that caused it, actually. I'll have to test it again and get back to you. I'll get back to you on the specs of my rig as well (I'm not near it at the moment).

Edited October 28, 2009 by Weasel

[LeatherMan]

Actually, there may have been other readables that did cause slowdown. I just know that many of them did not. I think the training mission may have had others that caused it, actually. I'll have to test it again and get back to you. I'll get back to you on the specs of my rig as well (I'm not near it at the moment).

 

/me awaits specs, fully expecting ATI gpu...

 

 

FWIW, I tested Outpost last night, and looking across the room from the readable was slightly lower than looking down at the readable (as expected), so it isn't a problem with the readables or TDM. Have you edited the config manually by chance? If so, what did you change?

 

 

[Weasel]

/me awaits specs, fully expecting ATI gpu...

 

 

FWIW, I tested Outpost last night, and looking across the room from the readable was slightly lower than looking down at the readable (as expected), so it isn't a problem with the readables or TDM. Have you edited the config manually by chance? If so, what did you change?

 

 

 

Sorry to disappoint you, but it's not an ATI gpu.

 

I realized I could get the specs from an old email, so here they are:

 

Windows XP Pro

Intel Core 2 Quad-Core Q6600 (8MB L2 cache,2.40GHz,1066FSB)

3 GB DDR2 SDRAM 800MHz (4 DIMMs)

768MB nVidia GeForce 8800 GTX

 

Assuming things I did with the St. Lucia demo don't carry over (I don't remember any more, but I don't think I changed much), I did not edit the config. I downloaded version 1.00 on Monday and once everything was loaded, I went straight in, adjusted in-game settings, and played the training mission. On Tuesday night (last night) I installed Outpost and played that.

[LeatherMan]

Sorry to disappoint you, but it's not an ATI gpu.

 

I realized I could get the specs from an old email, so here they are:

 

Windows XP Pro

Intel Core 2 Quad-Core Q6600 (8MB L2 cache,2.40GHz,1066FSB)

3 GB DDR2 SDRAM 800MHz (4 DIMMs)

768MB nVidia GeForce 8800 GTX

 

Assuming things I did with the St. Lucia demo don't carry over (I don't remember any more, but I don't think I changed much), I did not edit the config. I downloaded version 1.00 on Monday and once everything was loaded, I went straight in, adjusted in-game settings, and played the training mission. On Tuesday night (last night) I installed Outpost and played that.

 

Wasn't expecting Nvidia, that's for sure. For the record, there are a few systems running a Geforce 8 on XP without this problem. 

 

What Nvidia drivers do you have installed? Can you install the latest Nvidia drivers? Do you have any Doom 3 mods (3doom, parallax, etc) installed? Have you set Doom 3 to Ultra settings (someone suggested it may cause problems, but I'm not sure)? 

[Serpentine]

Do you have any AA or AF enabled? if so, try disabling etc and make sure they are not forced in the nvidia control panel.

[Weasel]

Wasn't expecting Nvidia, that's for sure. For the record, there are a few systems running a Geforce 8 on XP without this problem. 

 

What Nvidia drivers do you have installed? Can you install the latest Nvidia drivers? Do you have any Doom 3 mods (3doom, parallax, etc) installed? Have you set Doom 3 to Ultra settings (someone suggested it may cause problems, but I'm not sure)? 

 

Well, that was too easy. I installed the latest drivers and the problem went away. The thing runs like a dream now. I may have to try bumping up the anti-aliasing or something to get the choppiness back. :-P