I got a binary compiled for linux using make docker-linux, but can not get it to work. Retroarch does not recognize the .so file as a core. I am using ubuntu 26.04.
It seems the above crash on my end only happens if Retroarch video output is set to Vulkan. If I switch to Opengl or direct3d11 both software renderer and Vulkan in Goosestation video options do load shaders without an issue
I was mainly interested in software renderer combined with shaders, as I can use the original Duckstation that has much better performance for upscaled 3d renders in 4k
Interesting! Do you know how real psx shows it, with or without banding? This kinda looks like one of the first hardware revisions limitations, when similar effect was in tomb rider etc. I think duckstation actually has the setting for emulating it. Maybe this setting got stucknor something. I’ll take a look once I reach my pc
Actually docker is the least painful way to build it… all other methods are even more work
Make sure you have core info properly recognized, and delete the cache file from core info folder
Also you need -f Dockerfile.windows argument to point to proper file
I believe that’s the difference between 32-bit color and 15-bit (minus the normal dithering that the console used to cover up some of that atrocious banding).
I was able to replicate this by toggling this thing:
This emulates earlier models.
Without this setting, the colors are smooth
The game looks cool btw. Is this one of those hidden gems?
Awesome reports DemitryCzarevich!
1 Like
Moved the Folder to Goosestation one but still got an Error:
Cloning into ‘goosestation-builder’… remote: Enumerating objects: 138, done. remote: Counting objects: 100% (72/72), done. remote: Compressing objects: 100% (70/70), done. remote: Total 138 (delta 34), reused 7 (delta 0), pack-reused 66 (from 1) Receiving objects: 100% (138/138), 397.06 KiB | 424.00 KiB/s, done. Resolving deltas: 100% (71/71), done.
D:\Programs\PortableGit\goosestation-builder>cd goosestation-builder
D:\Programs\PortableGit\goosestation-builder\goosestation-builder>docker build -f Dockerfile.windows -t goosestation-builder-windows . ERROR: failed to connect to the docker API at npipe:////./pipe/dockerDesktopLinuxEngine; check if the path is correct and if the daemon is running: open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified.
D:\Programs\PortableGit\goosestation-builder\goosestation-builder>docker run --rm -v “$PWD/dist:/work/dist:Z” goosestation-builder-windows windows
I use this Command:
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 w
Yep, that’s it! I’m not sure how this option ended up enabled — maybe it was the default setting, or maybe it was left over from previous experiments with core versions 0.1 and 0.2 — but without it, the lighting gradients disappeared! All that’s left is to sort out the shader support for Vulkan rendering, and then we can start using Goosestation everywhere.
UPDATE: By the way, the lighting gradients are gone on OpenGL too, and the shaders work on OpenGL — awesome!
1 Like
This time, you’re having an issue with the Docker service not starting
ERROR: failed to connect to the docker API at npipe:////./pipe/dockerDesktopLinuxEngine; check if the path is correct and if the daemon is running
It seems to me that you’re running Docker commands from the Git console, right?
I did it by launching Docker directly from a shortcut on my desktop (Docker Desktop). At the bottom right, I had an arrow labeled “Terminal” (this is a new feature that appeared in version 4.32); from there, the console launched directly within the Docker window (in Windows, it was PowerShell), and I entered all commands right in that console.
I didn’t use the Git console; it’s essentially needed to run the “git” commands for cloning project repositories. I did everything directly in the open Docker Desktop window.
1 Like
Yes that is what I been Trying
Thanks for Instructions how to do it on Docker.
I will Try it Tonight
Update:
Just Tried it thru the Docker Desktop and it Compiled/Worked
Put core in RA and did load up game. Though only in GL Video Driver
Big Thank You @DemitryCzarevich for Helping Me to get this to Work
Will Follow the Development and Work on Goosestation
2 Likes
Hey all, did a fix for Vulkan If you had issues with Vulkan before, try this one https://codeberg.org/hueponik/goosestation-builder/archive/f753a72e2d43724a91200c6e3063d075564181ba.zip
4 Likes
YES!!! It works!
I’ve selected Vulkan renders in both RetroArch and the Goosestation core - games load normally and run with shaders.
But there’s still an issue with closing content: RetroArch crashes when I press the “Close Content” button.
UPDATE: Cheats from the RetroArch database also don’t work (
2 Likes
Retroarch also crashes if you try to change a game via Retroarch history. Though for a strange reason if you switch from a Playstation game to another via history, which also uses Goosestation, Retroarch does not crash
2 Likes
Last master should have cheats, try them? I haven’t tested them heavily yet
1 Like
Tried that and does load up in Vukan BUT when I press Fast Forward the RA just Freezes and have to exit RA and Come back on to use it Again
Here is the Log:
Closing content shouldn’t crash on latest master anymore.
@DaveTheMan1985, can’t reproduce… But I remember having this issue, and disabling frameskip in Settings => Frame Throttle helped
1 Like
Where can I go to download the Latest Master?
Tried that but Sadly did not work
I don’t have any issues with fast-forwarding; I use it all the time to skip the developers’ intros before the game starts. Unless this is related to the fact that you have an AMD graphics card (I have an NVIDIA 1080 - old but still going strong), you might want to try disabling “Sync to Exact Content Framerate” (I have that turned off, but “Fast-Forward Frameskip” is enabled)
@hueponik - thanks, the cheats are working now; I tested them on a few games - everything’s fine! I’m currently in the process of recompiling the core with a fix for RA crashes after closing content.
Where can I go to download the Latest Master?
Just delete the previous Goosestation repository clone. If you created it in Docker and didn’t specify specific paths for the project folder, it should be in the user’s root directory, like “c:\Users\DaveTheMan\goosestation-builder”, and then follow the core compilation instructions from the beginning.
1 Like