Unigine 2.7.3 Released With Rendering Improvements But No Vulkan Support Yet

[phoronix]

Phoronix: Unigine 2.7.3 Released With Rendering Improvements But No Vulkan Support Yet

The high-end, Linux-friendly Unigine engine for powering games but seemingly more industrial/simulator applications these days is out with their last feature release of 2018...

http://www.phoronix.com/scan.php?page=news_item&px=Unigine-2.7.3-Released

[birdie]

And what about open sourcing Unigine? UE4 and CryEngine have long been open sourced and that turned out to be a net positive for them.

[Danny3]

Such a shame that there's no Vulkan support yet!

[humbug]

Such a shame that there's no Vulkan support yet!

Even for Unreal engine their Vulkan investment is focused around android.
Not much for PC (windows, Linux).

[uid313]

Oh, they are slow.
It seems like pretty much all engines these days have Vulkan support except Unigine?

[Leopard]

Oh, they are slow.
It seems like pretty much all engines these days have Vulkan support except Unigine?

Yeah , most of them have Vulkan support but not in a meaningful way.

For example ; Unreal and Unity sees Vulkan as a mobile api so they're mostly half ass this point. Not tested properly , in experimental state.

[pete910]

Must be a reason as to why no Vulkan support. Seems a little odd as initially it was supposed to have it from the start

[SgtH3nry3]

Yeah , most of them have Vulkan support but not in a meaningful way.

For example ; Unreal and Unity sees Vulkan as a mobile api so they're mostly half ass this point. Not tested properly , in experimental state.

Not entirely true. Vulkan is now the default rendering API in Unreal Engine 4.0 for Linux targeted builds. The problem lies mostly with too much going on in the Linux GPU drivers space, Linux compatibility of middleware and the all old chicken-egg situation.

First, even though major distros such as Ubuntu, Debian and Fedora, games usually "just work". However, there are still unsolved issues such as what windowing system to target, even though it is clear for most that Wayland-Weston will win. Second, there are the discrepancies between how nVidia, Intel and AMD approach Linux drivers for their graphics solutions. At the moment, AMD shows how its done, but nVidia holds a considerable position, and it is still unclear if they will change their approach when it comes to Linux drivers. All in all, there are too many uncertainties for game developers and engine developers. Technically, it all works fine and dandy but the problem is that there is too much going on when it comes to windowing systems, middleware and Linux graphics drivers for game developers to make the jump to Vulkan games on Linux.

[kayosiii]

Unigine designed the 2.0 version of their engine before any of the current generation graphics APIs were announced ash is pretty squarely targeted at high end hardware (not mobile devices). The Unigine Devs have done some tests and don't see much in the way of a performance boost with the current architecture using Vulkan vs using OpenGL so other features (features not typically found in other for purchase game engines) have taken priority.

A version supporting Vulkan will probably start with the number 3.

[Leopard]

Not entirely true. Vulkan is now the default rendering API in Unreal Engine 4.0 for Linux targeted builds. The problem lies mostly with too much going on in the Linux GPU drivers space, Linux compatibility of middleware and the all old chicken-egg situation.

First, even though major distros such as Ubuntu, Debian and Fedora, games usually "just work". However, there are still unsolved issues such as what windowing system to target, even though it is clear for most that Wayland-Weston will win. Second, there are the discrepancies between how nVidia, Intel and AMD approach Linux drivers for their graphics solutions. At the moment, AMD shows how its done, but nVidia holds a considerable position, and it is still unclear if they will change their approach when it comes to Linux drivers. All in all, there are too many uncertainties for game developers and engine developers. Technically, it all works fine and dandy but the problem is that there is too much going on when it comes to windowing systems, middleware and Linux graphics drivers for game developers to make the jump to Vulkan games on Linux.

Like you said , it is default for Linux and i consider that as a loss. Because that just shows how they treat the api , second class citizen. Like they do with Linux.

If it was default on Windows too , i would say hell yeah but it is not.