Turrican (hurricane clone) black screen

ExarKunIv

@JimmyFromTheBay that one should of worked. I tested that script and it installed and worked fine for me.

If you are saying about the error that pops up when you finish installing it. That is just a error that comes up when there is no way for it to check for a update

JimmyFromTheBay

@ExarKunIv So what could be going wrong? For Hurrican, do I still need to install that libepoxy thing first?

Also, which error do you mean with OpenBOR? The "curl" one or the "crcerror" one?

ExarKunIv

@JimmyFromTheBay crcerror the name of the person who wrote the script not a error

sleve_mcdichael

@JimmyFromTheBay looks like you've already sorted some of this but I'll answer for the record here anyway:

how do I get rid of the old ZeroJay version of RetroPie-Extra? I can't install the new one over the top and neither the Remove or Update instructions here work.

To switch from ZeroJay's repo to Exarkuniv's:

# discard the most recent commit by checking out the commit one prior
# necessary because this commit is not in the new repo, will cause merge conflict
git reset --hard HEAD^

# switch to ExarKuniv's new repo
git remote set-url origin https://github.com/Exarkuniv/RetroPie-Extra

# now pull from the updated origin
git pull origin

@JimmyFromTheBay said in Turrican (hurricane clone) black screen:

@sleve_mcdichael So if I uninstall it and reinstall it now, it'll work?

This was just a bug in the install script, it should be fixed now and you can update your local version with git pull origin (or ./update-extras.sh).

Unfortunately it skipped a lot of them because they were already in RetroPie-Setup from previous failed attempts and there was no option to overwrite.

Earlier versions of RP-Extra, as well as some of our stand-alone scripts before they were integrated, used to be copied directly to the RetroPie-Setup/scriptmodules directory alongside the "official" RetroPie modules.

More recently, they have utilized RP's built-in method for including "external" modules by placing them in RetroPie-Setup/ext/[repo_name]/scriptmodules instead.

However, if you still have the old versions in the "official" scriptmodules directory, then the new "external" ones of the same name can't be used again. You can "clean the working tree of untracked files" with git clean. Navigate to your RetroPie-Setup directory:

cd ~/RetroPie-Setup

Use the -n (dry run) flag to see what will be removed, then use -f (force) to actually remove them:

git clean -n scriptmodules
git clean -f scriptmodules

So I manually copied hurrican.sh from /home/pi/RetroPie-Extra/ (...) It seemed to work okay, but when I booted it up, just music and a black screen again.

(...) So what could be going wrong? For Hurrican, do I still need to install that libepoxy thing first?

That is puzzling. The libepoxy-dev thing was in response to someone who was doing a manual installation; it should be done automatically by the script, now.

I wonder if there's a missing dependency that slipped through 'cause we already had it from a different module or something.

I don't know exactly what I'd be looking for but there might be some clue in the game and/or install logs.

Game log:

/opt/retropie/configs/ports/hurrican/Game_Log.txt

Install logs are in:

~/RetroPie-Setup/logs

They are compressed in .gz format; you can view them locally with zless or extract them for sharing with gunzip.

Only the 20 most recent are retained. If you can't find the one where hurrican was installed, just install it again and take the last one.

it reported a 404 relating to something about "curl", and when you try to run a game it says "https://github.com/crcerror/OpenBOR-Raspberry.git ^{} failed with return code 1 - please check your network connection".)

Also, which error do you mean with OpenBOR? The "curl" one or the "crcerror" one?

crcerror is the GitHub account name of the user who hosts the OpenBOR repo:

https://github.com/crcerror/OpenBOR-Raspberry

The curl error is something I see in some, but not all, of these extra scripts. It has to do with the way Setup checks if updates are available, I guess. Sometimes they are, sometimes they aren't, and sometimes it is unable to determine and says so...

...and then sometimes, in our extra scripts, it will do weird sh-- like say "update is available" when it is not, immediately after installing the latest version, or having "install options disabled" requiring a remove/reinstall any time an update is to be performed.

I'm really not sure what this is about. I suppose it is probably something going on in function rp_hasNewerModule() but I haven't dug deep into how that works, yet.

JimmyFromTheBay

@sleve_mcdichael said in Turrican (hurricane clone) black screen:

Earlier versions of RP-Extra, as well as some of our stand-alone scripts before they were integrated, used to be copied directly to the RetroPie-Setup/scriptmodules directory alongside the "official" RetroPie modules.

More recently, they have utilized RP's built-in method for including "external" modules by placing them in RetroPie-Setup/ext/[repo_name]/scriptmodules instead.

However, if you still have the old versions in the "official" scriptmodules directory, then the new "external" ones of the same name can't be used again. You can "clean the working tree of untracked files" with git clean. Navigate to your RetroPie-Setup directory:
cd ~/RetroPie-Setup
Use the -n (dry run) flag to see what will be removed, then use -f (force) to actually remove them:
git clean -n scriptmodules
git clean -f scriptmodules

Aha! THIS was it! I uninstalled everything, ran git clean, reinstalled and now the scripts are in separate RetroPie-Extra sections in RetroPie-Setup and Hurrican works! Yay! Many thanks!

Still having no luck with OpenBOR, though. It installs (curl error again) but then fails to run, complaining "no config for openbor". Any idea what it's looking for?

All I have in /opt/retropie/configs.hdmi/openbor

is EMULATORS.CFG, comprising this single line:

openbor-v6510 = "/opt/retropie/emulators/openbor-v6510/OpenBOR %ROM%"

I have a few ROMs in PAK format in /home/pi/RetroPie/roms/openbor, which AFAIK is the correct format for OpenBOR as a system rather than as a port, and it's in ES_SYSTEMS.CFG with these lines:

  <system>
    <name>openbor</name>
    <fullname>OpenBOR</fullname>
    <path>/home/pi/RetroPie/roms/openbor</path>
    <extension>.pak .PAK .sh .SH</extension>
    <command>"/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _PORT_ "openbor" "%ROM%"</command>
    <platform>openbor</platform>
    <theme>openbor</theme>
  </system>

sleve_mcdichael

@JimmyFromTheBay cheers on Hurrican! I can't help with openBOR, I've never looked into that one yet.

ExarKunIv

@sleve_mcdichael I have messed with openBOR a bit. But I'm not by my system at the moment. So I can't help till tomorrow.

I can take a better look at it. I thought I got it working right as a separate system so you don't have to go in to the ports to start it.

So I'll do a clean load and install that from my repo and see what happens

JimmyFromTheBay

@ExarKunIv Sorted it :)

Suddenly occurred to me to go and look in the other ES_SYSTEMS.CFG. This did the trick:

  <system>
    <name>openbor</name>
    <fullname>OpenBOR</fullname>
    <path>/home/pi/RetroPie/roms/openbor</path>
    <extension>.zip .ZIP .pak .PAK .ZIP .ZIP .PAK .PAK</extension>
    <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ openbor %ROM%</command>
    <platform>openbor</platform>
    <theme>openbor</theme>
  </system>

(The main difference being a SYS instead of a PORT, logically enough.)

I've wanted OpenBOR as a system for months and months, so thanks so much for taking over RP-E and making it work properly.

(And as a bonus I've now got Yabasanshiro installed and playing Sega Ages Memorial Selection Vol.2 beautifully, so this has been a heck of a day :))

Cheers to you both.

ExarKunIv

@JimmyFromTheBay glad you got it working.

And thanks for using it.

The more people use them and tell us the issues, the better.

JimmyFromTheBay

@ExarKunIv Well, since you ask... :D

Both previously and now, I'm having no luck at all with Heboris. Whatever I do, it's stuck in a tiny corner of the screen and there's almost no sound, just a bit of speech. I've tried every game option, I've tried setting it to a 640x480 resolution in Runcommand, none of it changes anything. So could it be somehow installing wrongly?

ExarKunIv

@JimmyFromTheBay It did install correctly for that script.

im in the middle of testing each and every script on my Repo.
that game needs to have a new command put infront of the command in the EMULATORS.CFG

it needs to look like this

heboris = "XINIT: pushd /opt/retropie/ports/heboris; ./heboris; popd"
default = "heboris"

and it will once i upload the new script.

so you might and will come across ports that dont work or are working odd.

by the end of the week i should have all the working scripts uploaded to the repo for everyone

keep a eye here for my updates

sleve_mcdichael

@ExarKunIv said in Turrican (hurricane clone) black screen:

it needs to look like this

"XINIT: pushd /opt/retropie/ports/heboris; ./heboris; popd"

That's going to come up against the same issue with XINIT and ; that we ran into here in SORR:

https://github.com/Exarkuniv/RetroPie-Extra/commit/8a86a6fb88e66126e89685747e59540b3819dd93

We'll need to build another in-between script that launches it with:

#!/bin/bash
pushd "md_inst"
./heboris
popd

...and then the emulators.cfg command would launch that script with XINIT:

heboris="XINIT:path/to/that_script.sh"
default="heboris"

ExarKunIv

@sleve_mcdichael really? let me check mine again

Update:

Will doing that does work just fine,
it does come up commands not found, or file not found, but it does work. Really odd.

im sure doing the script way is the correct way.

sleve_mcdichael

@ExarKunIv yes, as I described before what happens, here:

https://retropie.org.uk/forum/post/275525

When XINIT gets rolling, it echoes "I'm about to do [foo]", and then it does [foo].

It does this by:

echo -e "\nExecuting (via xinit): [foo]\n"
[foo]

If [foo] contains any semicolons, it gets broken. It tries to say:

echo -e "\nExecuting (via xinit): foo1; foo2; foo3\n"
foo1; foo2; foo3

Then this gets parsed by bash: the quotes are stripped, the semicolons break it into separate lines, and the commands that are actually run, are these:

# first command
echo -e \nExecuting (via xinit): foo1
# second command:
foo2
# third command:
foo3\n
# fourth command
foo1
# fifth command:
foo2
# sixth command
foo3

Yes, it does technically "work." The actual commands we want to run (foo1, foo2, and foo3) are ultimately ran at the end, and the game will launch. But before it runs the commands we do want it to run, it does some that we don't want. It runs an "echo" command that cuts off too soon, it runs foo2 an additional time (which probably does not work because we have not actually ran foo1 yet, just echoed that we are going to), and then it runs foo3\n which, with the \n appended, is not a valid command. If you check the runcommand log you will see the error messages pertaining to these erroneous commands.

In this case, nothing more disastrous would happen than logging some complaints about your syntax, but imagine what would happen in:

cd path/to/garbage_dir
rm -rf *

...if the second command were ran before the first.

ExarKunIv

@sleve_mcdichael yea i get it, that might be the reason why none of the settings that are changed keep once you quit the game, (its just a thought)

i will make the changes to my test script and see what i can find (about the settings saving or not)
as i know what you explained will get cleared up with your fix

JimmyFromTheBay

More investigations:

BurgerSpace: works fine, although weirdly if you don't set it to 640x480 in the Runcommand menu the keyboard gets disabled and there's no way to quit out except pulling the plug.

Prototype: works fine.

Wizznic: doesn't start, dumps you straight back to EmulationStation. No idea where to look for log files for clues.

Streets Of Rage Remake: see Wizznic.

ExarKunIv

@JimmyFromTheBay see the link i posted, that is the general one for all the ports we are dealing with, so post your findings there

as for SORR it works fine, as long as you have the data files.

and update your scripts, i just cleaned them all up (for the most part)

JimmyFromTheBay

@ExarKunIv said in Turrican (hurricane clone) black screen:

@JimmyFromTheBay see the link i posted, that is the general one for all the ports we are dealing with, so post your findings there

The "XINIT and ;" one?

as for SORR it works fine, as long as you have the data files.

Oh, I thought the whole point of SORR was that it was a ground-up remake that didn't use any of the original's resources and didn't need any additional files. Will investigate further. [EDIT: just dumped all the files from 5.2 into /home/pi/RetroPie/roms/ports/sorr and it works a treat now.]

ExarKunIv

@JimmyFromTheBay said in Turrican (hurricane clone) black screen:

[EDIT: just dumped all the files from 5.2 into /home/pi/RetroPie/roms/ports/sorr and it works a treat now.]

Glad you got it working, if any of the ports dont work, then they need the data files from another source, which you are on your own to provide.

Here is the link to my post here about all the scripts in Extras

post your questions and findings there, so everything is in one place