think I have found a couple of serious bugs or at least
incompatibilities with Diamond's Monster 3D II 12mb, the
drivers, or DX 6. With car shading turned on, there are some
serious problems with missing polygons(is this refered to by
the graphics industry as "polygon cracking"?)with the
previously mentioned Monster II and the latest Diamond
drivers. Also with mipmapping turned on the effect looks
awful and also looks like a bug. I'm no expert, I'm not
totally sure what mipmapping does, so correct me if I am
wrong about this. Anybody know what's causing this?
It's also very interesting to note that the usually slower
performing in Direct 3D Thriller 3D 4mb in my system runs
almost as fast as my Monster II 12mb, and with none of the
problems. What is it with Sierra and Rendition cards(other
than they used to sell a V1000 card), be it Direct 3D or
Speedy 3D, RRedline? They seem to make games that run better
on a Thiller 3D than anyone else. Ok, a couple of new demos,
F1RS2, NFS III, run pretty well on the Thriller as well.
Relevant system specs:
Win 95 OSR 2.1 DX 6 update
Abit AX5, latest Abit bios
64mb's EDO
P233 MMX overclocked to 262, 75 MHZ system bus
Diamond Monster 3D II 12mb, latest Diamond Drivers
Hercules Thriller 3D 4mb PCI, latest Hercules bios and
drivers
Creative Labs Soundblaster AWE 64, latest drivers
Thrustmaster ACM game card