Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal. You can also buy games using our partner links for GOG and Humble Store.
We do often include affiliate links to earn us some pennies. See more here.

Get ready to explore a bird-sized skatepark, as SkateBIRD has not only flown right past the initial goal on Kickstarter, it also now has a Linux demo for you to flap your wings in excitement with.

Drop in, and be a skateboarding bird. Grind on bendy straws, kickflip over staplers, and carve killer lines through cardboard and sticky tape parks. Skate an expansively tiny world with simple controls even a Hawk named Tony would dig.

YouTube Thumbnail
YouTube videos require cookies, you must accept their cookies to view. View cookie preferences.
Accept Cookies & Show   Direct Link

The current Unity version used has issues with NVIDIA, it's the graphical corruption bug I've reported on numerous times (like this). It's easy to workaround, just add this launch option for it:

SkateBIRD.x86_64 -force-glcore42 -force-clamped

Or, if you have a recent NVIDIA driver (introduced in 418.30) you can use the "__GL_IgnoreInvalidateFramebuffer=1" environment variable.

Seems like it's going to be a pretty fun game, the demo is obviously quite small and a rough work in progress but it's certainly very charming. The camera is going to need work though, it feels like it works against you too much but I've no doubt that will be much improved as it's further developed.

Not only have they already smashed their initial goal, they've hit a stretch goal to add in unlockable side-stories and they're well on their way to the next goal to add a bonus level in the clouds which sounds amusing.

Find the Kickstarter here and the demo here.

Article taken from GamingOnLinux.com.
9 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. You can also follow my personal adventures on Bluesky.
See more from me
The comments on this article are closed.
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
7 comments

Ehvis Jun 14, 2019
View PC info
  • Supporter Plus
The current Unity version used has issues with NVIDIA, it's the graphical corruption bug I've reported on numerous times.

NVIDIA was adding an option to the driver to work around this issue. Hasn't this made it into the driver by now?


Last edited by Ehvis on 14 June 2019 at 9:13 am UTC
Liam Dawe Jun 14, 2019
The current Unity version used has issues with NVIDIA, it's the graphical corruption bug I've reported on numerous times.

NVIDIA was adding an option to the driver to work around this issue. Hasn't this made it into the driver by now?
I assume you're talking about this, which was just another workaround and I've heard nothing since.
Ehvis Jun 14, 2019
View PC info
  • Supporter Plus
The current Unity version used has issues with NVIDIA, it's the graphical corruption bug I've reported on numerous times.

NVIDIA was adding an option to the driver to work around this issue. Hasn't this made it into the driver by now?
I assume you're talking about this, which was just another workaround and I've heard nothing since.

Exactly. It says in the nvidia forum thread that it was introduced in 418.30, no I would assume that this environment variable would be the better way to work around it for current drivers.
Liam Dawe Jun 14, 2019
The current Unity version used has issues with NVIDIA, it's the graphical corruption bug I've reported on numerous times.

NVIDIA was adding an option to the driver to work around this issue. Hasn't this made it into the driver by now?
I assume you're talking about this, which was just another workaround and I've heard nothing since.

Exactly. It says in the nvidia forum thread that it was introduced in 418.30, no I would assume that this environment variable would be the better way to work around it for current drivers.
Interesting, they never seemed to note that in their driver release notes. Even so, frankly the normal workaround is quicker and easier to do. Adding NVIDIA driver profiles is not the friendliest of processes when the one we already know works is an easy copy/paste.
Ehvis Jun 14, 2019
View PC info
  • Supporter Plus
Interesting, they never seemed to note that in their driver release notes. Even so, frankly the normal workaround is quicker and easier to do. Adding NVIDIA driver profiles is not the friendliest of processes when the one we already know works is an easy copy/paste.

There is an environment variable for it. No need for profiles.
Liam Dawe Jun 14, 2019
Interesting, they never seemed to note that in their driver release notes. Even so, frankly the normal workaround is quicker and easier to do. Adding NVIDIA driver profiles is not the friendliest of processes when the one we already know works is an easy copy/paste.

There is an environment variable for it. No need for profiles.
Ah yeah I went right to the profile bit on the old article, testing it briefly now it seems it does fix it for SkateBIRD too. Will add it to the article, cheers.
abelthorne Jun 14, 2019
The graphical issues seem to happen also on AMD (using Mesa 19.0.2) and are fixed with the command line options you give.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.