21 Oct 2024 |
Atemu | Is it though? From what I know, it can be accessed a bit more finely than that. Valve uses the motion estimation part of hwenc for SteamVR on Windows for VR smoothing purposes | 09:00:03 |
Sami Liedes | Well, the idea for having a separate cached copy of some humongous game for each GPU architecture (combination) doesn't feel beautiful either. | 09:00:43 |
K900 | In reply to@sliedes:hacklab.fi Well, the idea for having a separate cached copy of some humongous game for each GPU architecture (combination) doesn't feel beautiful either. You don't need a separate copy? | 09:08:05 |
K900 | The whole "separate copy per target" thing is very much a CUDA-ism | 09:08:21 |
K900 | Games don't do that | 09:08:46 |
Sami Liedes | Yeah, not for games, true. | 09:35:17 |
Marie | In reply to @k900:0upti.me https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/blob/main/docs/container-runtime.md oh TIL there are newer steam runtimes than 3, but not released yet and why does 5 have no tf2 name anymore :( | 09:51:59 |
K900 | Because it's not stable yet | 09:54:35 |
Sandro 🐧 | In reply to @atemu12:matrix.org Updated my write-up on a potential new hardware accel driver API in a new issue https://github.com/NixOS/nixpkgs/issues/350162 OpenGL through zink and nvidia? Also doesn't mesa kinda do everything? libva for i915? | 12:55:57 |
Atemu | I don't quite understand what the first question is | 13:09:55 |
Atemu | Mesa does a ton for a lot of hardware but there are more than enough drivers that aren't mesa | 13:10:28 |
Sandro 🐧 | can you sort things like zink from mesa with nvidia backend? | 14:30:29 |
K900 | Sort how? | 14:32:01 |
Sandro 🐧 | in the new option structure that was proposed | 14:53:59 |
K900 | Why do you need to sort things? | 14:55:14 |
Sandro 🐧 | sort them into those options | 14:56:42 |
Sandro 🐧 | probably Germlish | 14:56:46 |
K900 | You'd just enable both Mesa and Nvidia and it'll work the same way as now | 14:57:16 |
K900 | Zink doesn't really exist as a thing separate from the rest of Mesa anyway | 14:57:30 |
Atemu | In theory, you'd be able to choose on a per-driver level. You'd simply choose nvidia as the VK driver and zink as the OGL one | 15:49:37 |
Atemu | In the "lite" version that would only be able to choose the driver package, this would still work as there is no other OGL driver in mesa that works with the proprietary nvidia module | 15:50:15 |
K900 | Note that we can't expose options that define a single driver | 15:54:28 |
K900 | That's incorrect | 15:54:34 |
Atemu | Why not? | 15:55:03 |
K900 | Because multiple GPUs per computer is normal now | 16:01:12 |
Atemu | It'd be up to the user to configure that of course | 16:04:05 |
Atemu | If they have a multi-gpu system, they wouldn't disable the other GPU's driver | 16:04:27 |
K900 | What I mean is we can't have an option that says "only use this driver name for OpenGL" or whatever | 16:06:24 |
Atemu | Of course we can have the option | 16:06:53 |
Atemu | It's up to the user to decide whether that's what they want or not | 16:07:01 |