JK2 mode: Could not find string package 'KEYNAMES'

[Raz0r]

Clean install of JK2

Debug compile of OpenJK with JK2 support from latest git

Dropped openjk_sp.x86.exe and rdsp-vanilla_x86.dll into /JK2/GameData

Launched with: openjk_sp.x86.exe +set com_jk2 1

Tried with/without OpenJK's jk2gamex86.dll in both GameData and OpenJK with +set fs_game "OpenJK" - no difference.

 

 

(debug)OpenJK: v1.0.1.1 win-x86-debug Nov  1 2013
Initialising zone memory .....
----- FS_Startup -----
Current search path:
C:\Users\Razish\Documents\My Games\OpenJK\base
G:\Games\JK2\GameData\base\mapextras2.pk3 (28 files)
G:\Games\JK2\GameData\base\mapextras.pk3 (49 files)
G:\Games\JK2\GameData\base\assets1.pk3 (8011 files)
G:\Games\JK2\GameData\base\assets0.pk3 (6674 files)
G:\Games\JK2\GameData\base
 
----------------------
14762 files in pk3 files
execing default.cfg
execing openjk_sp.cfg
couldn't exec autoexec_sp.cfg
Running Jedi Outcast Mode
 
------- Input Initialization -------
Skipping check for DirectInput
Joystick is not active.
------------------------------------
----- Client Initialization -----
Could not open string package 'KEYNAMES'

 

jk2sp.exe works fine. All the assets are there and usable (and being loaded), JK2 support is being enabled.

 

Any ideas how to fix it? Other people seem to be able to run it okay.

[ensiform]

Perhaps if your install was from 1.04/newest you wouldn't have this issue.

 

Steam has assets2.pk3 (contains this file) and assets5.pk3

 

Our engine is based off of whatever is newest, therefore it requires assets of the newest.  It seems they switched to the keynames.sp required code in patch 1.03 from what I could find on some of the outcast forks.

[Raz0r]

Didn't even realise my JK2 was outdated fixed now.