← Brewology.com

Vita Store › Games

VitaKotor v0.5.1-multicore.2 by ScoobyDouche

Released Nov 1, 2026 · Games
267 downloads here · Developer site

Star Wars: Knights of the Old Republic running natively on the PS Vita. Loads Aspyr's own Android libraries via the so-loader technique, with graphics on vitaGL and a from-scratch FMOD audio backend over sceAudiodec. Playable Requires your own copy of the Android release.

Install on your Vita

This release has 2 builds of the app. Install one (the developer's notes say which): they install as the same app. In VitaShell, hold Left on the D-pad and press ○ to open the QR code scanner, then point the Vita's back camera at the code.

FileSize
KOTOR-nolog.vpk
bf203c62…bc97 · installs as KOTR00001
2.6 MB Download
QR code of the download link for KOTOR-nolog_brewology_com.vpk Scan it with VitaShell. It downloads KOTOR-nolog.vpk and asks to install it.
KOTOR.vpk
aa34027b…4305 · installs as KOTR00001
2.6 MB Download
QR code of the download link for KOTOR_brewology_com.vpk Scan it with VitaShell. It downloads KOTOR.vpk and asks to install it.

Homebrew needs HENkaku, h-encore, HENlo or Ensō. New to Vita homebrew? Start here.

All versions (7)

Other ways to install

Copy one to the memory card: copy the one you want to ux0: (USB or FTP in VitaShell), open it in VitaShell and press ✕ to install it.

Screenshots

About VitaKotor

A test pre-release from the multicore branch, aimed at playing with Shadows, Grass, Frame Buffer and 32-bit textures all on. It builds on multicore.1: the AI now runs alongside the 3D scene far more of the time, and one graphics stall the port caused itself is gone.

What changed

  • The AI waits far less for the scene. In multicore.1 the AI often had to stop partway and wait for the drawing to finish, mostly when it started a character animation or loaded a script. Animations are now queued and played the moment the drawing is done, and script loading shares the game's resource manager through a lock instead of stopping. In the Upper City the wait after each frame's drawing dropped from 3.8 ms to 2.0 ms; in the Lower City to 0.2 ms.
  • A texture update no longer stalls the frame. The game updates one texture every frame, and each update made the game core wait for the graphics core to finish everything before it: up to 3 ms a frame. It is now queued like every other draw call.
  • New option: ShadowDistance. How far away, in metres, creatures still cast shadows when Shadows is on. The default is the original 35; 20 saves about 1 ms in the Upper City crowds.
  • KOTOR-nolog.vpk: an optional build with diagnostic logging disabled. Install it in place of KOTOR.vpk if you prefer not to have a log file written.

What to expect

With every graphics option on and 32-bit textures, the Taris Lower City now averages about 34 ms a frame, right at the edge of the 30 fps lock: most frames make it, some show for an extra refresh. The Upper City South crowds still run at about 17 fps and the Undercity at about 19: those areas draw 500 to 800 objects a frame, and that work is the game's own code on one core, whatever the settings. With FrameLock at 30, frames that miss the lock are shown for an extra refresh; FrameLock=20 gives an even 20 in those areas if you prefer steady to fast.

Updating

Install KOTOR.vpk over your current one. Your files in ux0:data/kotor/, your saves and your mods stay as they are. If anything goes wrong, set ServerOverlap=0 under [Vita Options] in swkotor.ini, or reinstall multicore.1 or v0.5.0 from the releases page.

Honest limits

  • Tested for one evening in Taris. Several sessions in the Upper City, Lower City and Undercity with every graphics option on, with no crashes. The last small widening of the animation and lock changes has not been played yet.
  • 32-bit textures fill the Vita's video memory in the busy Taris areas, and the rest spills into regular memory. It has not caused trouble so far, but the bigger outdoor areas have not been tried at 32-bit.
  • Mod sets have not been tried with this build.
  • The loading screen runs twice when you load a save (issue #13), and the rare crash after an area-change auto-save (issue #12) is still open.

Everything else from multicore.1 still applies

The AI runs on its own core while the scene draws, the graphics calls run on another, and ServerOverlap=0 turns the AI overlap off.

You need your own copy of the game

This is a loader, not a game. It needs the Android release's main and patch .obb files, which you must own.

Something broken?

Open an issue with ux0:data/kotor/log.txt attached, say where in the game it happened, and whether it still happens with ServerOverlap=0.

Release notes

v0.5.1-multicore.2 · KOTOR-nolog.vpk · Nov 1, 2026

A test pre-release from the multicore branch, aimed at playing with Shadows, Grass, Frame Buffer and 32-bit textures all on. It builds on multicore.1: the AI now runs alongside the 3D scene far more of the time, and one graphics stall the port caused itself is gone.

What changed

  • The AI waits far less for the scene. In multicore.1 the AI often had to stop partway and wait for the drawing to finish, mostly when it started a character animation or loaded a script. Animations are now queued and played the moment the drawing is done, and script loading shares the game's resource manager through a lock instead of stopping. In the Upper City the wait after each frame's drawing dropped from 3.8 ms to 2.0 ms; in the Lower City to 0.2 ms.
  • A texture update no longer stalls the frame. The game updates one texture every frame, and each update made the game core wait for the graphics core to finish everything before it: up to 3 ms a frame. It is now queued like every other draw call.
  • New option: ShadowDistance. How far away, in metres, creatures still cast shadows when Shadows is on. The default is the original 35; 20 saves about 1 ms in the Upper City crowds.
  • KOTOR-nolog.vpk: an optional build with diagnostic logging disabled. Install it in place of KOTOR.vpk if you prefer not to have a log file written.

What to expect

With every graphics option on and 32-bit textures, the Taris Lower City now averages about 34 ms a frame, right at the edge of the 30 fps lock: most frames make it, some show for an extra refresh. The Upper City South crowds still run at about 17 fps and the Undercity at about 19: those areas draw 500 to 800 objects a frame, and that work is the game's own code on one core, whatever the settings. With FrameLock at 30, frames that miss the lock are shown for an extra refresh; FrameLock=20 gives an even 20 in those areas if you prefer steady to fast.

Updating

Install KOTOR.vpk over your current one. Your files in ux0:data/kotor/, your saves and your mods stay as they are. If anything goes wrong, set ServerOverlap=0 under [Vita Options] in swkotor.ini, or reinstall multicore.1 or v0.5.0 from the releases page.

Honest limits

  • Tested for one evening in Taris. Several sessions in the Upper City, Lower City and Undercity with every graphics option on, with no crashes. The last small widening of the animation and lock changes has not been played yet.
  • 32-bit textures fill the Vita's video memory in the busy Taris areas, and the rest spills into regular memory. It has not caused trouble so far, but the bigger outdoor areas have not been tried at 32-bit.
  • Mod sets have not been tried with this build.
  • The loading screen runs twice when you load a save (issue #13), and the rare crash after an area-change auto-save (issue #12) is still open.

Everything else from multicore.1 still applies

The AI runs on its own core while the scene draws, the graphics calls run on another, and ServerOverlap=0 turns the AI overlap off.

You need your own copy of the game

This is a loader, not a game. It needs the Android release's main and patch .obb files, which you must own.

Something broken?

Open an issue with ux0:data/kotor/log.txt attached, say where in the game it happened, and whether it still happens with ServerOverlap=0.

Full changelog

Something wrong with this listing? Report a problem · Are you the developer? Claim this listing