Skip to content

Releases

TyraX 2.15.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 01:23
e059583
  • 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".

Full changelog

TyraX 2.14.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 13:51
e828346
  • Faster drawing while driving on the PS2: terrain tiles next to a ground shadow, and other scenery that used to be worked out from scratch every frame, are now drawn the fast way. Measured on a PS2 in the crate-field crash drive: about 0.47 ms less work a frame, and 9 instead of 17 objects a frame taking the slow path. Rebuild games to use it.

Full changelog

TyraX 2.10.0

Choose a tag to compare

@github-actions github-actions released this 05 Nov 19:02
17f8cde
  • Batch grouping cell (Preferences > Static object batching). The width of the grid static batches are grouped in is now a project setting; auto keeps the cell every project used so far. A smaller cell merges fewer sparse props but leaves fewer batches crossing the edge of the screen, which cost the PS2 about 1.7 times a whole batch. Measured on a PS2: in a copy of the Vehicle Playground with a 129-crate field, 48 instead of 80 leaves 11 instead of 13.5 crossing batches a frame and takes 0.15-0.2 ms off draw submission; in the shipped Motor District it is neutral to slightly worse (p95 +0.2-0.5 ms), so the example keeps auto. See docs/static-batching.md, "The grouping cell".
  • Objects, static batches and road chunks that cross the edge of the screen cost the PS2 about 7 µs less each a frame (about 0.1 ms a frame in the Vehicle Playground crate-field drive). docs/stapip-bag-cost.md also measures what one draw costs the console, and why.

Full changelog

TyraX 2.9.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 22:34
7b1e597
  • tyrax::raycastCamera. A script raycast that always starts at the active camera: a cutscene's or setCamera's eye while one owns the view, the player's camera (first-person eye, third-person boom) otherwise. Aim it at a point or an object; by default it stops at the target, so hit tells you something solid stands between the camera and it, and hit.object == target that the camera sees the object first. tyrax::cameraPosition(ctx) returns that origin. See docs/script-api.md.

Full changelog

TyraX 2.8.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 20:56
ac78831
  • Script debugger. Stop the game on a line of a C++ script, step through it, read and change its locals and fields, from VS Code (F5) or any GDB. Open the project in VS Code and press F5: an open editor switches the debugger on, builds and runs the game, and with no editor open F5 does it headless (it asks before turning the debugger on). Change a script and press F5 again: it saves, rebuilds and restarts the game before attaching. The run button at the top right of a script does the same, in place of the C/C++ extension's "build and debug active file". Saving changed code while debugging shows that the game runs older code, and Restart rebuilds and starts it again. The editor checks that the game it serves is the build it has: a different game on PCSX2's PINE slot, or an old build still running, is named instead of debugged. Build > Debug Scripts in VS Code does the same from the editor, and the switch sits with the other live tools in Preferences. A GDB chip in the toolbar shows when it is ready, attached or stopped. It works in a stock PCSX2: the game carries a small breakpoint handler and the editor talks to it through PCSX2's PINE socket. Debug builds only; your scripts compile unoptimised while it is on so lines and variables match the source, and a release build carries none of it. Stepping is fast: a step over a line (F10) takes about a tenth of a second. New CLI: --debug-run (build, run, serve) and --debug-serve (serve a game you launched). See docs/script-debugger.md.
  • The VS Code extension is now "TyraX" (doctorspider.tyrax, version 0.5.0), published on the Visual Studio Marketplace by every release that bumps its version. It adds the tyrax debug type and a TyraX: Debug Game in PCSX2 command. The editor replaces the old tyrax.tyrax-flownode install, no longer reinstalls an up-to-date or newer copy every session, and finds VS Code when code is not on PATH (a fresh macOS install). The previous package was missing the menu-stylesheet language; this one has every language.
  • Fixed the editor's ELF reader looking up symbol names in the wrong section, so no symbol was ever found by name.
  • Fixed a project that owns a script.hpp from before the script API no longer compiling once a graph used Play Sound, Raycast, Random, events or Call Script. The graphs fall back to their own implementations there.
  • Fixed double, short, long and unsigned public fields failing to compile.
  • Detaching a script now keeps its field values; attaching it back restores them. Values kept from a detached script no longer load sounds or create events.

Full changelog

TyraX 2.1.1

Choose a tag to compare

@github-actions github-actions released this 26 Oct 17:29
e4acb73
  • The release notes on GitHub, and in the editor's update dialog, are now this changelog's entry for the version instead of a bare "Full Changelog" link.

Full changelog

TyraX 2.1.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 16:35
8dd65d5

What's Changed

  • Point-sampled textures (Smooth / Pixel / Pixel close-up), Properties > Material Editor, texture-atlas-filtering example by @doctorspider42 in #303

Full Changelog: v2.0.1...v2.1.0

TyraX 2.0.1

Choose a tag to compare

@github-actions github-actions released this 25 Oct 13:43
94c50db
  • The Assets header and selected asset's Open in Asset Browser buttons no longer share an ImGui ID. UI scripts now fail on duplicate widget IDs without requiring a hover, and the Linux release job exercises the Assets actions before packaging.

Full Changelog: v2.0.0...v2.0.1

TyraX 2.0.0

Choose a tag to compare

@github-actions github-actions released this 24 Oct 20:52
f01e832
  • Project > Audio is laid out by what loads each sound. Sounds are grouped into Always loaded, the scene, each streaming layer, each sound bank, other scenes and never loaded. Selecting one opens an inspector with what loads it, what plays it, its banks and the Always loaded switch. A card on top shows the most sound RAM a scene can need at once, split by group, with a scene picker. Music has its own tab.
  • Sound effects follow streaming layers, and you can make sound banks. The emitters and vehicles of a streaming layer bring their sounds with them, so an open-world scene keeps only the sounds of the districts you are in. Named banks (Project > Audio > Banks) group sounds a mission or cutscene needs, and the new Set Sound Bank Loaded node loads and unloads them. Sounds still playing when their layer or bank goes away are cut off cleanly, and anything else keeps playing, including through a scene switch. The SPU2 sample RAM meter now shows the worst moment it can find: zones close enough to be in together, layers your graphs load, and the banks they load.
  • Sound effects now load per scene. A scene keeps only the sounds it uses in the PS2's 2 MB of sound RAM, and frees them when another scene starts. Sounds every scene uses, sounds in prefabs, and sounds you mark Always loaded in Project > Audio stay loaded for the whole game. Sounds nothing plays are no longer loaded at all. The SPU2 sample RAM meter shows the shared sounds plus the heaviest scene, which is the most that is ever loaded at once. Play Sound nodes no longer load a second copy of a sound that an emitter also uses.
  • Walking through trees with distant impostors no longer drops frames. Every tree switching back to its full model used to be rebuilt in one go, about 13 ms on a PS2, so the impostor grove held 60 FPS standing still but fell to 50, or to 40 at a run. The full model is now baked over a few frames while the impostor is still shown, and models lit only by the sun bake several times faster (which also shortens scene loading). On the console the worst frame went from 27 ms of rebuilding to under 3 ms.
  • Camera drags in the viewport no longer stop at the edge of the window. Orbiting, panning or pushing forward with the right and middle buttons together wraps the cursor to the other side of the viewport when it reaches an edge, so a drag lasts as long as your desk does.
  • Shining the flashlight on a big block no longer switches off the lamps already lighting it. Large boxes skip only the torch's per-vertex cone (the beam lands on them as a per-pixel pool), and they used to lose every dynamic light with it.
  • A flashlight held in the eye no longer takes a shadow away. It used to win the shadow slot of whatever it lit from the moon or a lamp, and a torch shadow cast from the eye falls exactly behind its caster, so the shadow simply vanished. A torch held off the eye (Held right / Held below eye) casts its shadows as before.
  • A prop lit by a lamp keeps that lamp's light when the flashlight sweeps over it. Each mesh takes one dynamic light, and the torch used to take it whenever it scored brighter, so a ball next to the pulsing crystal turned torch-white and lost its blue. A lamp that properly reaches a mesh now keeps it, and the torch still lights what it is aimed at through its per-pixel pass.
  • The flashlight lights physics objects per pixel like everything else, so a crate under a lamp shows the torch's hotspot on top of the lamp's light.
  • The flashlight's pool on the floor no longer jumps when the beam's centre crosses the edge of a crate or another small object. It used to snap to the object's foot, or lie flat at the height of its lid, and back again, which looked like someone shaking the torch. Only walls and floors big enough to hold the pool move it now.
  • A projected shadow no longer switches off when you walk past its caster. Only casters in view could hold a shadow slot, so once an obelisk left the frame the long shadow a lamp threw from it vanished from the screen. A caster whose shadow is in view now keeps its slot.
  • The flashlight's ground pool no longer paints a bright band across the bottom of walls. It floated up to 1.2 units over the ground to clear bumps in the terrain, so on flat ground it lit the foot of every block it ran into. It now floats only as high as the ground under it needs.
  • The lighting example is a night plaza now: a moon that throws the hero objects' shadows, thin fog, a street lamp carving shadow volumes over the crates, and a flashlight held in the right hand with torch shadows on. The dusk ambience is still in the project.
  • Drop to floor moved from the Scene menu to the Edit menu.
  • The start page's Open folder... button is now just Open.
  • The Cutscene Director is easier to find your way around. The timeline takes the whole height of the window, and the shot preview (which can be folded away) sits above the inspector in a column on the right, so the inspector no longer scrolls in a small box. Object tracks open like a tree: a track into its channels (Position, Rotation, Scale, Color, Visibility), and Position, Rotation and Scale into X, Y and Z. Each row shows its value at the playhead and has a diamond that keys that row at the playhead or removes the key there. The time ruler stays at the top however far you scroll the rows, so you can always scrub. The Cinema workspace starts with the Project and Properties panels hidden, so the viewport and the Director get the full width (Ctrl+B and Ctrl+Alt+B bring them back; Layout > Reset to built-in arrangement applies this to an existing project). Keys are per channel now: dragging or deleting a key on the Position X row moves or removes position X only, and each axis interpolates between its own keys. Older projects open unchanged. Projects are saved as format 120.
  • The procedural node inspector is a form instead of a long list of fields. Each node has a header with its icon, inputs and outputs, and buttons to preview the node, bypass it and show its help. Values that belong together share a row, min..max pairs are one range with draggable ends (with the falloff drawn on it), short choices are segments and on/off settings are chips. Safety caps sit in a collapsed Advanced row. Settings that do nothing in the current mode are hidden. Noise and Terrain masks show their result, Remap Mask shows its curve and Filter by Attribute shows a histogram of the incoming values. Pool rows are cards that show each model's share of the points. Output lists every property it can set on the generated objects as a tick list.
  • The side panels slide away to give the viewport the room. Click the open page's icon on the left rail again (or press Ctrl+B) to hide the Project panel, and click any rail icon to bring it back. Ctrl+Alt+B hides the Properties panel. The two panel switches at the right end of the status bar and the View menu do the same. A hidden panel returns to the same place and size.
  • Each window layout remembers which side panels it has hidden, so the Procedural layout can keep the Project panel out of the way while Default keeps both. New projects get Procedural with the Project panel hidden. In existing projects, Layout > Reset to built-in arrangement applies the new default. Projects are saved as format 119.
  • The workspace switcher on the top bar ends in a ... button that lists the other layouts (Material Designer, Procedural and your own) and New layout....
  • Text in the Output and Debug panels selects directly with the mouse, colours and all: drag, Shift+click, double-click for a line, Ctrl+A, then Ctrl+C or right-click Copy. The Select text switch is gone.
  • The Debugger's Build & Run follows the PCSX2 | PS2 switch like the top bar's Run. With PS2 selected it used to launch PCSX2 anyway.
  • Copy image in Debugger > Screen now pastes into Claude and other Electron apps on Windows; it used to fail there unless the PNG was copied from Explorer.
  • The built-in layouts can no longer be deleted. They can still be renamed or reset. A project that lost one in an earlier version gets it back on open.
  • Instanced scatter budgets count shared near/far geometry instead of flagging the sum of every placement as an over-budget mesh. The full placement sum remains informational, and the memory label identifies geometry-only estimates.
  • Shared procedural object settings now live in the Output inspector instead of a disconnected graph card. Existing settings are preserved. Instance detail clearly shows that it is unused in Instanced mode, and its help explains the visual cost of simplification.
  • Dense procedural previews keep their models above 4,000 instances instead of replacing the entire layout with green crosses. Pick Asset previews use the pool's distant models, Output draw distance and camera-frustum culling. Unassigned graph points retain their markers.
  • The upscaler (BLSS) can draw only the particle emitters at the reduced resolution (Draw reduced: Particles only): smoke, haze, fire and rain lose three quarters of their fill while the rest of the scene, the HUD and every texture stay sharp, and depth of field, portals, split screen and frame extrapolation keep working beside it. On a physical PS2, upscaler-lab's haze yard went from 34.8 ms to 13.8 ms of frame work. See docs/upscaler.md.
  • New Set Upscaler (BLSS) flow node (and ctx.upscaler for scripts) switches the upscaler while the game runs - Scene default, Off, On or Automatic - so a level can run native and drop to the reduced raster only in the zone where the smoke and sparks are. The switch moves no VRAM.
  • BLSS's neural reconstruction is removed - the network, its trainer, the Neural Upscaler window and the --blss-* commands. It measured +0.3 dB over plain bilinear for ~5 ms of EE a frame. Projects keep the plain upscaler; the old settings are dropped on the next save (format 118).
  • Tree Generator adds Forest oak and He...
Read more

TyraX 1.173.2

Choose a tag to compare

@github-actions github-actions released this 20 Oct 15:09
45336c8

What's Changed

New Contributors

Full Changelog: v1.172.2...v1.173.2