Quoting: DerpFoxMaybe Mumble is not adapted for that use case. I mean in integration within a game engine blending in the game UI. I'm also not sure that mumble provides any 3D space voice chat for in game use. Mumble is just a Voice/Text software after all as we meant it a few years ago.

If you mean positional audio, Mumble has that:

https://wiki.mumble.info/wiki/Positional-Audio [External Link]
https://wiki.mumble.info/wiki/HackPositionalAudio [External Link]

View this comment - View article - View full comments

Developers should just use Mumble which is open source. No need for any closed middleware for what is already available as FOSS.

View this comment - View article - View full comments

Looks promising, and they plan GOG release too.

View this comment - View article - View full comments

I'm more interested in the software side. Will Valve back full open stack for it with OpenHMD + Monado (OpenXR)? I hope they would, like they do with Mesa for GPUs.

View this comment - View article - View full comments

I remember Google mentioning, that they preferred the open source solution, so I don't think it's a blob. Most likely amdvlk indeed.

As for Stardock, they are coming from the common closed source development mentality, and probably are totally not used to open development model with public bugs and so on. That's why they are eager to talk to "vendors", but there is zero communication from them on any public Vulkan bug trackers.

View this comment - View article - View full comments

Quoting: liamdaweDoesn't seem like Stardock want to give any more details, I asked which vendor they were having issues with and what the issues were. The response was "We're working with both of them on it. Making iterative improvements." - so basically, nothing.

Oh, this indicates their issues are with amdvlk, and not with radv. Since radv isn't controlled by the vendor. And that makes sense, since Stadia is using amdvlk. It also shows that they possibly don't even test it on radv to begin with.

View this comment - View article - View full comments

Quoting: GuestEvery time there's something from Stardock about this, it seems like they're worried about something with Vulkan drivers, however have never really said what. RADV is open source; the community is considered the driver maker. Sure, the main developers might have corporate funding, but their work isn't hidden away, and I'm sure if Stardock were working with the community on this, we'd have heard about it. So to me the post doesn't make much sense. I'm still very curious about what the issue actually is.

Which I conclude means the issue is not with radv or amdvlk, but with some blob. Or Stardock aren't used to dealing with the idea of open drivers.

View this comment - View article - View full comments

Quoting: TheRiddickis d9vk and vk9 one and the same? I know the VK9 guy left for life reasons, is that code being pulled over to d9vk?

No, they are not the same. d9vk is based on dxvk. vk9 is a separate effort. d9vk looks more promising today.

View this comment - View article - View full comments

Since Wine is now bundling Mono, why is updating prefix with 4.7 still asking about installing a Mono package?

View this comment - View article - View full comments

Are they using OpenXR now, that it's out?

View this comment - View article - View full comments