You should rather use the original ref_gl.dll with K6-2 in case you want to benefit from the performance increase achieved by disabling dynamic lighting and don't want to have the stupid effect of flash blend.
QUAKE II FRAME RATE DROP DRIVER
It just ignores this command and you won't get the performance increase unless you enable flash blend (gl_flashblend 1), which for some reason does finally switch off dynamic lighting in the default OpenGL 3DNow! driver ver. Asyncronous FPS will reduce outgoing bandwidth/packet rate at the expense of altering how certain aspects of the physics. The ref_glam.dll would not let you disable dynamic lighting (gl_dynamic 0). Now 3Dnow! is enabled each time you either run a 3Dfx card with the 3Dfx OpenGL driver or e.g.
QUAKE II FRAME RATE DROP DRIVERS
Simply copy the file 3dfxglam.dll as 3dfxgl.dll and ref_glam.dll as ref_gl.dll into the Quake 2 base directory, replacing the original drivers (rename them to keep them). To run Q2 3.19 with 3Dnow! enabled you don't have to do much at all. I tried finding a way around that, because I wanted to benchmark all CPUs with the same Q2 version. Now what we really want to know is how far can we go up with the resolution whilst keeping a good result in crusher.dm2. I claim that you can run Q2 just fine as long as your 'crusher.dm2' result is above 25 fps.
Using 'crusher.dm2' shows how bad the frame rate can get. You will hardly ever be in a death match with so many rockets, hyperblaster, BFG and Railgun shots flying around you, or if you should, you may not stay alive for long. 'Crusher' can be seen as the worst case scenario in Quake2. The CPU rather than the 3D card do the transform and lighting and 'crusher' is asking for the last bit of CPU performance. I never used this demo so far, because in reality it's a perfect CPU benchmark. He had the idea of putting 3D cards through tougher tests by recording a demo with a huge amount of explosions and light weapons, so he recorded 'crusher.dm2'. Now unfortunately Q2 tells us only the average frame rate from a benchmarking demo, no maximum, no minimum. As long as this is above a decent level, we don't have to worry anymore. You may remember what I said in the introduction, we shouldn't care less about 'average frame rate', we want to know the worst case scenario of a 3D card. Then there are the two larger demos recorded from the Q2 benchmarking Guru Brett '3 Fingers' Jacobs, which are 'massive1.dm2' and 'crusher.dm2'. There is the pretty useless built in 'demo1.dm2' or 'demo2.dm2', or some more demos included into 'Reckoning', the Q2 mission CD.
The different fps values that people are talking about come from different benchmarking demos for Q2. A sustained frame rate of 25-30 fps would actually do, it may never ever drop below 25 though, because that would cause game play restrictions.
.jpg "quake ii frame rate drop")
What is acceptable? Many Q2 players will answer '40-50+ fps is what it takes'. It is advisable to play at the highest screen resolution you can get, as long as the frame rate is acceptable. I don't see any reason for playing Quake2 at 640x480 anymore since the days of Voodoo2 and TNT.
0 kommentar(er)
