Triplex Para-souls X1650 512Mb DDR2

A retro-review and benchmarks of a mid-range card from ATi’s final generation of fixed function graphics cards.

  • RRP: unknown
  • Released: February 1st 2007
  • Purchase October 2024
  • Purchase Price £4.99
  • Form Factor: PCI-E
  • Available as AGP: Yes
  • Windows Compatibility: XP, Vista, 7, 8, 8.1, 10 and 11

Introduction – The Radeon X1000 Series

ATI’s Radeon X1000 series was introduced in 2005 as the successor to the Radeon X600/700/800 family. It retained strong DirectX 9 performance while adding Shader Model 3.0 support which was previously missing.

Compared with the X800 series, the X1000 family made greater use of programmable shader hardware. ATI’s new architecture was designed to handle more complex lighting, shadows, and surface effects, while features such as High Quality Anti-Aliasing and improved anisotropic filtering helped produce cleaner images. The series also introduced better support for high-definition video features, although the extent of hardware acceleration varied between models.

The timing of the launch was significant because the X1000 series overlapped both Nvidia’s GeForce 6 and GeForce 7 generations. The first Radeon X1800 cards appeared in late 2005, when the GeForce 6 family was still widely available, while Nvidia’s GeForce 7 range had already begun replacing it with products such as the GeForce 7800 GTX. ATI’s X1600 and X1300 models arrived during this transition period, competing with cards including the GeForce 6600, 6800, 7300, and 7600.

In broad terms, the X1000 series was more advanced than the older Radeon X800 generation, but its position against Nvidia depended heavily on the model. High-end Radeon X1800 and X1900 cards competed with the GeForce 7800 and 7900 families, while the X1300 and X1600 ranges targeted Nvidia’s lower and mid-range offerings. ATI therefore offered a complete DirectX 9 lineup, but the numerous GPU variants and confusing model names made comparisons less straightforward than they appeared.

Radeon RV530/RV535 Lineup Overview

The Mid-range cards of the X1000 series spanned three key GPU Codenames:

  • RV530 (Radeon X1300(XT)/X1600/X1650): The main workhorse of ATI’s midrange X1000 lineup, RV530 balanced modest gaming performance with full DirectX 9.0c support and shader model 3.0. It powered the highest-end version of the X1300 cards (the X1300XT) through the better-known X1600 Pro and XT and then lower-end variants of the X1650.
  • RV535 (Radeon X1650 Pro/X1650 XT): RV535 was the shrunk and refined version of the X1650-era architecture, bringing the same overall design to 80 nm with higher clocks and better efficiency. It formed the stronger end of the X1650 family, especially in X1650 Pro and X1650 XT form, where it delivered the best mix of clock speed, thermals, and board partner variation in this branch of the Radeon range.
  • RV560 (Radeon X1650 GT): Positioned as a lower-cost refresh of the X1650 line, RV560 kept the same basic 12 pixel shader, 5 vertex shader, 4 TMU, 4 ROP design but arrived on the smaller 80 nm process. In practice it sat between the older RV530-based X1650 and the faster RV535-based X1650 Pro/X1650 XT parts, offering a tidy stepping stone for OEM and mainstream boards. It must have been pretty rare as I can’t find any online, even searching completed sales on ebay.

Together, these chips saw made out the popular mid-range and competed directly with Nvidia’s 7600 series of products.


The Card

This card is special to me as it’s the first retro card purchased, hard to imagine looking up at the shelf above creaking under the strain, but there was a time where I just owned the GPU that is in my main PC and a spare FirePro card in a box somewhere.

I can’t say that I knew anything about the X1650 at the time that I clicked the ‘buy it now’ button, but that was part of the appeal.

The box looked nice in the photo but the seller had crushed it and slipped it in a jiffy bag, what a waste of history there. I still have it, of course, but it’s not a pretty sight.

There is little information about Triplex online. They were obviously a partner of ATi in the 2000s and manufactured cards from Taiwan. A few different reviews are out in the google results but on this exact card I could find nothing at all.

The card itself is very basic, it has the three normal outputs (S-Video, DVI and VGA) but a slightly sad looking cooler kept in place with two push pins. There really isn’t a whole lot more to say about it.

Once installed with all drivers, I also found that there are no temperature sensors anywhere on the card, also the fan runs at max speed only with no controller.. so very much built down to the lowest cost.

To add to the overall budget-feeling nature of this product, there was a clearance sticker on the box – even at the time no one wanted this card at the £49.99 price, it was sold at £34.99.

The side of the box suggest that there was perhaps a DDR3 version of the card, said I didn’t get that one, at least this isn’t stuck with a 64bit memory bus and we have the full 128bit. We do have the highest 512Mb RAM on board but I am suspicious that, like most mid-range cards of the era, the GPU won’t have enough grunt to need it.

The Ebay ad, hard to argue with £4.99

What is the X1650 without the Pro/XT suffix?

A good question! The vanilla X1650 seems to be a reasonably rare beast. There are pro cards everywhere by comparison.

What we are actually looking at is a renamed X1600 Pro with which it shares it’s RV530 core, but pumped out later with lower clocked DDR2 RAM, not very customer friendly.

The GPU-Z screenshot shows the stats of our card, the Default Clocks are blank but that quite often is the case so no worries there.

Against the basline figures lifted from the wikipedia entry for the X1650, we have a slight overclock on the GPU – up from 500Mhz of 554Mhz but the RAM clock is well down from an effective 800MHz to only 666Mhz. Which will no doubt show in the results

Popping off the heatsink assembly and repasting was no problem at all so I did that, dropped it into the system and set off to see what it can do.


The Test System

I used the Phenom II X4 for XP testing, not the most powerful XP processor by any means but its 3.2Ghz clock speed should be more than enough to get the most out of mid-2000s games, even if all four of its cores are unlikely to be utilised by most titles.

The full details of the test system:

  • CPU: AMD Phenom II X4 955 3.2Ghz Black edition
  • 8Gb of 1866Mhz DDR3 Memory (showing as 3.25Gb on 32bit Windows XP and 1600Mhz limited by the platform)
  • Windows XP (build 2600, Service Pack 3)
  • Kingston SATA 240Gb SSD as a primary drive, an AliExpress SATA has the Win7 installation and games on.
  • ASRock 960GM-GS3 FX
  • Catalyst 10.52
The Triplex Card stats compared to some competitors that you will see in the graphs below.

Tom Clancy’s Splinter Cell (2002)

Game Overview:

Tom Clancy’s Splinter Cell launched on November 19, 2002, developed by Ubi Soft Montreal. Built on the LithTech Jupiter engine (Unreal Engine precursor), it pioneered tactical stealth gameplay with groundbreaking light/shadow mechanics and realistic audio design. The game set new standards for immersion through dynamic lighting where visibility literally shaped gameplay.

Known for its revolutionary light-based stealth, Splinter Cell remains the ultimate benchmark for early 2000s GPUs. The game’s real-time shadows, particle effects, and high-poly environments brutally stress fillrate and shader performance even on modern retro hardware.

I have the GOG version of the game which has an internal benchmark that can be used.

Performance Notes:

The first test then and our little X1650 does not perform well, an average of 42.02 means a result down under even the budget X1300Pro. Far, far below the 7600GT which really should be in the same performance bracket.

The performance against the budget-tier X1300Pro can only be explained by the lower core and memory clocks of the X1650.

This early title obviously can’t take advantage of the extra pipelines


Unreal Tournament 2003 (2002)

Game Overview:
Released in October 2002, Unreal Tournament 2003 was built on the early version of Unreal Engine 2. It was a big leap forward from the original UT, with improved visuals, ragdoll physics, and faster-paced gameplay.

The engine used DirectX 8.1 and introduced support for pixel shaders, dynamic lighting, and high-res textures all of which made it a solid test title for early 2000s hardware.

We played a lot of this and 2004 at LAN parties back in the day.

Still a great game and well worth going back to, even if you’re mostly limited to bot matches these days. There’s even a single-player campaign of sorts, though it’s really just a ladder of bot battles.

The game holds up visually and mechanically, and it’s a good one to throw into the testing suite for older cards. The uncapped frames are pretty useful for my purposes.

Performance Notes:

A well optimised game this one and most mid-decade games give a very good account of themselves.

Our X1650 however falls well short of what is expected again, it does actually beat the X1300Pro in this title but the mid-range Nvidia competition of the time performs much better.


X2: The Threat (2003)

Game Overview:

Released for Windows in December 2003, with later ports to Mac OS X and Linux, X2: The Threat is a space trading and combat simulation developed by Egosoft. It continues the story from X: Beyond the Frontier, placing players in the role of Julian Gardna, a former pirate drawn into a conflict with a new alien threat known as the Khaak

While not tied to a widely licensed engine like Unreal, X2 introduced a new in‑house graphics engine built specifically for the X‑Universe. This engine delivered Improved ship and station models, More detailed sectors with nebulae and environmental effects, Dynamic lighting and particle effects and Support for DirectX 8.1‑class hardware, aligning it with early‑2000s GPU capabilities.

This made X2 a solid benchmark title for PCs of the era, especially for players testing mid‑range and high‑end GPUs from the GeForce 3/4 and Radeon 8500/9000 families.

This is the GOG version again and it does have an internal benchmark.

Performance Notes:

In X2: The Threat, the X1650 suffers again and is soundly beaten by the X1300Pro.

The slow clock speeds really hurt here.


Doom 3 (2004)

Game Overview:
Released in August 2004, Doom 3 was built on id Tech 4 and took the series in a darker, slower direction. It’s more horror than run-and-gun, with tight corridors, dynamic shadows, and a heavy focus on atmosphere. The engine introduced unified lighting and per-pixel effects, which made it a demanding title for its time, and still a good one to test mid-2000s hardware.

Performance Notes:

In Doom3 at 1024×768 we find the X1650 above the X1300Pro again, but the two of them languish down at the bottom of the table. 47.6fps isn’t a bad result if you wanted to play Doom3 but then so many other cards can perform the same trick so much better!


FarCry (2004)

Game Overview:
Far Cry launched in March 2004, developed by Crytek and built on the original CryEngine. It was a technical marvel at the time, with massive outdoor environments, dynamic lighting, and advanced AI. The game leaned heavily on pixel shaders and draw distance, making it a solid stress test for mid-2000s GPUs. It also laid the groundwork for what would later become the Crysis legacy.

Minimum at 800×600 is not a tricky task and becomes GPU limited at around 260ish fps.

Sadly the X1650 remains the bottleneck even at these settings, allowing 198.75 fps… a nice high number, but still,

Ultra Settings then along with a higher resolution, more of a test for these cards.

The X1650 gives a useful 56fps, edging out over the X1300pro but sitting behind the 6600GT

Adding in some Anti-Aliasing halves the framerate but 33.59 fps isn’t too bad.

It is well behind the higher mid-range 7600GT though which can manage nearly three times the framerate.

Really pushing things now at 1280×1024, just because three graphs looks bad in two columns more than anything.

At these settings the X1650 gives out 23.06 fps, not really a playable level there.

F.E.A.R. (2005)

Game Overview:
F.E.A.R. (First Encounter Assault Recon) launched on October 17, 2005 for Windows, developed by Monolith Productions. Built on the LithTech Jupiter EX engine, it was a technical showcase for dynamic lighting, volumetric effects, and intelligent enemy AI. The game blended tactical shooting with psychological horror, earning acclaim for its eerie atmosphere and cinematic combat.

Performance Notes:

F.E.A.R then.

The card is still at the bottom of the table but at least has the company of the 6600GT, a mid range card, albeit from the previous generation of Nvidia GPUs.

I would have guessed that the extra Pixel and Vertex shaders would have helped the X1650 along in this title as it was known for it’s visual effects but, not so. Raw clock speed is expected to pull you through here.

Adding some Anti-Aliasing obviously does benefit from the extra pipes, the X1650 does no better but other cards are pushed down the scale to join it in the unplayable bottom section.

Beating the much newer HD2600Pro is good, but more embarrassing for the later card really.


Battlefield 2 (2005)

Game Overview:
Battlefield 2 launched on June 21, 2005, developed by DICE and published by EA. It was a major evolution for the franchise, introducing modern warfare, class-based combat, and large-scale multiplayer battles with up to 64 players. Built on the Refractor 2 engine, it featured dynamic lighting, physics-based ragdolls, and destructible environments that pushed mid-2000s hardware.

No single-player campaign, but I find bot matches via Instant Action a lot of fun. It was hugely popular in its day, especially for Commander Mode, vehicle combat, and it apparently had a thriving modding scene.

Battlefield 2 performs adequately in this title and high settings are within reach. It actually performs better than the 6600GT which is nice, the X1300Pro is still far ahead. Strange.

A little Anti-Aliasing and performance drops predictably enough, the RV630 does a better job than the RV515 in the X1300Pro obviously as the X1650 is now ahead, the best result yet.


Need for Speed: Carbon (2006)




Game Overview:

Need for Speed: Carbon launched on October 30, 2006 in North America, developed by EA Black Box and published by Electronic Arts. It continued the series’ street-racing focus after Most Wanted but shifted the action to canyon showdowns and crew-based racing, adding stronger emphasis on territory control and team support. The game was built on the EAGL engine and designed to showcase glossy car models, night-time city lighting, and heavy visual effects suited to mid-2000s gaming PCs and consoles.

At 800×600 Medium settings performance is finally good! 58Fps beats even the 6800GS and 7600GT, two cards that were unbeatable in previous tests.

More of the same at 1024×768 Medium proving that it’s not just an error in the results.

Finally, a title that allows the card to use those extra pixel and vertex shaders

Max settings slow things down significantly and predictably – it’s a pretty game. The X1650 still does better than it’s competitors though.

Max and AA and things fall well within unplayable levels but it’s an interesting test anyway, perhaps the large 512Mb Frame buffer even has an effect here.


Medieval II: Total War (2006)

Game Overview:
Released on November 10, 2006, Medieval II: Total War was developed by Creative Assembly and published by Sega. It’s the fourth entry in the Total War series, built on the enhanced Total War engine with support for Shader Model 2.0 and 3.0. The game blends turn-based strategy with real-time battles, set during the High Middle Ages, and includes historical scenarios like Agincourt.

Performance Notes:

Medieval Total War on Medium Settings using the older SM1.0 method shows an average 43fps on the X1650. This brings the X1650 into good company, beating the 6600GT and budget X1300Pro

Best settings introduces SM2.0 and Anti-Aliasing, far too demanding for our X1650. Equally to demanding for the 6800GS and 6600GT which join the X1650 at the bottom of the table.


Test Drive Unlimited (2006)

Game Overview:

Test Drive Unlimited launched in 2006, developed by Eden Games and published by Atari. It took the series in a new direction with a huge open-world recreation of Oahu, where driving, buying cars and homes, and challenging other players were all part of the experience.

It was built on Eden’s Twilight 2 engine, giving it a more ambitious open-world setup than the previous Test Drive games. The big hook was its “massively open online racing” style, which blended solo progression with always-on multiplayer roaming.

800×600 against the lower and mid-range cards and the X1650 shares the familiar space with the 6600GT and X1300Pro, splitting the two cards.

25fps with 11fps on the 1% low is clearly not sufficient to play this title.

High settings at 1024×768 is asking a lot from the X1650 and 24fps is all that it can manage. Ahead of the 6600GT and a not-embarrassing amount behind the higher-end 6800GS

With Anti-Aliasing, also at High settings we are down at 19fps, now matching the much news HD2600Pro which is a card that matches the 512Mb of DDR2.


Oblivion 2006

Game Overview:
Oblivion launched on March 20, 2006, developed by Bethesda Game Studios. Built on the Gamebryo engine, it introduced a vast open world, dynamic weather, and real-time lighting. The game was a technical leap for RPGs, with detailed environments and extensive mod support that kept it alive well beyond its release window (it’s just had a re-release recently).

Known for its sprawling world Oblivion remains a benchmark title for mid-2000s hardware. The game’s reliance on draw distance and lighting effects makes GPUs struggle.

Oblivion is a tough game and not very nice looking at medium settings, still 59fps can’t be argued with. well ahead of the 6600GT and X1300Pro cards.

Ultra-High is far more of a challenge and the Triplex Card can only handle 23fps average, still ahead of the 6600GT which we’re getting used to seeing.

Ultra-High and 4xAA is clearly too much for the mid-range cards at the time, 30fps is only 1 away from the 6800GSD however and the 1% lows are way ahead


Crysis (2007)

Game Overview:
Crysis launched in November 2007 and quickly became the go-to benchmark title for PC gamers. Built on CryEngine 2, it pushed hardware to the limit with massive draw distances, dynamic lighting, destructible environments, and full DirectX 10 support.

The game is just about playable on the HD2600XT and 8600GT under DirectX 9.
‘Very High’ settings are technically selectable, but not on XP. To be tested separately later in the article.

Performance Notes:

The X1650 does give a usable 30fps in Crysis so close to playable if not exactly smooth.

This does beat the 6600GT and X1300Pro nicely

No surprises really about the performance once medium settings were selected – perhaps that the 7600GT performs equally badly posting only 13fps.


S.T.A.L.K.E.R. (2007)

Game Overview:
Released in March 2007, S.T.A.L.K.E.R.: Shadow of Chernobyl was developed by GSC Game World and runs on the X-Ray engine. It’s a gritty survival shooter set in the Chernobyl Exclusion Zone, blending open-world exploration with horror elements and tactical combat. The engine supports DirectX 8 and 9, with optional dynamic lighting and physics that can push older hardware to its limits.

Dynamic lighting – sure does make things look pretty, but at quite a significant cost in performance
Not quite as good with the static lighting

Stalker runs well on mid-range cards and the X1650 is no exception. 49 fps puts it well ahead of the 6800GS, X1300Pro and 6600GT and would be playable under these conditions

A tricky challenge for the mid-decade mid-range to handle the full dynamic lighting that Stalker can throw at them.

15Fps is the best that the card can do, Afterburner shows that this is actually using more than 256Mb of RAM.


Assassins Creed (2007)

Game Overview:
Assassin’s Creed launched in November 2007, developed by Ubisoft Montreal and built on the Anvil engine. It introduced open-world stealth gameplay, parkour movement, and historical settings wrapped in sci-fi framing. The first entry takes place during the Third Crusade, with cities like Damascus, Acre, and Jerusalem rendered in impressive detail for the time.

Performance Notes:

At 800×600 low the triplex X1650 gives a playable 54 fps, only a little behind the 6800GS and above even the X1300XT, those extra pipelines more than making up for clock and memory speed deficits.

Pushing the graphics up a notch level and increasing the resolution knocks the average fps down to 34.


Synthetic Benchmarks

The card was put through my usual suite of synthetic benchmarks with the following results:

3d Mark 2000


3d Mark 2001 SE

The X1650 does a little better than you may expect, given the gaming benchmarks on the earliest titles, beating the X1300Pro handily despite the clock deficits.

The result is still well below the 6600GT however.

3d Mark 2003

in 3d Mark 2003 the position is maintained, above the X1300pro but below the 6600GT by some margin.


3d Mark 2006

In 3d Mark 2006 those extra pipelines start to have an effect and the X1650 is now a good margin above the 6600GT


Unigine Sanctuary

Quite a demanding benchmark and the X1650 beats the 6600GT and X1300Pro handily again.



Temperature & Power Usage

I couldn’t find the TDP listed for the X1650 standard anywhere online, which was annoying.

There is no temp. sensor or fan controller on this card so not a whole lot to report on this section.

It is loud, as the fan speed is 100% at all times, the system draws 155w from the wall which is towards the lower end.

Summary and Conclusions

Unfortunately, not as well as its name might suggest. The X1650 moniker is somewhat misleading to begin with, as this particular card is based on the older RV530 architecture associated with the X1600 series. While the core itself is not especially poor, its performance is heavily restricted by the slow DDR2 memory used on this board.

In its current configuration, the card falls short of the supposedly lower-tier Radeon X1300 Pro in some earlier games. Those titles often cannot make effective use of RV530’s additional pixel and vertex-shader resources, leaving the X1650’s larger shader array underutilised. Combined with its slower memory, this allows the better-clocked X1300 Pro to take the lead.

In later and more demanding games, however, the X1650 manages to redeem itself somewhat and generally performs better than the GeForce 6600 GT. The GeForce 7600 GT remains well beyond its reach, although that is hardly surprising. A fairer comparison would be the Radeon X1650 XT, which was designed for this performance segment and, importantly, used much faster GDDR3 memory.

I will get hold of an X1650 XT eventually, although these cards do seem to be quite rare. For now, I have a standard GeForce 6600 available, which should provide a closer comparison with this unusual Triplex card.

The 512 MB frame buffer is, of course, excessive for this level of hardware. If every other specification were identical, a 128 MB version fitted with GDDR3 would likely outperform this slow DDR2-equipped model by a considerable margin. The extra memory capacity offers little benefit when the card’s available bandwidth is such a severe limitation.

Although the card is a welcome addition to the collection—and how many other people can say they own a Triplex Para-Souls X1650?—it has ultimately made for a somewhat disappointing test subject. More concerningly, I suspect the card may be beginning to fail. During the last few boots, the display has failed to initialise until I have pressed the system’s reset button.

This is my rock-solid Phenom system, which has successfully tested a large number of graphics cards without issue. With the rest of the platform behaving normally, the Triplex card is therefore the most likely source of the problem.

Leave a Reply