Goosestation - Build Your Own Duckstation-libretro

Libretro Cores
#108

first load the Goosestation core via the “Load Core” menu, then load the game via the “Load Content” menu, play for a bit (even just watch the opening screens), and then select “Close Content” - the core resets but does not unload completely;

Hm, it’s not crashing or anything is it? I think this is “by design”. I wanted to add the mode where you can just boot bios without the game.

So you load the core. Then you can either load the game with it or just boot it. Then if you close content, you don’t close the core… You can also use “unload core” button to actually unload the core.

What’s your usage scenario that is ruined by this logic?

#109

No, it doesn’t crash - at least not right away - if you repeat the process: “Load Core” - “Load Content” - “Close Content” - since the core isn’t unloaded or closed until the BIOS has fully loaded - “Load Content” (another game) - “Close Content” - repeat 3 times; after that, the entire RetroArch crashes (this may be specific to my hardware; you can try repeating this experiment. I’m considering it solely from a testing perspective, not as a real-world usage scenario).

Yeah, and it works great! Thanks for this feature - I love sometimes listening to tracks from the game on CD-player :smile:

The “Unload Core” button is only available if the core is not running; if the core is already running and has loaded into the BIOS, the “Unload Core” button is not displayed.

Screenshot_1
Screenshot_11919×1032 164 KB
Screenshot_2
Screenshot_21919×1035 201 KB

As I mentioned earlier, I sometimes download new game images and run them to test their functionality. After that, I usually rename the image according to my naming convention (title, region, game serial number, language, country of release), find the corresponding box art, and then add the game to my PlayStation playlist and link the appropriate core to it. But sometimes I don’t have time to neatly organize a new game in the playlist, so I just settle for a quick check to see if the image works. In those cases, I use this scenario: “Load Core” - “Load Content” - wait for all the opening intros to play, start the game until the character appears - “Close Content.” In this scenario, the Beetle PSX HW and SwanStation cores close the content but do not unload the core or boot the BIOS, unlike GooseStation. Sometimes I want to test a game with a different core (by default, all games from my PlayStation playlist open using the Beetle PSX HW core); in such cases, I also prefer to use the scenario “Load Core” - “Load Content” - to check the aspects of the game that interest me using the current core settings - “Close Content,” rather than reassigning the core in the playlist, and then reverting to the default core after testing and experimentation.

During my experiments, I tested a scenario where, conversely, we first select “Load Content” and then choose a core for that content - with this sequence of actions, closing the content while using the GooseStation core does not trigger a subsequent boot into the BIOS, and both the content and the core are completely unloaded. I guess I just need to get used to this specific sequence of actions :slightly_smiling_face:

#110

For you, when you do “close content” it boots into bios automatically?.. Couldn’t reproduce this

#111

Yes, that’s exactly right.
I tried creating a clean installation of the RetroArch nightly build with all default settings, copied the core and info files to the appropriate folders, loaded and launched the core in BIOS to select the Vulkan renderer and increase the resolution, without any additional core settings (PGXP, Audio, Display, etc.), restarted RetroArch completely to apply the settings, and followed the sequence “Load Core” – “Load Content” – wait for all the opening intros to play, start the game until the character appears – “Close Content.” Even in this case, with all default settings, after closing the content, I am booted back into the PSX BIOS.

1 Like
#112

Regarding game compatibility, Duckstation and Goosestation are the only ones that do not freeze in Slayers Royal 2 in the beginning, during Naga’s sleeping spell. This was a known bug in the 2000s emulators but a few years ago when I tried psx beetle, it also had it. Few years ago Duckstation had it as well. Issue is not present in Saturn version

1 Like
#113

How long has it been since you updated the Beetle PSX (HW) core?
Over the past two months, they’ve done a major refactoring and fixed issues that hadn’t been working for a long time (based on my personal observation, the game “Roswell Conspiracies - Aliens Myths Legends” now plays sound in certain locations - this wasn’t the case before, and this fix was implemented just last week), I’m by no means downplaying the achievements of the Goosestation core, and in most cases it’s much more functional than other PSX cores - except that you have to build it yourself due to licensing issues. I always try to test the same game on all available PSX cores to determine which one produces the best-looking graphics for me and doesn’t have any significant gameplay issues caused by emulation.

2 Likes
#114

I have not Followed so when did they last update the Beetle PSX Cores?

Though I agree that need to be good as not everyone would know how to Build It and Not even know about it as not Offical

#115

The Beetle PSX Cores were last updated on June 14, 2026.
I’m keeping track of the changes at this link:

(My apologies to @hueponik for this slight off-topic)
1 Like
#116

Tried the game with Beetle and it still freezes, while music continues playing. Does not happen on Duckstation. You start the game, talk to specific guy and pick the top right spot on the map where Naga meets you. She casts few spells, you hit her a few times and when she tries to cast her final spell that will backfire and put her to sleep, thus ending the fight, game freezes. I remember this bug happening both on epsxe and psx back then. Seems it has not been resolved

Slayers Royal 2 (Japan)-260617-180608
Slayers Royal 2 (Japan)-260617-1806082633×2160 1.08 MB

2 Likes
#117

Yes, I agree - there are games that won’t run on one core and won’t even launch, but run perfectly on another without any issues. It’s great that we now have one more core available thanks to @hueponik’s efforts.

1 Like
#118

Hi all @DemitryCzarevich sorry I couldn’t reproduce your issue with bios load after game close, I’ll take another look later. I’ll spend some time this later, was too busy with below:…

#119

Goosestation 0.6.5 with skip engine

https://youtu.be/KO29LtFPhYE

What do achievements, cheats and doors have in common? Goosestation. Because it now has SKIP ENGINE!

Are you tired of seeing Resident Evil doors? Slow memory card reading screens, or just normal slow loading screens? Get the feels-like-cartrtidge-based-psx feeling with SKIP ENGINE.

  • Skips any cd reading segments
  • Skips memory card activity

Know a part of the game you’d like to skip? Enter the Skip Trainer: add your own skip rules by training the engine. And, erm… you have to, as for now only 3 games have rules configured:

  • Resident Evil - Director’s Cut - Dual Shock Ver.
  • Resident Evil 2 - Dual Shock Ver. (Disc 1)
  • Wipeout XL

Training engine is based on rcheevos for detecting skippable parts, and scanner works similarly to cheat diggers to find skip triggers. More info on how to train your skip engine: https://codeberg.org/hueponik/goosestation-builder/src/tag/v0.6.5.11443/SKIP_TRAINER.md

New option is available in Core Options -> Skip Engine/Trainer

If you find good solid skip rules, feel free to open a pull request https://codeberg.org/hueponik/goosestation-builder/pulls

5 Likes
#120

I didn’t think PS1 emulation could be improved any further, but here we are!! Thank you.

2 Likes
#121

Could this Be Added to other PS1 Cores?

#122

Anything is possible, but for now I’m gonna concentrate on Goosestation

2 Likes
#123

Fair Enough

I was just wondering as just in case IF GooseStation was gone after by Steznek

So work on others as a Back up

#124

Managed to build the core.

As someone who’s not familiar with Docker (don’t have a ton of experience with Linux either for that matter) I thought I’d share what I did and how it went.

First off, Docker seems to require at least Windows 10. Already on Win10 so, no problem but wait…nope: actually for Windows 10 it needs the 22H2 update…Alright; I’m just gonna use a virtual machine then. So, begin the install process of the Win10 22H2 update but the (virtual/guest) machine update got stuck at 96% for some reason. Apparently, it’s pretty common. So, update via the Update Assistant instead. After a while it successfully updates to 22H2.

Then I also need to install git. I do that. Finally start Docker but it gives me an error. Apparently, the VMware virual machine needs virtualization enabled else it won’t work. Alright, I do that, it launches but now it gives me another error “WSL version too old” or something. Bit of searching I manage to fix that also.

After a bit of reading, it finally starts building/compiling. Everything seems to go well, except it’s really, really slow…took more than 30 mins and it wasn’t finished (running a Win10 guest on a Win10 host is likely going to be slow unless you have a pretty decent machine) but half way through

docker build -f Dockerfile.windows -t goosestation-builder-windows .

I get an error…looking up the error seems it may have been a timeout error…So my guest OS was running/compiling so slowly that it may have caused the problem. Ok, allocate more RAM to the guest OS and disable a bunch of things in the Guest OS, alright so things runs much faster now…

I get a bunch of other errors, was ready to give up but just for the sake of curiosity after all these attempts I check out the Docker output folder and there is a goosestation_libretro.dll. Huh. “Probably outputted the dll but since it never completed the full compiled file, it probably won’t work”. To my surprise, nope, it works perfectly. Whatever, I’ll take it.

So here are the command lines I tried for the record, not sure when/where it compiled successfully, tbh

(Posted above by DemitryCzarevich)

git config --global core.autocrlf input
git clone https://codeberg.org/hueponik/goosestation-builder.git
cd goosestation-builder
docker build -f Dockerfile.windows -t goosestation-builder-windows .
docker run --rm -v “$PWD/dist:/work/dist:Z” goosestation-builder-windows windows

then, I believe these from some reddit thread:

git fetch
git checkout v0.6.5.11443
docker build -f Dockerfile.windows -t goosestation-builder-windows .
docker run --rm -v “$PWD/dist:/work/dist:Z” goosestation-builder-windows windows

docker build -f Dockerfile.windows -t goosestation-builder-windows .
docker run --rm -v “$PWD/dist:/work/dist:Z” goosestation-builder-windows windows

This is by no mean a “guide” because it’s more luck than anything I got it to work.

TL;dr Big thanks to hueponik for making this possible, even though the process is a bit more complex than the usual ‘Download pre-compiled core, place in core folder’ way (I understand why it has to be done this way) but…it worked in the end.

edit: Goosestation also supports No$psx’s bios. To obtain the bios use the stand alone No$psx, go to ‘utility’ > remote access > create nocash bios rom as raw image (PSX-XBOO.ROM). Take the file created and simply place it in RetroArch’s system folder where the other PSX bios normally are.

1 Like
#125

Tried Latest Version goosestation-builder-v0.6.7.11580 and when I load the Game up Retroarch Just Crashes and Exits the Program

Tried making Log File but it also exits and lose it Straight Away

1 Like
#126

I’ll take a look. Must be windows thing

1 Like
#127

Okay - I am using Windows 11