VitaKotor changelog
v0.5.1-multicore.2 · 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 original35;20saves about 1 ms in the Upper City crowds. - KOTOR-nolog.vpk: an optional build with diagnostic logging disabled. Install it in place of
KOTOR.vpkif 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.
v0.5.1-multicore.1 · Oct 31, 2026
A test pre-release from the multicore branch. The game's AI now runs on a second CPU core while the 3D scene draws, instead of after it. It has had two short test sessions, so it is a pre-release for anyone who wants to try it early.
What changed
- The AI runs alongside the graphics. Every frame the game used to draw the scene, then run the AI for every creature in the area, one after the other on the same core. The AI now starts on another core as the scene starts drawing, so the two overlap. In busy areas that takes about 3.5 ms off each frame, on top of v0.5.0's graphics core.
- It can be switched off. Add
ServerOverlap=0under[Vita Options]inux0:data/kotor/swkotor.inito go back to the old order without reinstalling. - Two sound fixes: a race in the mixer could make a replayed track carry on from where it last stopped, and a released stream could be closed while it was still being decoded. Both found in VitaKotor2.
- A graphics fix: a deleted buffer stayed bound, so a later draw could read freed memory. It is now unbound first, as OpenGL requires.
- KOTOR-nolog.vpk: an optional build with diagnostic logging disabled. Install it in place of
KOTOR.vpkif you prefer not to have a log file written.
How it stays safe
The AI sometimes reaches straight into the things being drawn: it moves models, starts animations and loads scripts. Around 1,350 of the game's drawing and resource functions are guarded, and if the AI reaches one while the scene is drawing, it waits until the drawing is done and then carries on. Area changes, saves, loads and quitting all finish the AI's frame first. A few functions that only store a position or look up a resource are let through, after checking what they do.
Why only 3.5 ms
The AI is about 5.5 ms of a busy frame, and in two thirds of frames it still has to wait at one of the guards before it finishes. The 3D scene itself, about 30 ms, is the game's own code on one core and is unchanged.
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, or reinstall v0.5.0 from the releases page.
Honest limits
- Tested for two short sessions, not a playthrough. Busy areas with full graphics settings on, with no crashes and nothing wrong on screen.
- The AI reacts one frame later, about 33 ms. It has not been noticeable in play.
- 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 v0.5.0 still applies
The graphics calls run on their own core, setup mistakes show a message, the 1.0.10, 1.0.9 build 54 and 1.0.7 / 1.0.71 APKs work, and frames are locked to 30 fps.
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.
v0.5.0 · Oct 24, 2026
VitaKotor v0.5.0 — a second core for the graphics
A pre-release. The game's graphics calls now run on their own CPU core, which makes busy scenes faster and smoother. It has had one evening of testing, so it is marked pre-release until more people have played on it.
What changed
- The graphics calls run on a second core. Until now the core running the game also did all of vitaGL's work for every object it drew, several hundred times a frame in busy areas. That work now goes to a thread on another core, and the game core moves on to the next object. In the Upper City and the Endar Spire fights each busy frame takes about a tenth less time, and motion feels smoother.
- Setup mistakes show a message instead of a black screen. A missing
kubridge,libshacccg,.sofile or.obbnow opens a message box saying what is missing and where it goes. - 16-bit textures could come out corrupted when the game re-uploaded a texture, or updated one on a texture unit it had not just bound. Fixed.
- Smaller fixes: the missing-OBB message is shorter, and a few internal clean-ups in the loader's hooks and thread handling.
- KOTOR-nolog.vpk: an optional build with diagnostic logging disabled. Install it in place of
KOTOR.vpkif you prefer not to have a log file written.
Why only a tenth
The graphics library was not most of the frame. Most of a busy frame is the game's own code working out what is on screen and preparing each object, and that still runs on one core. PSVshell will still show that core at 100%: it is doing more frames in the same time, not less work. What this release moves off it is everything the port itself controls.
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, v0.4.3 is still on the releases page and installs the same way.
Honest limits
- Tested for one evening, not a playthrough. Several sessions in the Taris Upper City and save loads, with no crashes and nothing wrong on screen. The rest of the game has not been played on this build yet, which is why it is a pre-release.
- Mod sets have not been tried with this build.
- Busy areas still sit near 20 fps with a crowd on screen; the remaining time is the game's own code.
- The loading screen runs twice when you load a save (issue #13). It fills once without a tip, then again quickly with one. It happens in v0.4.3 too, and the save loads normally.
- The rare crash after an area-change auto-save (issue #12) is still open.
Everything else from v0.4.3 still applies
The 1.0.10, 1.0.9 build 54 and 1.0.7 / 1.0.71 APKs work, Griff spawns in the Sand People Enclave, texture quality is picked from the MODS button, busy areas have 96 sound channels, and frames are locked to 30 fps.
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, and say where in the game it happened.
