New comment by ArmedAviator on void-packages repository

https://github.com/void-linux/void-packages/pull/32100#issuecomment-885068044

Comment:
That was my thought, too.  I double checked and do have the 32-bit libraries installed.

> 
> rich@area51 ~ $ xbps-query -s nvidia*
> [*] nvidia-470.57.02_1            NVIDIA drivers for linux - Libraries and Utilities
> [*] nvidia-dkms-470.57.02_1       NVIDIA drivers for linux - DKMS kernel module
> [*] nvidia-gtklibs-470.57.02_1    NVIDIA drivers for linux - GTK+ libraries
> [*] nvidia-libs-470.57.02_1       NVIDIA drivers for linux - common libraries
> [*] nvidia-libs-32bit-470.57.02_1 NVIDIA drivers for linux - common libraries (32bit)
> 
> rich@area51 ~ $ ls -lh /usr/lib32/libnvidia-glvkspirv.so.*
> -rwxr-xr-x 1 root root 15M Jul 22 04:29 /usr/lib32/libnvidia-glvkspirv.so.470.57.02

This has happened before during the 460 series of nvidia driver updates and it just "fixed" itself after an update one week.  I do recall that the drivers were not updated when things began working again - maybe something built against nvidia libs in steam/proton?  I don't know.

With that said, it seems this package is good to go and that my problem is coming from Steam/Proton itself.