VOGONS


Reply 20 of 31, by user33331

User metadata
Rank Member
Rank
Member

Hmmm... I remember Voodoo 3-3000 was a cheap mid range graphic card back then.
I too think the first Geforce 256 and TNT 2 are faster.
When all graphics are cranked up and using fast movements Voodoo 3 starts to hickup on 1999+ games.

Reply 22 of 31, by dr.zeissler

User metadata
Rank l33t
Rank
l33t

The voodoos have one BIG advantage. The run nativ supported and optimized (wickedgl) games MUCH better,
then the other cards of the same time period and even the generation after that.

There is only a very small drop in framerate between 640x480/800x600/1024x768 on the V3.

Though there is the 16BIT/22BIT color processing, but hey games from 1997-1999 do not really make that
difference if the game offers 16 and 32BIT colordeph.

Retro-Gamer 😀 ...on different machines

Reply 25 of 31, by user33331

User metadata
Rank Member
Rank
Member

I inserted all graphic option "very high" or "high" in Midtown Madness 2, visibility=full, traffic\pedestrials=full, 1024x768 resolution.
- Then drove recklessly full speed in city in full traffic and screen showed signs of slowing down.

This with Duron 650 Mhz and 512mb SDRAM.

Reply 26 of 31, by Bige4u

User metadata
Rank Member
Rank
Member

Since the cpu fsb is 200mhz internally and if you were using just pc100 memory, it would be running at the default clock speed of 650mhz(100x6.5), but since you are using pc133, perhaps inadvertanly, the system is running overclocked w/o you knowing @ 865mhz(133x6.5) and running at the default voltage stressing the cpu causing your issues, the memory divider should have kicked in keeping you at 650mhz but with a faster fsb externally.

Check the BIOS settings to make sure everything is correct for your cpu/system, if not, choose the "default settings" option, then tweak what you need to manually and save on exit, when back in windows, use CPU-Z v1.76 to check the cpu/fsb/memory speeds and other assorted information.

Example picture(my system)...

Attachments

  • system 1.jpg
    Filename
    system 1.jpg
    File size
    272.3 KiB
    Views
    662 views
    File license
    Fair use/fair dealing exception

Pentium3 1400s/ Asus Tusl2-c / Kingston 512mb pc133 cl2 / WD 20gb 7200rpm / GeForce3 Ti-500 64mb / Sound Blaster Live! 5.1 SB0100 / 16x dvdrom / 3.5 Floppy / Enermax 420w / Win98se

Reply 27 of 31, by Shagittarius

User metadata
Rank Oldbie
Rank
Oldbie

I run Half Life with a single Voodoo 2 on my P4 3.4Ghz without any real problems. I just went and looked at the Blast Pit section, and that is running at very nearly 30 FPS consistently. Are you using the miniGL driver or running D3D through it, cause that is a disaster.

Last edited by Shagittarius on 2019-07-17, 14:23. Edited 4 times in total.

Reply 28 of 31, by user33331

User metadata
Rank Member
Rank
Member

Is this true ?
https://forums.tomshardware.com/threads/midto … eforce2.878517/
"When you loaded the Via 4 in 1 drivers did you select the AGP Turbo mode? If you did not you would be running your AGP at 1X only. Turbo mode allows the choice of 2X or 4X (selectable in your BIOS)."

Voodoo 3-3000 AGP is =AGP 2x.
MSI MS-6340 v3 ( VIA KM133A chipset.)

Reply 29 of 31, by auron

User metadata
Rank Oldbie
Rank
Oldbie

regarding GTA2: this is a case of game speed tied to framerate+craptastic internal framerate limiter, which is why i'm surprised at the comments saying "easily running it above 60fps", because doing that will make the game run way too fast. same applies to capping with vsync to 60hz or whatever monitor refresh rate.

when turning on the framerate limiter it runs the game at a fluctuating 25fps so it's no wonder this results in a juddery mess. my solution is to use a modern OS, grab the unofficial 11.44 version, insert the audio files from the original disc, force vsync on in the driver, then get msi afterburner and cap the framerate to 29.993 FPS in RTSS (assuming a 60hz monitor). this is the way to get consistent frame delivery with lowest possible input lag and correct game speed.

supposedly there is a way to adjust the internal frame cap via registry, so maybe it's possible to improve results on retro PCs as well. as-is though i don't get how anyone can claim the game runs smoothly out of the box and this video running on a high-end 1999 config should illustrate this.

Reply 30 of 31, by lost77

User metadata
Rank Member
Rank
Member
user33331 wrote:

I inserted all graphic option "very high" or "high" in Midtown Madness 2, visibility=full, traffic\pedestrials=full, 1024x768 resolution.
- Then drove recklessly full speed in city in full traffic and screen showed signs of slowing down.

This with Duron 650 Mhz and 512mb SDRAM.

I think you are expecting too much of the Voodoo 3. 1024x768 with max settings was reserved for the top graphic cards of the day. For Midtown Madness 2 that would be the Geforce 2 Ultra.

I found a FPS score of a race I did a while ago. Recorded with FRAPS. This is the original Midtown Madness.

Athlon 700Mhz
Riva TNT2 Ultra
1024x768x16 Highest settings

44 FPS

There was certainly some dips down to maybe 25 fps or so.

Reply 31 of 31, by user33331

User metadata
Rank Member
Rank
Member

OK as a result I'll play games made before ←1999 with Voodoo 3 3000 AGP 16mb SDR:
- Half life 1 1998-99 (High detal causes some lags)
- Midtown Madness 1,2 1999,2000 (High detal causes some lags)

And use better AGP graphic cards 64-128mb DDR with after 1999→ games that need Win95/98:
- Such as Geforce 4,5,6(2002,03,04), ATI 9000-series(2002) that have Win95/98 drivers.
- Too bad that newer ATI like HD3650 512mb AGP(2007) don't have any Win95/98 drivers.