Not only that, but S3TC allowed these much higher quality textures to be rendered with negligible performance impact. Sign up now Username Password Remember Me. The Savage XP was basically a repaired version of the Savage and considered too outdated. S3 Graphics graphics processors. In early , S3 retired the Savage3D and released the Savage4 family. The mobile version was going to be called AlphaChrome but was otherwise completely identical.
|Date Added:||24 April 2010|
|File Size:||45.97 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
VIA Technologies x86 processors.
CONFIG_I2C_SAVAGE4: S3 Savage 4
Only the high-quality texture capability from its S3TC sacage gave it good mind share with the gaming community. Development of Savage as a discrete card was discontinued. The mobile version was going to be called AlphaChrome but was otherwise completely identical. S3 Graphics graphics processors.
On Paper Index On Paper 0.
86C410 S3 SAVAGE2000
The initial benchmarks looked solid, the performance of the chipset was much improved over the old Savage3D and most of the bugs the original solution were fixed in the Savage4. Poor drivers resulting in poor compatibility and poor performance notice a trend?
It was never sold, only prototypes exist. The Savage XP was the first chip announced by the regrouped S3 in S3 would regroup in later years and create the Chrome series.
Its innovative feature-set included the following:. 86v410 the past 68c410 product releases, S3 has done very little to offer the market a competitive solution. They could be equipped with MiB memory. S3 refined the chip, fixing hardware bugs and streamlining the chip for both cost reduction and performance. Retrieved from ” https: Index On Paper saage. Sign up now Username Password Remember Me. They added single-pass multi-texturing, meaning the board could sample 2 textures per pixel in one pass not one clock cycle through the rendering engine instead of halving its texture fillrate in dual-textured games like Savage 3D.
No other manufacturer would even dream of spending so much time and effort on offering a single video chipset, and thus most manufacturers dropped their Savage 3D products, including Diamond Multimedia, a name that would later hold much significance for the company.
The driver problems were still there. Savage was a product-line of PC graphics chipsets designed by S3.
Linux Kernel Driver DataBase: CONFIG_FB_SAVAGE: S3 Savage support
The compressed textures were a vast improvement over the standard textures eavage on all other cards. On paper, and even in the first few trials, the Savage 3D seemed like a true winner — a potential candidate for the “Voodoo2 killer” throne that the video market had so intently sought out.
The MX had many similarities to Savage4 but had reduced clocks and added an integrated TV out function with optional Macrovision. Unfortunately S3TL does not function properly.
200 causes missing textures, errors in geometry and models, and minimal performance benefits. From Wikipedia, the free encyclopedia.
Combined with poor drivers and the chip’s lack of multitexturing support, the Savage3D failed in the market. Savage supported S3’s S3TC texture compression, a hardware transform and lighting engine named “S3TL”, and was equipped with a “QuadTexture Engine” capable of a single quad-textured pixel per clock or 2 dual-textured pixels per clock.