Tomb Raider: AOD DX9 Benchmarks

[Reverend]

Is there any chance you release some kind of "public" demo, so we can compare the results, reserving your testing demo unrevealed,so someone could not cheat in the drivers..?

At the moment, no. Beyond3D has an exclusive version of the EXE which is not available to the public yet. As soon as EA (who is responcible for releasing patches to the public) get around to releasing it then we should have all of the tools we need to make our own demos. Of course, you will have to purchase the game as per usual.

My bolds. It's Eidos, not EA.

 

[Sage]

oops... yeah, my short term memory is quickly fading in my old age (turned 19 yesterday, eek) and all I rememberd was the "E"

 

[Joe DeFuria]

Apparently, the v49 patch has been released:

http://www.eidosinteractive.co.uk/support/patchinfo.html?ptid=67

 

[Dave Baumann]

Well, the results from this version appear to correlate with our beta patch, so it would seem that this is the official version of that patch.

 

[Reverend]

Man, the patch's readme is kinda confusing/hard to understand at first glance... it surely is much less verbose than our readme.rtf !! I sure hope I won't be flooded with requests for clarification.

For those of you attempting to record your own demo for benchmarking, it is important :

1) to get the shortcut described in the patch's readme absolutely correct. Especially the "Start in/working directory" field (i.e. make sure it points to the game's root folder, and not the \bin\ subfolder... this is a common mistake)

2) Once you're done recording, use ALT-F4 to quit the game directly... don't negotiate the menus to quit the game, because doing so would have the benchmark tabulate the framerates during menu negotiation as well (and the framerates during menu negotiation are in the hundreds of fps, which will bump up the benchmark average fps)

Debugging keys is mentioned in the patch. I think I'll be nasty and let you guys find out for yourself what the debug keys are and what they do/mean, hehe

Nice to see the B3D acknowledgement in the patch readme though

 

[Reverend]

Well, the results from this version appear to correlate with our beta patch, so it would seem that this is the official version of that patch.

I haven't tested this official patch and compared it to the private v49 build we have but I think there are two additional stuff in the official patch that aren't in the private build, namely :

1) "Glow" effect is totally disabled/won't work even if enabled
2) The "St. Aicard Graveyard" level has the grass renderer totally disabled... it's a real pixel fillrate/bandwidth killer due to the multiple alpha blended and alpha tested levels to render the grass.

 

[digitalwanderer]

Man, the patch's readme is kinda confusing/hard to understand at first glance... it surely is much less verbose than our readme.rtf !! I sure hope I won't be flooded with requests for clarification.

For those of you attempting to record your own demo for benchmarking, it is important :

1) to get the shortcut described in the patch's readme absolutely correct. Especially the "Start in/working directory" field (i.e. make sure it points to the game's root folder, and not the \bin\ subfolder... this is a common mistake)

2) Once you're done recording, use ALT-F4 to quit the game directly... don't negotiate the menus to quit the game, because doing so would have the benchmark tabulate the framerates during menu negotiation as well (and the framerates during menu negotiation are in the hundreds of fps, which will bump up the benchmark average fps)

Debugging keys is mentioned in the patch. I think I'll be nasty and let you guys find out for yourself what the debug keys are and what they do/mean, hehe

Nice to see the B3D acknowledgement in the patch readme though

Thanks Reverend, the clarification/explanation is much appreciated.