![]() The AI, for reasons unknown, seems actually worse in the sequel. Zombies look a little like Shamblers from Quake, except a lot smaller and a lot less dangerous. Except the Scorpion because, woah baby, look at those Wraiths getting blown up in seconds. The problem is that said sequences just aren’t very fun. They must have taken them straight from Halo, and the vehicle sequences in Halo aren’t very fun either. Half-Life is one such experience from start to finish, while HL2 and its episodes continuously break the action to make you feel cooler about yourself. One reason is that vehicular sequences are not present. People apparently liked the hovertank and the dune buggy thing, but I really prefer shooting aliens in the face. This gives me a rare opportunity: instead of telling you why HL is great, which really everybody should know by now, I’ll tell you why I like it better than HL2. However, there seems to be a preference for the sequel. This is cheating, right? I mean, putting Half-Life in any top games list is a bit like putting Michael Jordan in a list of best basketball players. I’m going to try a few S3-specific games next, although some of them were only available on DOS, so it will be hard to get pictures. A lower-quality solution like Ati’s might have been better in retrospect, but it should be at least noted that Ati’s own bilinear occurred in even worse performance drops even on the Rage II. ![]() I like that it tries to go for high-fidelity bilinear filtering, although it was probably a bad idea performance-wise. But if you consider the average 3D card at the time (did someone say NV1, AT3D and 3D Rage?), it was actually okay-ish. Then again, so few of these older games actually let you pick anything higher than 16 bits.Ĭould it have been better? Oh yes. But in truth, I didn’t see all that much of a difference in 320×240. Of course, the card was already slow enough. If you have the guts to enable 24 bits rendering on your damn Virge, quality improves considerably. Worth noting that, due to the Virge actually running in 15 bits colors (5550), there’s a bit more color banding than the average 16 bits game. ![]() Dithering was annoying, but you had to deal with it, at least in 16 bits mode. Some games actually run better than the DX, despite the less optimized (eheh) architecture, because the card isn’t choking under the weight of the textures. It’s surprising how much the extra memory helps. Alas, so many D3D games didn’t give many settings to play around with, either. After all, I have a P3, but most people at the time were stuck with, er, 133mhz? A Virge was bound to help a little bit in D3D-compatible games. Steer clear of any fancy effects, and your games might actually run a bit faster than before. Hardly the worst I’ve ever seen, at least. Enabling bilinear filtering incurs in a lower framerate (those numbers up there din’t tell the story anyway), and also an unneeded look into S3’s dithering solution. It runs decently on 320×240, as long as you disable texture filtering and fog and fancy stuff and… just about everything else… you know, maybe you should just take your chances with a N64. Tough luck, CPU guys: Turok requires a 3D card. It would be a bit like trying to run a 4K game on a regular Xbox One. Texture filtering! On a card that, by most accounts, needs 8 cycles for bilinearly filtered textures! Those engineers must have seriously overestimated their chances. Unfortunately, many S3-specific games wanted to run on at least 512×384, with bilinear filtering. The only way to run Blood 2 properly: in 320×240 on Low settings, with disabled lightmaps. If you stuck a Virge in there, kept the resolution low, and didn’t bother with filtering or anything else, your game was gonna look a lot like software rendering… but faster. Back then, it was sometimes hard to get even 320×240 to run well in software mode. It should be pointed out that its popular nickname might be something of a misnomer, as the card did indeed “accelerate” rendering. In Half-Life, the card outright refuses to texture the enviroment, even on 320×240… so I just took this picture at 640×480 for the extra crispness. ![]() Also, as my DX has merely 2MB of video memory, I went out of my way to find a 4MB Virge this time, so I could test a few games all the way up to 800×600 (why I would want to suffer like that, nobody knows), or at least run certain tests without the constant threat of dropped textures. While I already had the DX version, I know that the 3D engine was improved for that card, so I wanted to see what kind of framerates I could really get from the original decelerator.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |