You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Remote Pad on a real PS2 no longer costs the game frames. A debug game deployed over ps2link used to read the Remote Pad state as a file from your PC every 4th frame, and the console waited for each of those network round trips. Now the console's I/O processor receives the state from the editor over the network and leaves it in memory, so the game reads it for free every frame, and the pad also answers sooner. PCSX2 is unchanged. See docs/devlink.md for details.
The Live Debugger on a real PS2 goes through the I/O processor too. Breakpoints, pause/step, watches and the Stats page used to cost the console a network round trip every 25 frames, and the panel updated twice a second. Now commands and reports travel as network packets the I/O processor handles, so the game pays almost nothing and reports as often as it does in PCSX2. Nothing to set up: it happens whenever the run target is PS2.
Every other live tool on a real PS2 too: Live Link, Live Logic, texture hot reload and the time machine now reach a console game the same way, so editing the scene, patching a graph or rewinding no longer costs the game network waits every 25 frames. The game's log lines arrive the same way, in the editor and in --run-ps2.
Capturing the screen of a real PS2 no longer freezes the game for seconds.Debugger > Screen > Capture frame used to stop the console for about three seconds while the picture was written to your PC. Now the game only pauses to read the picture out of video memory, and the I/O processor sends it while the game keeps running. Measured on a PS2 at 512x512: a 34 ms pause, and the picture is in the panel about a second and a half later. If part of it gets lost on the network, the editor asks again by itself. The VU1 packet capture and the render-cost report travel the same way.
Live preview of the game's screen, real PS2 included.Debugger > Screen > Live preview shows a small moving picture of what the game is drawing - about 20 pictures a second from a console, at about a millisecond of the game's time each. Useful when the console is not next to you, or its TV is not. It is a preview (a quarter of the resolution); Capture frame still takes the full picture.
The Live Debugger no longer slows a PS2 game down while attached. An attached debugger used to cost the game about a millisecond every frame on a console (two short sleeps that guarded against a hang). With the debugger's traffic now going through the I/O processor the guard is no longer needed there, so attaching leaves the frame time alone.
Play the game on the console from the editor with an Xbox controller. Plug a controller into the PC, open Debugger > Screen, click the live picture and the controller drives the running game - on a real PS2 or in PCSX2; Esc lets go. The picture can be popped out into its own window and made fullscreen (F11), so the console does not need a TV next to you. Dead zone, trigger threshold, which pad it drives, when its input is sent and what every button sends (a full mapping, on a drawing of the pad) are under Preferences > Running games > Controller.
See the geometry of a whole frame.Debugger > VU memory > Frame > Capture frame geometry draws every triangle the game sent in one frame as a wireframe over a picture of the scene, one colour per draw batch, with the count of triangles that never reach the screen. Click a batch to isolate it. It works on a real PS2 as well. The single-packet view is still there (Packet), and now decodes geometry it used to miss.
--capture-frame and --profile-frame work against a real PS2 again. Since the Live Debugger moved to the I/O processor, a command written from a shell never reached a console game. The process that deployed the game now forwards it, so both commands work as they do in PCSX2 - about two seconds per picture.
The editor now knows when a game on a PS2 has crashed or frozen. The console's I/O processor keeps running when the main CPU dies and tells the editor: "the console's IOP reports the game silent for N s - it crashed or hung". Before, a frozen game and a console that dropped off the network looked the same.
A null or wild pointer on a real PS2 now gets a crash report. With the EE crash handler on (debug builds), the most common crash there is - touching memory through a null or garbage pointer - used to skip the handler entirely: no bin/crash.txt, no TYRAX screen, only ps2link's register dump. It is now reported like every other crash, and the console log says TYRAX EE CRASH the moment it happens. Crash backtraces also stop listing stack addresses as code. See docs/devkit.md, "A null pointer is reported too".