I've tested SplitWolf yesterday on my RPI2 and I confirm that it worked. However, I got some issues that I don't know for sure where to report them, so for now, lemme post them here.
The first one is about automatic game data detection. I copied Wolf3D and Spear of Destiny data files (both full versions) to "rom/ports/wolf3d" folder, and I've even renamed all files in order to make them lowercase. Spear of Destiny worked fine, but Wolf3D gave me the error below:
Wolf4SDL was not compiled for these data files:
vgahead.wl6 contains a wrong number of offsets (162 instead of 150)!
Please check whether you are using the right executable!
(For mod developers: Perhaps you forgot to update NUMCHUNKS?)
After analysing how splitwolf works, I noticed there's various binaries for each game version: one for Wolf3D shareware, other for Wolf3D full, another for Spear of Destiny (both demo and full), etc. And you have to use the right binary according to your game version. In the case of the Retropie version, it tries to detect automatically which is your game version by looking into the md5sum of the "vswap.wl6" or "vswap.sod" files, and based on that, it chooses its respective binary file.
The problem relies exactly in the md5sum game version detection in the splitwolf.sh file, from RetroPie-Setup:
function launch_splitwolf() {
local wad_file="\$1"
declare -A game_checksums=(
['6efa079414b817c97db779cecfb081c9']="splitwolf-wolf3d"
['a6d901dfb455dfac96db5e4705837cdb']="splitwolf-wolf3d_apogee"
['b8ff4997461bafa5ef2a94c11f9de001']="splitwolf-wolf3d_full"
['b1dac0a8786c7cdbb09331a4eba00652']="splitwolf-sod"
['25d92ac0ba012a1e9335c747eb4ab177']="splitwolf-sodmp --mission 2"
['94aeef7980ef640c448087f92be16d83']="splitwolf-sodmp --mission 3"
['35afda760bea840b547d686a930322dc']="splitwolf-spear_demo"
)
...
}
Inside the "launch_splitwolf" function, I noticed that the checksums for "splitwolf-wolf3d_apogee" and "splitwolf-wolf3d_full" are swapped, and that was making splitwolf uses the binary for "apogee" version, instead of "full" version. After making the change below, it worked:
['b8ff4997461bafa5ef2a94c11f9de001']="splitwolf-wolf3d_apogee"
['a6d901dfb455dfac96db5e4705837cdb']="splitwolf-wolf3d_full"
Just for confirmation: the md5sum of my "vswap.wl6" is exactly "a6d901dfb455dfac96db5e4705837cdb". And I don't remember seeing any Apogee mentions on the Wolf3D version I have here.
The second one is about controller mappings. I used this adapter, with two PS2 controllers plugged:
When I opened the game the first time, I noticed that the right analog was wrongly mapped: when I press up, the player looks left, and when I press down, the player looks right.
I noticed that SplitWolf now uses SDL_GameControllerDB, in order to automatically detect and map buttons for a lot of different controllers. I followed the instructions mentioned in "Help, my controller is still not mapped properly" section, downloaded libsdl, compiled "controllermap" and run the following commands:
hg clone http://hg.libsdl.org/SDL
cd SDL/tests
gcc controllermap.c -lSDL2 -I/usr/include/SDL2 -o controllermap
./controllermap 0
After pressing the buttons on my controller, I got a line similar as the one below:
03000000100800000100000010010000,Twin USB Joystick,a:b22,b:b21,back:b28,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,leftshoulder:b26,leftstick:b30,lefttrigger:b24,leftx:a0,lefty:a1,rightshoulder:b27,rightstick:b31,righttrigger:b25,rightx:a3,righty:a2,start:b29,x:b23,y:b20,platform:Linux,
However, there's already a very similar line in "gamecontrollerdb.txt" file, in the Linux section, line 573:
03000000100800000100000010010000,Twin USB PS2 Adapter,a:b2,b:b1,back:b8,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,leftshoulder:b6,leftstick:b10,lefttrigger:b4,leftx:a0,lefty:a1,rightshoulder:b7,rightstick:b11,righttrigger:b5,rightx:a3,righty:a2,start:b9,x:b3,y:b0,platform:Linux,
Assuming the line already exists, then it should work. And after a lot of tests and analysis, I got it to work by adding the line below, in "launch_splitwolf" function:
function launch_splitwolf() {
local wad_file="\$1"
declare -A game_checksums=(
['6efa079414b817c97db779cecfb081c9']="splitwolf-wolf3d"
['a6d901dfb455dfac96db5e4705837cdb']="splitwolf-wolf3d_apogee"
['b8ff4997461bafa5ef2a94c11f9de001']="splitwolf-wolf3d_full"
['b1dac0a8786c7cdbb09331a4eba00652']="splitwolf-sod"
['25d92ac0ba012a1e9335c747eb4ab177']="splitwolf-sodmp --mission 2"
['94aeef7980ef640c448087f92be16d83']="splitwolf-sodmp --mission 3"
['35afda760bea840b547d686a930322dc']="splitwolf-spear_demo"
)
if [[ "\${game_checksums[\$(get_md5sum \$wad_file)]}" ]] 2>/dev/null; then
export SDL_GAMECONTROLLERCONFIG="$(cat $md_inst/bin/gamecontrollerdb.txt)" #This is the line I've added
$md_inst/bin/\${game_checksums[\$(get_md5sum \$wad_file)]} --splitdatadir $md_inst/bin/lwmp/ --split 2 --splitlayout 2x1
else
echo "Error: \$wad_file (md5: \$(get_md5sum \$wad_file)) is not a supported version"
fi
}
The reason why I think this worked: Splitwolf wasn't using "gamecontrollerdb.txt" file, and instead, was using default control mappings, probably identical mappings from Xbox360 controllers (I confirmed it by removing "gamecontrollerdb.txt" file, then running SplitWolf, and the results was the same as before). In order to make Splitwolf use the controller mappings from that file, you have to put its contents inside a environment variable called SDL_GAMECONTROLLERCONFIG. And that's exactly what the line above does.
For now, that's it. Can you guys tell me where's the right place to post the issues above? In your bitbucket repo? Or in RetroPie-Setup github repo?
