The Problem:
Modern UDPBD and OPL implementations focus on maximum throughput. While "Zero-Latency" loading is impressive, it lacks the Mechanical Friction of a physical 4x DVD drive. On the SCPH-90000 (Deckard), this "Over-Feeding" of data causes I/O desyncs and FMV stutters because the console is hard-coded to expect the "Thinking Time" of a physical laser lens.
The Proposal: Mode 9 (Authentic I/O Timing)
I am proposing a new compatibility layer for UDPBD. Instead of seeking higher speeds, this mode would enforce the physical constraints of 2001-2007 era hardware to ensure 1:1 retail accuracy of the DVD drive. This isn't just "faking delays"—it is recreating the I/O pacing the original developers used to sync game engines.
The "Authentic I/O" Specification:
Hard 5.28 MB/s Cap: Enforcing the 4x DVD limit (44Mbit) over the 100Mbit line.
Seek Latency Simulation: Injecting timed pauses (e.g., 80ms–230ms) based on LBA jump distances to simulate the actuator arm.
Rotational Latency: Micro-delays between sector reads to mimic the spindle's spin and synchronization.
Zero Junk Policy: A "Purist Mode" that can optionally disable IGR, PADEMU, and GUI hooks. The goal is to maximize available IOP RAM to match the retail environment as closely as possible for high-stress titles.
Why this matters:
I've spoken with performance-focused devs who are primarily interested in throughput, but for the PS2, Timing = Compatibility. I am looking for the Purists—people like @TnA or @Berion—who understand that recreating the physical behavior of the drive is the final frontier for OPL stability on the Slim 90000.
Is anyone interested in helping define a standardized "Seek Penalty Table" or a "Paced Stream" protocol to bring this level of accuracy to OPL?
Modern UDPBD and OPL implementations focus on maximum throughput. While "Zero-Latency" loading is impressive, it lacks the Mechanical Friction of a physical 4x DVD drive. On the SCPH-90000 (Deckard), this "Over-Feeding" of data causes I/O desyncs and FMV stutters because the console is hard-coded to expect the "Thinking Time" of a physical laser lens.
The Proposal: Mode 9 (Authentic I/O Timing)
I am proposing a new compatibility layer for UDPBD. Instead of seeking higher speeds, this mode would enforce the physical constraints of 2001-2007 era hardware to ensure 1:1 retail accuracy of the DVD drive. This isn't just "faking delays"—it is recreating the I/O pacing the original developers used to sync game engines.
The "Authentic I/O" Specification:
Hard 5.28 MB/s Cap: Enforcing the 4x DVD limit (44Mbit) over the 100Mbit line.
Seek Latency Simulation: Injecting timed pauses (e.g., 80ms–230ms) based on LBA jump distances to simulate the actuator arm.
Rotational Latency: Micro-delays between sector reads to mimic the spindle's spin and synchronization.
Zero Junk Policy: A "Purist Mode" that can optionally disable IGR, PADEMU, and GUI hooks. The goal is to maximize available IOP RAM to match the retail environment as closely as possible for high-stress titles.
Why this matters:
I've spoken with performance-focused devs who are primarily interested in throughput, but for the PS2, Timing = Compatibility. I am looking for the Purists—people like @TnA or @Berion—who understand that recreating the physical behavior of the drive is the final frontier for OPL stability on the Slim 90000.
Is anyone interested in helping define a standardized "Seek Penalty Table" or a "Paced Stream" protocol to bring this level of accuracy to OPL?