New Installer Jedi Academy
-
@quicksilver I'm not certain that I can explain it well. The problem I encountered may only apply to retropie on a desktop environment.
I am trying to explain this the best I understand it (which isn't that well).
X windows has 2 resolution pieces, usually set to the same value.
First there is the desktop resolution This is the max desktop size. It can be large.
Second there is the viewing resolution. This ths the portion of the desktop currently being displayed on your monitor.
So for example, you can have a 1920x1080 desktop size, and a 640x480 view size.
---------------------------------- | Desktop. | | ------------- | | | View. | | | | | | | ------------- | ----------------------------------
When a game launches with a smaller resolution than the desktop, it starts with its focus on the same portion of the desktop as the game. Now, frequently, if you move your mouse too quickly, the view window may no longer be focused on the same portion of the desktop as where the game is being rendered.
------------------------------------- | ----------- | | | View. | | | ----------+--- | | | | Game. | | | | | | ---+------- | | | | | | -------------- | -------------------------------------
Where possible, at least with the quake3 engine games the simplest solution is to set the games resolution to the same as the desktop. There might be a better way.
-
@quicksilver I'm a little stumped by your error. I don't have a file
/opt/retropie/ports/openjk_ja/base/ui${arch}.so
at all, and the game runs. Do you have a file/opt/retropie/ports/openjk_ja/uiarm.so
? -
@gderber said in New Installer Jedi Academy:
@quicksilver I'm a little stumped by your error. I don't have a file
/opt/retropie/ports/openjk_ja/base/ui${arch}.so
at all, and the game runs. Do you have a file/opt/retropie/ports/openjk_ja/uiarm.so
?Yes uiarm.so is located there. However I found the solution. https://github.com/JACoders/OpenJK/issues/631. Copying the .so files to the base directory solved the issue. I find it a bit puzzling though because the error log doesnt show that it was expecting it to be there. But nonetheless it worked...perhaps we should symlink the .so files to the build folder? What do you think is the best solution?
-
@quicksilver I'm not sure, a symlink does seem easy. But is it necessary. Like I said, I don't have that file in my base folder, and both SP and MP run without problems. And why does SP work for you and not MP.
I think the error is the symptom and not the actual problem. I'd like to identify the actual problem if possible.
-
@gderber Im not sure. All I know is that it doesnt work as-is. But if I follow the advice from that github issue I posted and I copy the .so files to the build directory then it works.
-
True, I've updated the script so that it'll work for people. This may be the best solution.
I wish I could find an answer to my questions because I'd feel better about the solution.
-
@gderber I wonder if the .so files are replacements for the original games .dll files (it would then make sense why openjk expects them to be in the same folder as the game files). Since the original windows .dll files will not be compatable with a ARM Linux system they might need to be replaced. This is just a hunch, as it's something I have encountered before with other game engines. I'm not near my computer right now but will look into this.
-
So removing the .so files from
/opt/retropie/ports/openjk_ja/
and moving them to thebase
folder causes the single player to stop working. I guess just symlinking the .so files is the best way to get around this that way the single player and multiplayer launch scripts will work. Why they are needed in both directories im not sure. Or perhaps only some of them are needed in the base directory? I cant find anything in the openjk documentation that sheds any light on this unfortunately. -
@gderber said in New Installer Jedi Academy:
True, I've updated the script so that it'll work for people. This may be the best solution.
I tried the script out again but I dont see where it made the symbolic links.
-
@quicksilver It should have made a link $romdir/ports/uiarm -> /opt/retropie/ports/openjk_ja/uiarm.so
I did notice a typo in the script it should be $romdir/ports/uiarm.so
-
I am new to RetroPie, so how would I get this downloader running?
-
@Luddo183 The easiest way will be inside the RetroPie-Setup/scriptmodules/ports folder run the command
wget https://raw.githubusercontent.com/gderber/RetroPie-Setup/feature/openjk_ja/scriptmodules/ports/openjk_ja.sh
Then run retropie_setup.sh, it will be under the experimental section. Right now Singleplayer works, Multiplayer depending on your setup may be a little buggy.
-
@gderber
Thanks, will try ASAP -
@gderber
When booting in, cannot find default.cfg -
@Luddo183 I don't have a file by that name. It's probably inside the datafiles.
Did you copy assets0.pk3 assets1.pk3 assets2.pk3 assets3.pk3 from the original game into
RetroPie/roms/ports/jediacademy
? -
@quicksilver I've updated the script. For me it creates the symbolic link inside the
RetroPie/roms/ports/jediacademy
directory pointing to/opt/retropie/ports/openjk_ja/uix86_64.so
For you it should point to/opt/retropie/ports/openjk_ja/uiarm.so
-
@gderber Just tried again and still no symbolic link. Im not sure why it isnt working.
-
@quicksilver does the install log show anything?
-
@gderber Im assuming this is the relevant part of the log
ln: failed to create symbolic link '/home/pi/RetroPie/roms/ports/jediacademy/uiarm.so': Function not implemented /home/pi
I should note that my
/home/pi/RetroPie/roms/ports/jediacademy
is on an external flash drive. I wonder if thats what is causing the issue. However I have not run into issues with symbolic links before so Im not sure what would be different about this one. -
@quicksilver FAT32 doesn't support symbolic links - if that is the current USB stick filesystem format.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.