Talk:PlayStation 2 technical specifications

Video games Low‑importance

This article is within the scope of WikiProject Video games, a collaborative effort to improve the coverage of video games on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Video gamesWikipedia:WikiProject Video gamesTemplate:WikiProject Video gamesvideo game articles

Low

This article has been rated as Low-importance on the project's importance scale.

Summary of Video games WikiProject open tasks:

Summary of Video games WikiProject open tasks

AfDs

Cake Mania (series) (0 participants)
Omocat (4 participants)
Fortnite Chapter 5 Season 2: Myths and Mortals (9 participants)
SpongeBob SquarePants (disambiguation) (9 participants)
Stick Soldiers (2 participants)
Rick Jay Glen (4 participants; relisted)
Do You Like Horny Bunnies? (16 participants; relisted)
Atlus USA (15 participants; relisted)

Merge discussions

Other discussions

No major discussions

Optical drive[edit]

The article currently states "Later models starting with SCPH-500xx are DVD+RW and DVD-RW compatible.". How come my SCPH-39004 (a european "fat" V7) happily reads DVD+RW without any problems or modifications..? (No modchip, unmodified consoles will play DVD video from burned disks). Am I missing something here?! SCPH-500xx would be referring to the later/younger V9 or V10 consoles (the ones with the Firewire/i.Link connector removed) --84.62.150.17 (talk) 23:02, 2 November 2013 (UTC)[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified one external link on PlayStation 2 technical specifications. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

Corrected formatting/usage for //www.philvaz.com/games/PS2.htm

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—^{cyberbot II}_{Talk to my owner:Online} 16:01, 1 April 2016 (UTC)[reply]

Some Tidying up PS2 Misconceptions[edit]

Just want to clarify a few things before anything is edited.

The idea of using the mainRAM for off-screen textures is misleading. The way the memory works is, like on the NGC, assets are all stored on the main RAM, and their VRAMs are streamed just the portion of the content needed to build the current frame. They then stream through, and process, very quickly, the data, to draw said frame. They're sent a lot more than just 3MBs or 4MBs per-frame, as they just build a frame in several MB doses at a time, at rates closer to an SGI workstation of the time's. A NGC game will have much more than 1MBs of textures, per frame, as it was built to handle everything going in & out, like PS2. PS2 has texture buffers that work out the texels for the frame buffers.

In fact, the ps2's vram, at 30-60hz, can stream through, and process, up to nearly 38-76MBs/frame (according to: Source, see GS section), more than the 32MBs of main RAM can even store. VRAM doesn't become a bottleneck, so you only have to worry about what you can fit into mainRAM. So, it's not that you need to allocate some portion of another memory, for extra space & potential, hence why the statement is misleading. Instead, it is again that you store all the level's assets on mainRAM, then stream it to their VRAMs, in little doses, and they build the frame, very quickly, in very small doses of a MB or so, at fast rates. So, it's more about how fast their VRAMs can work, the throughput, and, as they could go through way more than what the total of their RAMs sizes, once more, the main RAM becomes what determines what size & complexity a level will factor, on screen, etc.

Most graphics cards of the time (circa 2000-2005, and onward) would have stored all their assets into VRAM, as there was almost no work to be done on the CPU, anymore, save for the basics, and their buses were much slower, and not meant to handle constant streaming, like PS2's and NGC's. So, technically, this is where the confusion comes from, as many would merge this together with the fact those systems were intentionally slower, given how their memory arrangement worked, and could not, very quickly, stream, from one pool of memory to another, anywhere near as quickly as NGC & Ps2 could.

Xbox had just 6.4GB/sec, for the whole system, 5.34GB/sec, after CPU stuff was taken care of. PS2 & NGC had 2.6-3.2GB/sec, just for the main RAM, then a dedicated 1.2-1.3Gb/sec asset/data transfer bandwidth, only for sending content to the GPUs of the systems, then 18-48GB/sec for VRAM, so that work doses could be done, and gone through, incredibly quickly, so it could move on to the next dose of content.

Second, the bit about Multi-Pass rendering is a bit specific, while including the data from the pdf is fine. Mind you, the poly count listed isn't exactly in the paper listed. Maybe just the poly count bit could be removed?

--SilenceoftheHills (talk) 13:54, 12 April 2022 (UTC)[reply]