← Brewology.com

Vita Store › Games

VitaKotor2 v0.6.0 by pyjabox

Released Nov 14, 2026 · Games

Star Wars: Knights of the Old Republic II - The Sith Lords running natively on the PS Vita. Based on VitaKotor, it loads Aspyr's own Android libraries via the so-loader technique, with graphics on vitaGL and a custom FMOD audio backend over sceAudiodec and sceAudioOut. Bink cutscenes play through the game's embedded decoder with synchronized audio. Because the sequel is more demanding, the port adds performance work: vitaGL runs on its own CPU core, distant objects hidden behind walls are culled on the GPU, DXT textures are uploaded natively, music and voices are streamed, and the frame rate is capped at 30 FPS. Dynamic shadows and bloom passes are disabled. The buttons, analog sticks and the front touchscreen are supported. No game data is included: the port requires the files of the Android release.

Install on your Vita

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
KOTOR2.vpk
62c5b55b…27c9 · installs as KOTR00002
2.1 MB Download
QR code of the download link for KOTOR2_brewology_com.vpk Scan it with VitaShell. It downloads KOTOR2.vpk and asks to install it.

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

All versions (5)

Other ways to install

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

Screenshots

About VitaKotor2

VitaKotor2 v0.6.0 — Enemies that fight back, and a lighter engine

This release is about the AI and big fights. In large battles most enemies
used to stand idle, waiting seconds for their turn; they now take their turns,
and the AI's work costs less: scripts run in the port's own interpreter,
reactions that change nothing are skipped, and the AI waits less for the
drawing. The engine's calls, menus, animations and effects cost less too.
It also fixes saving during big fights, and mods' English-only lines that came
out blank in other languages. The release build was played on a physical Vita
over several sessions, through to Korriban.

The AI

Hardware, the battle of Khoonda on Dantooine (TSLRCM, 20+ fighters); each
change measured on and off in alternating 10 s windows.

  • Enemies take their turns. The engine ends an AI priority level as soon as an event is due, and every enemy turn queues shouts, so the enemies in combat stopped after one or two creatures whatever the budget: each enemy decided every 2–3 s. Beside the drawing, the AI now carries on past due events, their time no longer counts against its budget, and the budget follows the time the drawing leaves (from the engine's 10 ms up to six times that). Enemy decisions went from 1.5–2.6 to 5–15 a frame, attacks from 45–85 to 85–245 per 10 s, and one enemy decision from 4–5 ms to 1–2 ms.
  • Scripts run in the port's own NWScript interpreter: the engine's, transcribed, with its common stack operations done in place. Each script's set-up of its constants (720 instructions for the AI's main script, about 70% of everything the AI interpreted) is worked out once, checked against a real run, then copied in.
  • Shout reactions that do nothing are skipped. Every listener of every battle shout ran the AI's main script. The runs its bytecode shows change nothing, 35–57% of them in heavy fighting, are skipped, only for those two scripts byte for byte: about a third less script time for the AI.
  • The AI waits less for the drawing. The calls that made it wait most often (combat state, facing, camera, the combat message line, damage numbers) are queued until the drawing ends, and attack animations are looked up by the game thread at safe points of the drawing. The game thread waited 14.1 instead of 42.5 ms a frame for the AI; the queued messages save about 5 ms more.

Faster

  • Engine calls: libkotor2 is a shared library, so its calls to its own functions went through a call table. About 97,000 of them now go straight to the function (those to functions the port hooks keep the table): Telos frames of 62.2 instead of 67.8 ms, battle frames 7–11% shorter.
  • Action menus are rebuilt when something changes rather than every frame: 1.6 instead of 4.2 ms a frame in the battle.
  • Quaternion interpolation and name comparisons are 2–3 times faster, with the same answers.
  • Effects: procedural texture animation (energy fields, hyperspace) without a library call per random number: 2.9–3.2 instead of 6.2–7.0 ms a frame. Blaster sparks no longer test collisions with the scene (300–660 tests a frame, 6–13 ms). Particle drawing in the battle went from 15–31 to 8–16 ms a frame.
  • Animation: key searches, animation and table-column lookups are remembered (the engine's own answers, checked against it), and bone and light constants already sent to the GPU are not sent again (62–74% of them in the battle).
  • Trade-offs, each with a switch: creatures and objects out of view are animated one frame in three, those drawn beyond 20 m every other frame, and the engine's animation-detail distances are 6 and 15 m instead of 12 and 30 m. Their animation events can fire a frame or two late. Blaster sparks fly on through the floor, hidden by it, instead of bouncing.
  • Overall: the battle's first wave runs at 111–140 ms a frame (v0.5.8: about 158 ms, with most enemies idle), with 3–6 times as many enemy decisions.

Fixed

Saving during big fights sat on the SAVING screen: the save ran out of
memory. Every pending scripted event saved its own copy of its script (one
area's record reached 37 MB), the record grew by small fixed steps, and empty
strings were saved without a length, so loading could read a stray 18.9 MB
string. Events are now saved in the engine's own form without the copy, the
record grows by an eighth, and new room starts zeroed. A save that already
holds a 40 MB area still needs that memory to be saved again: load an older
one.

Mods' English-only text in another language. Player replies, item names
and other text that a mod has only in English came out blank instead of in
English, and a conversation whose replies mixed blank and translated lines
did not open. In French, the Sith Academy's detention terminal on Korriban
(M4-78EP) stopped opening after "ERROR: UNSPECIFIED". The English fallback
now applies whenever a text comes out empty, in every language and for every
mod. Checked on hardware at that terminal.

Resuming after the PS button: the README now describes TheFloW's optional
FdFix plugin, which
keeps the game's open files valid across a suspend.

Installation

  1. Install KOTOR2.vpk with VitaShell. The title ID is KOTR00002.
  2. Create ux0:data/kotor2/.
  3. Copy from your own copy of the Android version 2.0.4, using the 32-bit libraries from the APK's lib/armeabi-v7a/ folder (the README lists each file's exact size and SHA-256):
  • libkotor2.so
  • libObbVfs.so
  • libc++_shared.so
  • libminiz.so
  • libLzmaLib.so
  • main.213.com.aspyr.swkotorii.obb
  • patch.14.com.aspyr.swkotorii.obb
  • the APK assets/ directory
  1. Install and enable kubridge.skprx.
  2. Place libshacccg.suprx in ur0:data/.
  3. Optionally, mods in ux0:data/kotor2/mods/, voice packs in ux0:data/kotor2/localized/, and the FdFix plugin (see the README).

Upgrading from v0.5.2 or later: install the VPK over the old one.
Game data, saves, mods, voice packs, the chosen language and the shader cache
stay as they are.
From v0.5.1 or older, see also the v0.5.2 notes: the first launch asks for a
language.

Known issues and limitations

  • Very large fights are still slow: the battle of Khoonda with TSLRCM runs at about 7–9 FPS, now mostly drawing the blaster fire and effects.
  • A black screen after the militia's retreat at Khoonda was seen once in about five test runs of the battle: the retreat's conversation never started, and the screen stayed black while the game kept running. Not seen since, and the cause is not known yet. If it happens, load a save from before the retreat.
  • The menu before the game is in English.
  • Mods in another language: what a mod has only in English shows in English, voice lines added by mods are English (they were never dubbed), and a mod's own voice-line and lip-sync files are used instead of a voice pack's (TSLRCM: 4 lines and the lip sync of 9 areas). Text a mod adds only to the English talk table, rather than to its own files, can still be blank. Details in the README.
  • With mods, launches take about 1 s longer while they are indexed, and the first launch in a new language about 2 s more to build its talk table.
  • Noise behind the sound in busy scenes, such as Telos. The decoders and the mix were checked and are clean; the cause is not known yet (issue #5).
  • About one launch in three takes about 11 s longer, in the engine's scan of dlc/. The cause is not known yet.
  • Shorter hitches remain (usually 0.12–0.23 s, occasionally more) when new content is first read from the memory card, at about 10 MB/s: the minimap's first draw, dialogue entries and their voices, creatures spawned by scripts.
  • Loading-screen images still take about 0.1–0.35 s each.
  • Heavy scenes remain CPU-bound, mostly in the engine's per-object rendering work.
  • Visual changes: no dynamic shadows, no bloom passes, and blaster sparks don't bounce. Rooms keep their baked lighting.
  • Less frequent updates: idle creatures, placeables, doors and items get their AI update every third frame; animation trade-offs as above. Nothing was noticed in testing.
  • One frame of extra latency: the GL worker lets the game run up to one frame ahead, and the AI's decisions reach the screen one frame later. An object stepping out from cover can appear up to three frames late (occlusion culling).
  • Touch: only the front touchscreen is used. The game keeps its controller layout, so its touch-only on-screen controls are not shown.
  • First launch: it can take about two minutes while archives are scanned and shaders compile, and the loading screen can sit still for much of it.
  • Shader cache: if a warm launch black-screens, remove ux0:data/shader_cache/KOTR00002/ and relaunch.
  • No complete playthrough certified yet. Trophies, cloud saves and online features are unavailable.

Switches

Create the file in ux0:data/kotor2/ and relaunch; delete it to go back.

  • New: each of these files turns one v0.6.0 change off, going back to how v0.5.8 did it:
  • nwvm_mode.txt containing 0: the engine's own script interpreter.
  • dialogue_mode.txt containing 0: every shout reaction runs.
  • spark_collision.txt containing 1: blaster sparks bounce again (up to 13 ms a frame in big fights).
  • part_collide_mode.txt containing 0: the engine's own particle box test.
  • anim_mode.txt containing 0: no remembered animation lookups.
  • anim_offscreen.txt containing 0: everything out of view animated every frame; anim_far.txt containing 0 (or a distance in metres instead of 20): distant creatures animated every frame; anim_depth.txt containing 0: the engine's animation-detail distances.
  • plt_mode.txt containing 0: the engine's calls through its call table.
  • menu_mode.txt containing 0: action menus rebuilt every frame.
  • leaf_mode.txt containing 0: the engine's own interpolation and name comparison.
  • proc_mode.txt containing 0: the engine's own procedural texture animation.
  • slim_mode.txt containing 0: pending events saved with their script's copy (saves in big fights grow by tens of MB and can run out of memory).
  • gff_mode.txt containing 0: the engine's own save writer and string reader (also turns off the slim saves).
  • From v0.5.8: ai_thread.txt, aslw_mode.txt, offload_mode.txt, scene_mode.txt, path_mode.txt and script_mode.txt containing 0 go back to how v0.5.7 did each.
  • ai_mode.txt containing 0: the game's own AI loop, with no throttle and no AI caches (slower in busy areas). Containing a number from 1 to 65: the AI's base time budget in milliseconds (the engine's is 10).
  • touch_mode.txt containing 0: buttons only, as in v0.4.2.
  • loadscreen_mode.txt containing 0: black screen until the legal screen, as in v0.4.2.
  • patcher_mode.txt containing 0: vitaGL's vertex-program requests go straight to the shader patcher and nothing is freed, as in v0.4.2 (the pool stays at 4 MB).
  • fps_cap.txt containing 0: no 30 FPS cap. LockFramerate=1 under [Graphics Options] in swkotor2.ini then caps again, and V-Sync=0 turns vsync off.
  • room_distance.txt containing a distance in metres: rooms beyond it are not drawn (up to about 25% faster where long views open, with distant geometry missing).
  • glw_mode.txt containing 0: vitaGL on the game thread, as in v0.2.0.
  • dxt_mode.txt containing 0: DXT textures decoded on the CPU, as in v0.3.0.
  • mipgen_mode.txt containing 0: every mip chain built by the engine, as in v0.3.0.

This release contains no copyrighted game code or data.

KOTOR2.vpk SHA-256: 62c5b55b48abd07048237a3fa2e8131bdc4dfd7d834c829e2f6d82552ff827c9

Release notes

v0.6.0 · KOTOR2.vpk · Nov 14, 2026

VitaKotor2 v0.6.0 — Enemies that fight back, and a lighter engine

This release is about the AI and big fights. In large battles most enemies
used to stand idle, waiting seconds for their turn; they now take their turns,
and the AI's work costs less: scripts run in the port's own interpreter,
reactions that change nothing are skipped, and the AI waits less for the
drawing. The engine's calls, menus, animations and effects cost less too.
It also fixes saving during big fights, and mods' English-only lines that came
out blank in other languages. The release build was played on a physical Vita
over several sessions, through to Korriban.

The AI

Hardware, the battle of Khoonda on Dantooine (TSLRCM, 20+ fighters); each
change measured on and off in alternating 10 s windows.

  • Enemies take their turns. The engine ends an AI priority level as soon as an event is due, and every enemy turn queues shouts, so the enemies in combat stopped after one or two creatures whatever the budget: each enemy decided every 2–3 s. Beside the drawing, the AI now carries on past due events, their time no longer counts against its budget, and the budget follows the time the drawing leaves (from the engine's 10 ms up to six times that). Enemy decisions went from 1.5–2.6 to 5–15 a frame, attacks from 45–85 to 85–245 per 10 s, and one enemy decision from 4–5 ms to 1–2 ms.
  • Scripts run in the port's own NWScript interpreter: the engine's, transcribed, with its common stack operations done in place. Each script's set-up of its constants (720 instructions for the AI's main script, about 70% of everything the AI interpreted) is worked out once, checked against a real run, then copied in.
  • Shout reactions that do nothing are skipped. Every listener of every battle shout ran the AI's main script. The runs its bytecode shows change nothing, 35–57% of them in heavy fighting, are skipped, only for those two scripts byte for byte: about a third less script time for the AI.
  • The AI waits less for the drawing. The calls that made it wait most often (combat state, facing, camera, the combat message line, damage numbers) are queued until the drawing ends, and attack animations are looked up by the game thread at safe points of the drawing. The game thread waited 14.1 instead of 42.5 ms a frame for the AI; the queued messages save about 5 ms more.

Faster

  • Engine calls: libkotor2 is a shared library, so its calls to its own functions went through a call table. About 97,000 of them now go straight to the function (those to functions the port hooks keep the table): Telos frames of 62.2 instead of 67.8 ms, battle frames 7–11% shorter.
  • Action menus are rebuilt when something changes rather than every frame: 1.6 instead of 4.2 ms a frame in the battle.
  • Quaternion interpolation and name comparisons are 2–3 times faster, with the same answers.
  • Effects: procedural texture animation (energy fields, hyperspace) without a library call per random number: 2.9–3.2 instead of 6.2–7.0 ms a frame. Blaster sparks no longer test collisions with the scene (300–660 tests a frame, 6–13 ms). Particle drawing in the battle went from 15–31 to 8–16 ms a frame.
  • Animation: key searches, animation and table-column lookups are remembered (the engine's own answers, checked against it), and bone and light constants already sent to the GPU are not sent again (62–74% of them in the battle).
  • Trade-offs, each with a switch: creatures and objects out of view are animated one frame in three, those drawn beyond 20 m every other frame, and the engine's animation-detail distances are 6 and 15 m instead of 12 and 30 m. Their animation events can fire a frame or two late. Blaster sparks fly on through the floor, hidden by it, instead of bouncing.
  • Overall: the battle's first wave runs at 111–140 ms a frame (v0.5.8: about 158 ms, with most enemies idle), with 3–6 times as many enemy decisions.

Fixed

Saving during big fights sat on the SAVING screen: the save ran out of
memory. Every pending scripted event saved its own copy of its script (one
area's record reached 37 MB), the record grew by small fixed steps, and empty
strings were saved without a length, so loading could read a stray 18.9 MB
string. Events are now saved in the engine's own form without the copy, the
record grows by an eighth, and new room starts zeroed. A save that already
holds a 40 MB area still needs that memory to be saved again: load an older
one.

Mods' English-only text in another language. Player replies, item names
and other text that a mod has only in English came out blank instead of in
English, and a conversation whose replies mixed blank and translated lines
did not open. In French, the Sith Academy's detention terminal on Korriban
(M4-78EP) stopped opening after "ERROR: UNSPECIFIED". The English fallback
now applies whenever a text comes out empty, in every language and for every
mod. Checked on hardware at that terminal.

Resuming after the PS button: the README now describes TheFloW's optional
FdFix plugin, which
keeps the game's open files valid across a suspend.

Installation

  1. Install KOTOR2.vpk with VitaShell. The title ID is KOTR00002.
  2. Create ux0:data/kotor2/.
  3. Copy from your own copy of the Android version 2.0.4, using the 32-bit libraries from the APK's lib/armeabi-v7a/ folder (the README lists each file's exact size and SHA-256):
  • libkotor2.so
  • libObbVfs.so
  • libc++_shared.so
  • libminiz.so
  • libLzmaLib.so
  • main.213.com.aspyr.swkotorii.obb
  • patch.14.com.aspyr.swkotorii.obb
  • the APK assets/ directory
  1. Install and enable kubridge.skprx.
  2. Place libshacccg.suprx in ur0:data/.
  3. Optionally, mods in ux0:data/kotor2/mods/, voice packs in ux0:data/kotor2/localized/, and the FdFix plugin (see the README).

Upgrading from v0.5.2 or later: install the VPK over the old one.
Game data, saves, mods, voice packs, the chosen language and the shader cache
stay as they are.
From v0.5.1 or older, see also the v0.5.2 notes: the first launch asks for a
language.

Known issues and limitations

  • Very large fights are still slow: the battle of Khoonda with TSLRCM runs at about 7–9 FPS, now mostly drawing the blaster fire and effects.
  • A black screen after the militia's retreat at Khoonda was seen once in about five test runs of the battle: the retreat's conversation never started, and the screen stayed black while the game kept running. Not seen since, and the cause is not known yet. If it happens, load a save from before the retreat.
  • The menu before the game is in English.
  • Mods in another language: what a mod has only in English shows in English, voice lines added by mods are English (they were never dubbed), and a mod's own voice-line and lip-sync files are used instead of a voice pack's (TSLRCM: 4 lines and the lip sync of 9 areas). Text a mod adds only to the English talk table, rather than to its own files, can still be blank. Details in the README.
  • With mods, launches take about 1 s longer while they are indexed, and the first launch in a new language about 2 s more to build its talk table.
  • Noise behind the sound in busy scenes, such as Telos. The decoders and the mix were checked and are clean; the cause is not known yet (issue #5).
  • About one launch in three takes about 11 s longer, in the engine's scan of dlc/. The cause is not known yet.
  • Shorter hitches remain (usually 0.12–0.23 s, occasionally more) when new content is first read from the memory card, at about 10 MB/s: the minimap's first draw, dialogue entries and their voices, creatures spawned by scripts.
  • Loading-screen images still take about 0.1–0.35 s each.
  • Heavy scenes remain CPU-bound, mostly in the engine's per-object rendering work.
  • Visual changes: no dynamic shadows, no bloom passes, and blaster sparks don't bounce. Rooms keep their baked lighting.
  • Less frequent updates: idle creatures, placeables, doors and items get their AI update every third frame; animation trade-offs as above. Nothing was noticed in testing.
  • One frame of extra latency: the GL worker lets the game run up to one frame ahead, and the AI's decisions reach the screen one frame later. An object stepping out from cover can appear up to three frames late (occlusion culling).
  • Touch: only the front touchscreen is used. The game keeps its controller layout, so its touch-only on-screen controls are not shown.
  • First launch: it can take about two minutes while archives are scanned and shaders compile, and the loading screen can sit still for much of it.
  • Shader cache: if a warm launch black-screens, remove ux0:data/shader_cache/KOTR00002/ and relaunch.
  • No complete playthrough certified yet. Trophies, cloud saves and online features are unavailable.

Switches

Create the file in ux0:data/kotor2/ and relaunch; delete it to go back.

  • New: each of these files turns one v0.6.0 change off, going back to how v0.5.8 did it:
  • nwvm_mode.txt containing 0: the engine's own script interpreter.
  • dialogue_mode.txt containing 0: every shout reaction runs.
  • spark_collision.txt containing 1: blaster sparks bounce again (up to 13 ms a frame in big fights).
  • part_collide_mode.txt containing 0: the engine's own particle box test.
  • anim_mode.txt containing 0: no remembered animation lookups.
  • anim_offscreen.txt containing 0: everything out of view animated every frame; anim_far.txt containing 0 (or a distance in metres instead of 20): distant creatures animated every frame; anim_depth.txt containing 0: the engine's animation-detail distances.
  • plt_mode.txt containing 0: the engine's calls through its call table.
  • menu_mode.txt containing 0: action menus rebuilt every frame.
  • leaf_mode.txt containing 0: the engine's own interpolation and name comparison.
  • proc_mode.txt containing 0: the engine's own procedural texture animation.
  • slim_mode.txt containing 0: pending events saved with their script's copy (saves in big fights grow by tens of MB and can run out of memory).
  • gff_mode.txt containing 0: the engine's own save writer and string reader (also turns off the slim saves).
  • From v0.5.8: ai_thread.txt, aslw_mode.txt, offload_mode.txt, scene_mode.txt, path_mode.txt and script_mode.txt containing 0 go back to how v0.5.7 did each.
  • ai_mode.txt containing 0: the game's own AI loop, with no throttle and no AI caches (slower in busy areas). Containing a number from 1 to 65: the AI's base time budget in milliseconds (the engine's is 10).
  • touch_mode.txt containing 0: buttons only, as in v0.4.2.
  • loadscreen_mode.txt containing 0: black screen until the legal screen, as in v0.4.2.
  • patcher_mode.txt containing 0: vitaGL's vertex-program requests go straight to the shader patcher and nothing is freed, as in v0.4.2 (the pool stays at 4 MB).
  • fps_cap.txt containing 0: no 30 FPS cap. LockFramerate=1 under [Graphics Options] in swkotor2.ini then caps again, and V-Sync=0 turns vsync off.
  • room_distance.txt containing a distance in metres: rooms beyond it are not drawn (up to about 25% faster where long views open, with distant geometry missing).
  • glw_mode.txt containing 0: vitaGL on the game thread, as in v0.2.0.
  • dxt_mode.txt containing 0: DXT textures decoded on the CPU, as in v0.3.0.
  • mipgen_mode.txt containing 0: every mip chain built by the engine, as in v0.3.0.

This release contains no copyrighted game code or data.

KOTOR2.vpk SHA-256: 62c5b55b48abd07048237a3fa2e8131bdc4dfd7d834c829e2f6d82552ff827c9

Full changelog

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