05:52fdobridge: <redsheep> Okay I was able to get a detailed report that covers most of how of how the Vulkan profiles differ between vkd3d-proton and nvk (properties were hard to compare) and here it is
05:52fdobridge: <redsheep> https://cdn.discordapp.com/attachments/1034184951790305330/1241629568415039508/results.txt?ex=664ae525&is=664993a5&hm=a32f2af82d2370d770e0023a5daa1d992d7e6e23be0e493a04de93509c9c9252&
05:57fdobridge: <redsheep> This basically confirms that for the latest vkd3d-proton the upper part of the tracker is correct if we don't care about anything "optional" or "optimal". Further, it confirms that the shader model areas still contain what is needed
05:59fdobridge: <redsheep> There are a few new things I learned though. First, it seems that while the maximal reconvergence extension is advertised, the feature is not. Second, while the shader models contain the correct information this data shows that shader models 6.6 and 6.7 are just optimal/optional stuff, and if we want to start tracking all of that stuff there's a TON more to include. This probably means closing shouldn't block on those.
06:01fdobridge: <redsheep> While testing this I also found that RADV is failing to actually advertise the present id and wait extensions in vulkaninfo, even though present wait is enabled for radv in features.txt
06:03fdobridge: <pixelcluster> are you sure it’s not just that eg you’re under x and they’re supported under wayland only?
06:04fdobridge: <redsheep> I had a friend pull the json, and they were on a wayland session. Still, maybe something like that was going on? I am not sure, I didn't dog too deep on that
06:04fdobridge: <redsheep> didn't dig*
06:05fdobridge: <redsheep> Also, I am on an x11 session, so if anything would explain that due to current session type it would be the other way around, given nvk is not listed as missing that in the report I sent above
06:43OftenTimeConsuming: What ptstate does nouveau default to? It doesn't list the current one under /sys/kernel/debug/dri/0/pstate unless I set one. I want to swap between power state 0f and the default (power state 07 is unstable).
06:59fdobridge: <gfxstrand> We definitely advertise both the maximal reconvergence extension and the feature bit.
07:13fdobridge: <redsheep> Is my vulkaninfo just busted or something?
07:13fdobridge: <redsheep> https://cdn.discordapp.com/attachments/1034184951790305330/1241649902992228402/VP_VULKANINFO_NVIDIA_GeForce_RTX_4090_NVK_AD102_24_1_99.json?ex=664af815&is=6649a695&hm=5d480a03fe66981469cdeef76eda128c0caec3d081eb9729d791613d65948f39&
07:13fdobridge: <redsheep> Just searching reconvergence finds the extension but not the feature
07:15fdobridge: <redsheep> Oh wait. It's not just not enabled, it's not *there*
07:15fdobridge: <redsheep> Let me see what the vkd3d profile has
07:15fdobridge: <gfxstrand> https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/nouveau/vulkan/nvk_physical_device.c?ref_type=heads#L434
07:16fdobridge: <redsheep> vkd3d expects this, and it simply is not a thing in my json
07:16fdobridge: <redsheep> ```"features": {
07:16fdobridge: <redsheep> "VkPhysicalDeviceShaderMaximalReconvergenceFeaturesKHR": {
07:16fdobridge: <redsheep> "shaderMaximalReconvergence": true```
07:17fdobridge: <redsheep> If you do vulkaninfo -j do you get that feature?
07:23fdobridge: <redsheep> I am just using the arch package for vulkan-tools, maybe 1.3.269 is too old to know to list that, but if that's the issue why does it show the extension and not the feature?
07:23fdobridge: <pixelcluster> ah yes that is the issue
07:23fdobridge: <pixelcluster> the extensions are just a list of strings
07:24fdobridge: <pixelcluster> but for the features, vulkaninfo actually has to know the struct exists and actively query it
07:24fdobridge: <pixelcluster> the extensions are just a list of strings returned by the driver, vulkaninfo just relays those (edited)
07:24fdobridge: <redsheep> Ok, thanks for the explanation. That makes sense
07:24fdobridge: <redsheep> False, alarm then, all is well
07:25fdobridge: <redsheep> False alarm then, all is well (edited)
07:25fdobridge: <gfxstrand> Yup
08:08fdobridge: <!DodoNVK (she) 🇱🇹> Meme distro moment (my lib32 package is much newer)
08:11fdobridge: <redsheep> Yeah it looks like 1.3.269 is about 6 months old so, not great. Still maximal reconvergence is really new, so even a reasonably new package might not done it
08:12fdobridge: <!DodoNVK (she) 🇱🇹> I'm going to sync that package with the recent vulkan-headers update later (so it will be very new)
08:14fdobridge: <redsheep> Wait. Which package are we talking about? Do you mean your nvk aur package? From what I was seeing it looked like vulkaninfo comes from vulkan-tools or vulkan utils, or vulkan sdk, depending where you are looking
08:17fdobridge: <redsheep> Ok just did pacman -F, it comes from vulkan-tools for me for sure, which is not a dependency in your package
16:15Sarayan: Hi, I have a laptop with IntelAlder Lake-P GT2 and GeForce RTX 3060 Mobile, with the thunderbolt connected to the nvidia. After the last update of things it's a mess, and my main question is what nvidia driver should I try to actually make work, nouveau, nvidia or nvidia-open?
16:15Sarayan: Right now all three fuck up in a different way
16:35fdobridge: <rinlovesyou> definitely seeing some magic happening here, no_cbuf eliminates the perf problems that Yakuza 0/Kiwami 1 are suffering from when you look into the crowd. From 15-20 fps to a locked 60 through and through! (the game hard locks to 60fps. Different times i guess)
16:44fdobridge: <rinlovesyou> might definitely be seeing some perf regressions in other areas
16:44fdobridge: <rinlovesyou> might definitely be seeing some perf regressions in other areas, i.e Just Cause 4/Minecraft shaders (edited)
17:02fdobridge: <rinlovesyou> definitely seeing some magic happening here, no_cbuf eliminates the perf problems that Yakuza 0/Kiwami 1 are suffering from when you look into the crowd. From 15-20 fps to a locked 60 through and through! (the game hard locks to 60fps. Different times i guess). If only they wouldn't *freeze* with nvk (edited)
19:38fdobridge: <!DodoNVK (she) 🇱🇹> lib32-vulkan-tools
20:51fdobridge: <redsheep> Yeah the performance characteristics of that branch are really interesting right now, I'm excited to see where it goes after the nak work
21:21fdobridge: <rinlovesyou> it was very exciting to see that this already solves the yakuza thing