It's interesting to note that Unity aren't providing a binary patching utility for Linux as they are for Mac and Windows (which allows developers to deploy fixes for legacy projects without having to do new builds). Some additional Linux-specific notes on the vulnerability from Unity's developer remediation guide [External Link] for this issue explain how platform-specific security implementations make them see a lower risk profile.

On Linux, the vulnerable Unity command‑line arguments function similarly to the LD_PRELOAD mechanism. Under the standard Linux security model, these arguments do not cross privilege boundaries and therefore do not introduce additional risk relative to what is possible with LD_PRELOAD.

In environments such as AppArmor, bubblewrap, Firejail, or SELinux, if a restricted process can launch a Unity application outside its confinement, arbitrary code execution is already possible and this vulnerability does not add further risk. In certain SELinux or AppArmor configurations, common injection methods (LD_PRELOAD, ptrace) may be blocked while still allowing Unity to be launched with arbitrary arguments. In this case, the vulnerable arguments could bypass policy restrictions and become a viable exploit path.

View this comment - View article - View full comments

Happy birthday! Here's to many more. Glad to have been a part of things along the way!

View this comment - View article - View full comments

Quoting: dpanterDefinitely in my top twenty list of games where you eat art as a snake! :wub:

:D

View this comment - View article - View full comments

Congrats to you, Liam (and all the other contributors over the years). Here's to many more birthdays.

Lovely choice of cakes, dpanter!

View this comment - View article - View full comments

Quoting: stormtuxIs it possible the cursor/button offset is linked to the use of wayland or X11? With KDE Wayland I see the problem but not in KDE X11.

Ah, you're probably right - I've been swamped with other work on the project and haven't yet managed to really dig into it again. I'm not sure if I'll be able to squeeze in a proper fix in time for the imminently upcoming "Game Difficulty and Player Freedom" update, but if not, shortly after.

Quoting: stormtuxSetting the environmental variable fixes the problem for me on KDE Wayland, thank you :woot: .

Glad to hear that's sorted it for you! Thanks for confirming!

View this comment - View article - View full comments

Just to follow up on the cursor/button offset stuff, it looks like my original fixes for the same problem occurring in Gnome made it manifest in KDE. Good times.

I'd still like to come up with a more universal solution, but in the meantime, setting the following environment variable should help (log will show "Found CAPES_BORDER_FALLBACK environment variable. Restoring default Unreal behaviour." when it's detected).
CAPES_BORDER_FALLBACK=true

If you're on Steam, the following launch option will do that for you:
CAPES_BORDER_FALLBACK=true %command%

Sorry again for the inconvenience!

Edit: Turns out that doesn't help. I'll need to dig into it further.

View this comment - View article - View full comments

Quoting: hardpenguin

All Reviews: Mixed (57%)

Nooooooooooo

It's difficult to feel like many of the negative reviews reflect the game we made (people are never wrong about how they feel though). It's a bummer for sure.

View this comment - View article - View full comments

Quoting: stormtuxI found a similar problem linked to the interaction between the cursor and the UI elements (buttons, checkboxes). It looks like there is some offset between the cursor coordinates and the UI coordinates.

Yeah, it's all the same thing. Unreal has a separate transparent SDL window to capture input events, and keeping that in sync with the window the game renders to ends up being a little awkward. My workarounds so far covered a bunch of cases, but returning to being a borderless fullscreen window after being minimised seems to have more idiosyncrasies than are visible in Gnome on my development machine.

Until I have a more robust fix, the quickest way to toggle to windowed mode and back is to press F11 (that way you don't have to go via the menu).

Quoting: stormtuxOne thing I found missing is the audio for the narrator in the intermission videos. The characters speak and then... silence... then they speak again. A good narrative voice would perhaps have improved the interludes, and given more opportunities to add more funny jokes :grin: .

Would have been nice to have, for sure! If we had been able to get that recorded, it would have been Seraph (the character who gives the narration in the intro cutscene) narrating.

View this comment - View article - View full comments

Gosh, this is a very nice writeup. Thanks so much - it's super nice to hear the game is resonating with you, and gratifying to know that the game's focus on teamups and positioning shines through and feels like a strength.

Like me, you'll probably end up with some favourites for their abilities, as well as their link team-up abilities, and you'll end up hardly using some others.

Don't leave us hanging! Who are your favourites? :D

Issues: one real nuisance quirk I did have on Kubuntu Linux 24.04 (KDE Plasma), was having to switch between borderless and windowed mode to get it to actually fill the screen properly. First launch had the bottom cut, after that it kept going into a small window

Oh darn. We saw this on the Steam Deck, but I thought we'd fixed it. I'll look into it further and see what I can do.

View this comment - View article - View full comments

Quoting: Purple Library GuyIs there a sort of "down time chatting at the safe house" thing like in Shadowrun?

Never played Shadowrun, so I can't speak to that specifically. We have some between-mission "conversations" that unlock at various points in the game, but they're not interactive. There's also a whole bunch of cutscenes with plenty of dialogue and scene-setting.

View this comment - View article - View full comments