Attentat 1942, a historically-accurate adventure about World War 2 from developer Charles Games has recently switched to the Unity game engine and is looking into Linux support.
Originally released in 2017, it was made using Adobe AIR which dropped Linux support many years ago and Adobe themselves won't even be supporting AIR at all directly as it's moving over to HARMAN. For game development, there's now far better tools available for cross-platform development. The developer actually made a little blog post on Gamasutra about moving to Unity.
For Linux support, out of seemingly nowhere the developer revived a years old topic on Steam themselves to mention this:
Hey hi from 2020! We have started inquiring into possible Linux port! We have switched the whole Attentat 1942 into new engine which is much more versatile so that kind of untied our hands. I can't promise anything definitive, but it is something we are considering and finding if it's even technically feasible (video codecs being main culprit). Thanks for your interest and patience, we'll keep you updated!
That's good news. I've also given them a tip on the codec issue, which Unity apparently still doesn't communicate well enough to developers. If you're using Unity, for Linux and video codecs you need to use either webm / vp8 or ogv (info here) otherwise it's black screens and freezing as I've seen too many times in Unity games.
You can follow Attentat 1942 on Steam. Original trailer is below:
Direct Link
If you're using Unity, for Linux and video codecs you need to use either webm / vp8 or ogv (info here) otherwise it's black screens and freezing as I've seen too many times in Unity games.
Is this a Unity problem? I thought the issue with games was that they weren't using platform codecs, but the Unity documentation there implies they do, and playing h.264 files on Linux hasn't really been a problem for quite a long time - unless your distro takes a free-software-only stance, which you'd already have needed to work around to install games.
Yes, it's specific to the Unity video player. I see it quite often when testing games for developers. The Unity docs make it very clear what they work with on Linux, as I linked.If you're using Unity, for Linux and video codecs you need to use either webm / vp8 or ogv (info here) otherwise it's black screens and freezing as I've seen too many times in Unity games.
Is this a Unity problem? I thought the issue with games was that they weren't using platform codecs, but the Unity documentation there implies they do, and playing h.264 files on Linux hasn't really been a problem for quite a long time - unless your distro takes a free-software-only stance, which you'd already have needed to work around to install games.
Yes, it's specific to the Unity video player. I see it quite often when testing games for developers. The Unity docs make it very clear what they work with on Linux, as I linked.Yeah, not doubting the accuracy of your reporting, just thinking that it's something that Unity could fix.
Is this a Unity problem? I thought the issue with games was that they weren't using platform codecs, but the Unity documentation there implies they do, and playing h.264 files on Linux hasn't really been a problem for quite a long time - unless your distro takes a free-software-only stance, which you'd already have needed to work around to install games.
When testing Encodya, I could play back the video file without problems manually, but it didn't run at all in the game in the first test version. So, it's Unity.
Last edited by Eike on 29 May 2020 at 9:45 am UTC
Interestingly, even on Windows, Intel had to write their own thing to grab a video stream from Unity so that it could be hardware accelerated.
See more from me