← Brewology.com

Vita Store › Games › VitaKotor2

VitaKotor2 changelog

v0.6.0 · 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

v0.5.8 · Nov 3, 2026

VitaKotor2 v0.5.8 — More cores, and long sessions fixed

This release puts the Vita's other two cores to work: the AI now runs beside
the drawing, and the game's GL translation runs on the GL worker. It also
fixes saving and the save list failing after a long session with a voice
pack, and a crash in Telos's cantina. The new threading was played for
several hours on a physical Vita; the two last fixes were checked in Vita3K.

Faster

Hardware, Telos; each change was measured on and off in alternating 10 s
windows.

  • The AI runs on core 1 while the scene is drawn: 22.3 against 19.5 FPS. Wherever the AI reaches into the client side, it waits for the drawing to end, so the two never touch the same data.
  • The game's GL translation (ASLgl) runs on the GL worker: 18.4 against 14.6 FPS.
  • **Text widths are cached, and animated textures (water, ripples) are rebuilt on core 1:** 21.5 against 17.5 FPS.
  • Smaller savings: light lists without repeated scans (about 1.5 ms a frame), and creatures not drawn in a frame animated one frame in three (about 0.7 ms).
  • A periodic hitch in Telos: a creature with no clear path re-planned it every few seconds, about 110 ms a try. Searches that fail on the walkmesh alone are now remembered until the next load: worst frames of 60–92 ms instead of 165–194 ms.
  • Large fights: compiled scripts stay in memory instead of being read again on every run. In the battle of Khoonda on Dantooine (TSLRCM, 20+ fighters; issue #4) this halves the AI's work: 55% more creatures are updated each frame, and frames take 158 instead of 192 ms. The battle is still slow (see below).

Fixed

**Saving, the save list and the voices failing after a long session with a
voice pack.** After one to two hours, saving failed, Load Game listed no
saves, and the voices switched to English. The game forgets to close the file
of every dialogue line it plays. v0.5.6 kept loose voice lines in RAM, which
only delayed the problem: after about 512 lines, all 64 files a Vita app may
hold were taken. The loader now closes what the game forgets. Voices from
the game's archive (English) leaked too, more slowly.

A crash in Telos's cantina, which looked like a black screen at 30 FPS
with no sound, and made saves in that module look as if they would not load.
The game asked the loader for a C library function by name (wcslen), which
the loader did not provide. Saves made there were never damaged.

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/ and voice packs in ux0:data/kotor2/localized/ (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 slow: the battle of Khoonda with TSLRCM runs at about 6 FPS. The engine gives its AI 10 ms a frame; in such fights that runs out, and creatures of lower priority act only every few frames, so some seem idle. ai_mode.txt containing a number of milliseconds (1 to 65) raises the budget, at a cost in frame rate.
  • 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). 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 and no bloom passes. Rooms keep their baked lighting.
  • Idle objects update less often: idle creatures, placeables, doors and items get their AI update every third frame, and creatures not drawn in a frame are animated one frame in three. 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 containing 0 turns one v0.5.8 change off, going back to how v0.5.7 did it:
  • ai_thread.txt: the AI on the game thread.
  • aslw_mode.txt: ASLgl on the game thread.
  • offload_mode.txt: text widths and animated textures on the game thread.
  • scene_mode.txt: the engine's own light lists, and every creature animated every frame.
  • path_mode.txt: no failed path search remembered.
  • script_mode.txt: scripts read from the archive on every run.
  • 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 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: a8dddf4ac000e38afd25dd07afcf5421443cd0be99ee6520ecc6643204f66950

v0.5.7 · Oct 16, 2026

VitaKotor2 v0.5.7 — German and Italian

This release fixes German and Italian, which were swapped, and closes two
races in the sound mixer. German was tested on a physical Vita.

Fixed

German and Italian were swapped
(issue #1). Since v0.5.2,
choosing DEUTSCH ran the game in Italian, and ITALIANO ran it in German. Only
the first loading screen was in the right language, and a German patch in
dlc/ was never read, because the game looked for the Italian folder. The
loader gave the game the numbering of the talk tables' headers instead of the
Android app's. English, French and Spanish were not affected. A language
already chosen needs no change: if you picked DEUTSCH, the game now starts in
German. The boot menu now lists ITALIANO before DEUTSCH.

Two rare races in the sound mixer. A track replayed while the mixer was
decoding could carry on from where it stopped instead of starting over. A
stream released while 128 others were waiting to be closed was closed while
the mixer could still be decoding it.

Also new

  • The log now says how often the audio port ran dry, and the least sound it held, in each 10 s window with a problem ([snd-gap] lines). This helps with the noise in busy scenes (issue #5), which is still open.

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/ and voice packs in ux0:data/kotor2/localized/ (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. If you created ai_mode.txt to get past a door, you can
delete it.
From v0.5.1 or older, see also the v0.5.2 notes: the first launch asks for a
language.

Known issues and limitations

  • 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). 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 and no bloom passes. Rooms keep their baked lighting.
  • Idle objects update less often: idle creatures, placeables, doors and items get their AI update every third frame. Nothing was noticed in testing.
  • One frame of extra latency: the GL worker lets the game run up to one frame ahead. 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.

  • ai_mode.txt containing 0: the game's own AI loop, with no throttle and no AI caches (slower in busy areas).
  • 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: 170122bccd91fe27d2d8df33f05110e89a5296b45b2899d21e5c05299bd247a5

v0.5.6 · Oct 15, 2026

No notes for this release.

v0.5.0 · Oct 9, 2026

No notes for this release.