Skip to content

OpenTricky 0.1.6: A faster graphics pipeline

Latest

Choose a tag to compare

@GiZcesi GiZcesi released this 13 Nov 12:17
OpenTricky-0 1 6-header-2560x1440

Seventh public release of OpenTricky: a faster graphics pipeline, and steadier over long sessions. Above 60 FPS, the game no longer waits for the graphics card to learn how much of each light halo is in view, and every draw costs the translation to Direct3D 11 less: in the heaviest scenes, up to 56% more frames per second than 0.1.5 without a frame rate limit, and on a 240 Hz screen they now hold 240 FPS where 0.1.5 fell short. A freeze after hours of play without restarting is fixed, the shaders the races need are built before the first race, the sound no longer crackles when the processor is busy, and at 60 FPS on a 60 Hz screen the controls answer about 5 ms sooner. Above 60 FPS, the trail in the snow and the snow sprays stay with the board. Keep VSync on: the launcher now says why when it's off. This version adds no setting, and races play out exactly as in 0.1.5. Guides and help are on opentricky.com.

💿 No disc image, music or video from the game is distributed. You need your own copy of the game: a disc image (.iso or .xiso) of SSX Tricky for the original Xbox, USA release.

Download

OpenTricky-0.1.6-win64.zip runs on Windows 10/11 64-bit with Direct3D 11, and on Linux and the Steam Deck through Proton. For a new install, extract it into an empty folder, start OpenTricky.exe and pick your disc image: click the disc label at the top, or the drop area, then choose from the SSX Tricky (USA) disc images found on this computer (Find my disc image), or browse for it. To check the download, use SHA256SUMS.txt and its signature, SHA256SUMS.txt.sig.

  • Coming from 0.1.2, 0.1.3, 0.1.4 or 0.1.5: update from the launcher. Your saves, your settings and your disc image are kept.
    • From 0.1.5, nothing in your settings moves: this version has no new setting and changes no preset.
    • From 0.1.4 or earlier, settings that match a preset (Recommended, Original Xbox or Steam Deck) follow that preset's current values, settings you chose yourself stay, and each setting your version didn't have takes the value of the closest preset. You also get everything that came in between: see the 0.1.5 and 0.1.4 release notes.
    • No update offered? The 0.1.4 and 0.1.5 launchers have Check now in Settings → Advanced → Updates. The 0.1.2 and 0.1.3 launchers look only once a day: close the launcher, delete update-cache.txt (next to settings.ini; deleting it is harmless), then start it again. With Skip launcher next time on, hold Shift (or Back / Select on a controller) while you start OpenTricky.exe to see the launcher.
  • Coming from 0.1.1: the 0.1.1 launcher can't install 0.1.6, so install it fresh, in a new folder. Saves in Documents\My Games\SSX Tricky\Saves stay where they are; if yours were inside the old folder (a Saves folder with portable.txt, or an hdd folder), copy that folder, and portable.txt, across. Leave settings.ini behind: pick your disc image again (and your save folder, if you had chosen one), remake your shortcuts (the game is bin\SSX Tricky.exe), then delete the old folder.

A faster graphics pipeline

Light halos no longer slow the game. The sun's glare, the lamps and the coloured lights are halos. For each one, the game asks the graphics card how much of it is in view, then reads the answer at the start of the next frame, and waits if it isn't there yet, as the original game does. Above 60 FPS, that answer only exists once OpenTricky has translated the whole frame and the card has drawn it, so the game and the translation took turns instead of working side by side. Now, when a halo's answer hasn't come back, the game goes on with that halo's own latest answer, as long as it is no more than two game steps old; a halo can then fade in or out a frame or two later than before. Only the halos' brightness uses these answers, never the race. At 60 FPS the game waits for the answer, as in the original game, and OpenTricky now sends the card the draws that come before the question in batches, as they are made, so the answer comes back sooner.

Lighter draw translation. A frame of SSX Tricky is thousands of draws, each one translated for Direct3D 11, and each now costs less: a draw's vertex streams are put in order in one pass instead of one search per stream, a texture lookup that repeats the one just made is reused, a texture that is already bound isn't bound again, and the translation's own switches are worked out once per frame instead of at every draw. The same draws, and the same picture.

When the frame rate drops below your screen's. Above 60 FPS with a frame rate limit, OpenTricky draws extra frames between the game's steps, on a steady beat set by your screen or by the limit. When a frame took longer than one beat, OpenTricky used to leave the beat before each game step empty, rather than risk showing that step late, and the picture before it stayed on screen for one more refresh. That beat now stays empty only when the game step's own picture would otherwise slip to the next one. In exchange, that picture can reach the screen up to half a beat later than before.

Without a frame rate limit. With Frame rate limit at Unlimited, OpenTricky draws extra frames between the game's steps as fast as it can. Before each step, it used to stop as soon as the next extra frame might end after the step was due, then sit idle until the step: those pauses made the slowest frames. It now draws that frame when, judging by how long recent frames took and how much that varied, it is at least as likely to help as to hold the step back. A game step can run a little later than before.

A faster build of the game. The game in the zip is now built with link-time optimisation, which lets the compiler work across all of its code at once: the same code, run faster.

Measured against 0.1.5 with the same settings, in the heaviest scenes we know of (Mesablanca and Pipedream in Showoff, Pipedream in the sun, Aloha Ice Jam in Showoff):

  • Without a frame rate limit: 49 to 56% more frames per second on average, and 23 to 35% higher 1% lows.
  • On a 240 Hz screen: Mesablanca and Pipedream in Showoff, Pipedream in the sun and Aloha Ice Jam in Showoff now hold 240 FPS, where 0.1.5 fell short, and 91 to 99% fewer frames are shown twice. Garibaldi (Race) holds 240 FPS with both versions.

Your gains depend on your PC.

Fixes

Stability

  • A freeze after hours of play: each time a track was unloaded, a part of it stayed in the game's memory, because the code that frees it had been left out of the recompilation since the first release. After hours of races without restarting the game, that memory ran out, and the game could freeze or crash, for example while loading a track. That code now runs, as in the original game, and the game's memory stays level however long you play.
  • A trick name written past its memory (in the original game's code): to show some trick names (on the Showoff results, for example), the game set aside room for the letters but not for the zero that ends them, and with some names it wrote just past that room. It now leaves room for it. Nothing on screen changes.
  • A rare draw command read half-written: one of the game's routines for simple render settings (blending, alpha test, depth test) announced a new command before writing it. On the console, the graphics chip never reads that far until it is told to; OpenTricky's translation reads as soon as the announcement comes. Above 60 FPS, about one to three times in a million frames, it read two stale words instead, and a few draws could get the wrong setting for a frame. It was never seen on screen; the routine now writes the command first, like all the others.

Above 60 FPS. The game itself runs at 60 steps a second, and OpenTricky draws the frames in between from two steps. These fixes change only those frames: at 60 FPS, and in Original Xbox, nothing changes.

  • The trail in the snow and the snow sprays: the board is drawn where it is at that instant, between two game steps, but the game lays its trail, and the rider's snow sprays, puffs and powder, at each step, from where the board is at the newer one. They ran a little ahead of the board, and in turns the trail's bright band could stick out in front of its nose. They now follow the board as it is drawn.
  • Sudden moves: when the game moves a rider at once, or turns their feet or board sharply in a single step (at the start and the finish of a race, and in some tricks), OpenTricky slid from one to the other over a few frames, through positions and poses the game never shows. The rider now changes at once, as at 60 FPS, and with Smoother legs in turns the smoothing starts again from the new pose. The rivalry icon above that rider moves with them.

Frame rate

  • A game moved to a 60 Hz screen: with Frame rate limit at Match screen (the Recommended value), or at a limit above your screen's with VSync on or Adaptive, the game follows your screen. Started on a faster screen and then moved to a 60 Hz one, or with that screen switched to 60 Hz, it kept drawing frames in between at 60 a second: up to one game step of extra delay, for no extra frame. It now plays as at 60, with the original game's timing, and goes back above 60 when the screen does. The other way round, see Known issues.

Picture

  • 16-bit textures (always on, in every preset, Original Xbox included): when their colours were widened to 8 bits, they were rounded down, and nearly half of the values came out one level in 255 too dark (on the ground, the snow and the rocks). They now get the nearest value. You won't see the difference, but the colours are exact.

Errors that said nothing

  • When the graphics can't start, or stop: if Direct3D 11 couldn't start (or the graphics card doesn't offer Direct3D feature level 11_0), the game showed a black window and was then reported as frozen; if the graphics driver stopped while you played, the picture stayed frozen and nothing said why. The game now writes a bug report and says what happened: in a message when you start it yourself, and on the launcher's LAST SESSION screen when you start it from the launcher.
  • When the launcher can't start (without OpenGL 3.3, for example): it now says so in a message, instead of closing or crashing without a word.
  • PLAY greyed out: when one of the launcher's pictures couldn't be read, PLAY stayed grey. It now depends only on your disc image, and the picture is just left out.

Better

  • Lower input delay at 60 FPS on 60 Hz and 120 Hz screens (in fullscreen): the game's frame timer and your screen's refreshes don't run at exactly the same rate, so the time between a frame being ready and the refresh that shows it drifted over each cycle, by up to a whole refresh on a 60 Hz screen. The timer now follows the refreshes, and that time stays short: about 5 ms less input delay on a 60 Hz screen, with a steadier rhythm, and about 2 ms less on a 120 Hz screen. At 240 Hz, nothing changes. The game's steps and their order stay the same; only the moments they come move.
  • Shaders built before the first race: the first time the game needs a shader, OpenTricky builds it for Direct3D 11, then keeps it on disk. On a new install, that build came during the first races, often right at the start, as a short stutter. The zip now comes with a list of the shaders the races use, and at the first start OpenTricky builds them in the background while you are in the menus (a few others are built there too, the first time). In our tests, no shader was built during a race.
  • Sound when the processor is busy: the game asks for two of its threads, the sound among them, to run ahead of the others, but those requests never reached Windows. They now do. In our tests, with the processor kept fully busy by other programs, the sound no longer crackles.
  • VSync, explained in the launcher: with VSync set to Off, a line under the setting now says what it costs (uneven motion and tearing) and that On adds very little input delay. On stays the value of every preset.

Known issues (short)

  • Without VSync, above 60 FPS: motion is less even than with VSync on, even at a higher frame rate, most of all with Frame rate limit at Unlimited. Keep VSync on (the default). We plan to improve this in a later version.
  • Controls above 60 FPS: they respond one game step (about 17 ms) later than at 60. Frame rate limit at 60 (Xbox) gives the original game's exact timing.
  • A game started on a 60 Hz screen (with Match screen, or with VSync on or Adaptive) doesn't follow a faster one: moved to it, or with the screen switched to a higher rate, it stays at 60 FPS. Restart the game there (the setting's help now says so).
  • Controllers: Xbox-style (XInput) ones work natively, and the DualShock 4 and DualSense with PlayStation controllers (experimental). For others, use Steam Input or DS4Windows, and choose PlayStation modern or PS2 original in Button style.
  • Proton Experimental (Linux, Steam Deck) may run slower: try Proton 10 or PortProton, and send us your logs.
  • Screens that don't report their refresh timing (the Steam Deck, some laptops): at 60 FPS on 60 Hz, frames can queue up and reach the screen later than in 0.1.3.
  • Smoother terrain seams leaves a few of the original game's seams visible, and gives the processor more to do on every frame.

All known issues: opentricky.com/known-issues.

Reporting bugs

Post in #bug-reports on the Discord, or open an issue, with your settings, your PC and SSX Tricky.log (or the zip from Settings → Advanced → Bug report → Prepare…, which the launcher also offers after a crash).

Thanks to everyone who reports bugs and tells us how the game runs on their PC, on Discord and on GitHub.

Build it yourself

From your own disc image, build.bat "<your .iso>" builds the game and the launcher. See Building from source.

Unofficial fan project, not affiliated with Electronic Arts or Microsoft. SSX and SSX Tricky are trademarks of Electronic Arts.