You can sign up to get a daily email of our articles, see the Mailing List page.
We do often include affiliate links to earn us some pennies. See more here.

LunarG has now officially rolled out 'DevSim', a rather fancy tool for developers to test their Vulkan games and applications against many different configurations.

Why is this interesting? Well, not every developer will have access to tens (and more) different GPUs. With DevSim, they technically don't need to, as they can use it to simulate various different configurations.

Here's how they describe it (read more in their news post):

The LunarG Device Simulation layer helps test across a wide range of hardware capabilities without requiring a physical copy of every device. It can be applied without modifying any application binaries, and in a fully-automated fashion. The Device Simulation layer (aka DevSim) is a Vulkan layer that can override the values returned by your application’s queries of the GPU. DevSim uses a JSON text configuration file to make your application see a different driver/GPU than is actually in your system. This capability is useful to verify that your application both a) properly queries the limits from Vulkan, and b) obeys those limits.

It's free as well, with the source included in their VulkanTools repository on GitHub.

Fantastic to see more like this out there for Vulkan, hopefully the more we see like this, the easier and more likely it will be for developers to use Vulkan, which can help bringing games to Linux become a bit easier.

Article taken from GamingOnLinux.com.
Tags: Vulkan
6 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 came back to check 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. Find me on Mastodon.
See more from me
The comments on this article are closed.
1 comment

Purple Library Guy Jan 24, 2018
Quoting: GuestBefore anyone gets the wrong idea, this essentially limits the capabilities of your system/driver reporting. It cannot be used to test something that doesn't exist at all.

Think things like maximum reported surface size (monitor resolution), buffer counts, memory sizes, etc.

Ah. So it's not some kind of ridiculous VM capable of actually simulating the activity of a bunch of different incredibly complex GPUs. That would have been a bit too amazing to be true. Something like that would require a pretty monstrous system to work anyway.
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.