If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I was right. I used the registry hack to turn off VSync. I can tell it's off, because there is some screen tearing in the one or two fast spots.
Anyway, for Quake3 1.08, demo 1, my scores are unchanged:
24.2fps with 5.15, 13.8fps with 5.21
All the settings are the same - I know they are, since all I did was swap out the ICD file (fresh install of 5.21 onto a fresh install of Win98 gave me 13.8, drop in the 5.15 icd and get 24.2).
So Ant, please - explain it to me. I'm not being mean, I just am curious as to how you propose to get this back up to speed!
- Gurm
------------------
G. U. R. M. It's not hard to spell, is it? Then don't screw it up!
The word "Gurm" is in no way Copyright 1999 Jorden van der Elst.
The Internet - where men are men, women are men, and teenage girls are FBI agents!
I'm the least you could do
If only life were as easy as you
I'm the least you could do, oh yeah
If only life were as easy as you
I would still get screwed
Don't patronize me. I know it came disabled... I turned it on.
- Gurm
The Internet - where men are men, women are men, and teenage girls are FBI agents!
I'm the least you could do
If only life were as easy as you
I'm the least you could do, oh yeah
If only life were as easy as you
I would still get screwed
no patronizing going on here. VSYNC on or off affected only D3D, not OpenGL. No matter what you did, vsync only worked in D3D. Sorry, but that is the way it is. So, in effect, you will see no perf. drop in D3D with the new drivers, but will see a drop in OpenGL, since you want vsync enabled.
Rags
------------------
That's your wife on the back of my horse!!
The hacks are, from the look of things, for D3D. Ok, fine.
How then, pray tell, do I disable VSync in OpenGL? I figured turning it off in the Quake3 config menu did the trick, perhaps I'm wrong?
- Gurm
P.S. And then why in God's name is Ant proposing the D3D registry hack to fix Quake 2 & 3, both of which are OpenGL only?
------------------
G. U. R. M. It's not hard to spell, is it? Then don't screw it up!
The word "Gurm" is in no way Copyright 1999 Jorden van der Elst.
[This message has been edited by Gurm (edited 09-03-1999).]
The Internet - where men are men, women are men, and teenage girls are FBI agents!
I'm the least you could do
If only life were as easy as you
I'm the least you could do, oh yeah
If only life were as easy as you
I would still get screwed
In earlier drivers, vsynch was always disabled in OGL. There was no way to affect the vsynch in OGL. Period. The reg hack at that time would only affect D3D.
Now, with 5.21, vsynch can be enabled/disabled in OGL AND D3D. The same reg hack NOW affects both.
Core2 Duo E7500 2.93, Asus P5Q Pro Turbo, 4gig 1066 DDR2, 1gig Asus ENGTS250, SB X-Fi Gamer ,WD Caviar Black 1tb, Plextor PX-880SA, Dual Samsung 2494s
The reg hack had no effect on the drivers pre-PD 5.2x in OpenGL, because the Vsync was always disabled in OpenGL, no matter what anyone tried. Now, vsync is working in the new 5.2 drivers. So, you will see a difference in performance in BOTH D3D and OpenGL when disabling/enabling it, rather than just D3D with the "old" drivers.
Rags
------------------
That's your wife on the back of my horse!!
Gurm is 100% right! The demo1 DOES drop a lot! In fact I got just like him a drop from 25.7 to 13.8fps! The slowdown can be seen in the open scene where there are lots of jumps. It literally crawls there!
That's all at 1024x768x32bit with everything on (trilinear, highest texture details, 32bit textures).
I did apply RegHack for disabling VSync. With VSync on it was 12.6 without it 13.8 (as I said). That is far cry from 25.7 I get with 5.13.
Strangely, demo2 got better. Went up from 26.4 to 27.0 in both VSync on and off... go figure.
r_swapinterval 0 or 1 produce EXACTLY the same results. deleting .cfg file as Haig suggested and setting the settings again doesn't change a thing.
The only good thing about 5.21 is that Rogue Squadron now works. Great job on that one! At 1280x1024 it rocks. I wish I could select 1600x1200...
BUT System Shock 2 is now broken! In the room where you choose between advanced and basic training the doors to the holos are screwed and you see some weird textures moving on them. It's perfectly fine with 5.13.
I didn't check Q2 - it might give 100fps for all I care - it's an old and stupid game with shitty graphics.
I'd summarize that DX compatibility improved, while OGL got worse, rather drastically.
Michael
P.S. Before I'll be declared incompetent, the reg hack was applied to 0000. I opened the .reg file in ASCII before applying it and followed to where it was adding the info. I checked - the info is there. The 5.13 drivers were first COMPLETELY uninstalled using _Matrox_ utility and then the 5.21 were installed. And since I'm getting what others are getting (same FPS precisely) we are NOT making this stuff up! Why would we???
------------------
P2c-300a/450, 192MB PC125 SDRAM, Quantum Fireball Plus KA 18.2GB 7200rpm, Panasonic 7502B x4/x8 Ultra SCSI CD-R, Tekram DC-390U2W Ultra2Wide SCSI controller, Diamond MX300 (Vortex2), Creative Labs AWE64 Gold Sound Blaster, A-Trend Voodoo II 12MB, Matrox Millennium G400Max, 19" Hitachi SuperScan 752 and some other fancy stuff
P2c-300a/450, 256MB PC125 SDRAM, Quantum Fireball Plus KA 18.2GB 7200rpm, Panasonic 7502B x4/x8 Ultra SCSI CD-R, Tekram DC-390U2W Ultra2Wide SCSI controller, Diamond MX300 (Vortex2), Matrox Millennium G400Max, 19" Hitachi SuperScan 752, Logitech Cordless MouseMan Wheel and some other fancy stuff
does the mgatweak work for disabling the v-sync.if it does then i have no speed increase
so basically what are you guys saying you gained from old version(v-sync broken and off all the time) to this version(with v-sync turned off)
if you care about the other question just answer about the mga tweak
My only comment here is this: WHY SHOULD IT BE THIS DIFFICULT?? Even Ant was stumped at first, so don't tell me that every kid who plays with computers should be able to hack this problem with ease.
Haig: Just explain it clearly and put it in the control panel, please. No one should have to hack their registry or any of this other gobbledygook to turn vsync on and off, or to get their video card to perform as designed.
Now, if some people are turning vsync off but getting the same results, how do we explain this?
An easy way to enable/disable vsync and other options is to install Byron Montgomeri's g400tweak utility. Get it here ftp://ftp.cdrom.com/pub/3dfiles/utility/g400tweak.zip or http://ftp.telepac.pt/pub/3dfiles/utility/g400tweak.zip
What about playing with the refresh rate of your monitor? If your quake gives you, say, 75 fps on average, the optimal refesh rate should be 75 Hz, or a clean multiple of 75. This should allow you to approximate the game's full performance, with vsync on and thus without the tearing. Triple buffering should also be enabled, since with a second frame in store the refresh-frame-rate timing is not as critical as with only one. (Refer to http://www.entechtaiwan.com for more details.)
I havn't tried this for OpenGL (I do not use it, I do not play quake), but it should work according to all theory. In D3D, that I know, the rate of frames that actually appear on your screen can be much improved by setting the optimal monitor refresh rate - of course with vsync ON.
BTW: With the (D3D) games I play there's a performace gain of up to 15% with the 5.21 drivers, as compared to 5.15.
Comment