If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

And yet the latest 331.xx branch still doesn't have XOrg 1.15 support. I suppose it is kind of cool that NVIDIA has basically went back to their legacy drivers and added XOrg 1.15 support, but it seems kind of backwards that their latest drivers supporting their most recent cards are the last to get it.

And this is the only resolution that games see. Want to change to a lower res. because the HUD is too small and you can't see/read it? Want to improve fps rate? Tough luck.
Also, if I change the resolution through nvidia-settings to a lower one, half of the desktop is out of the screen, because they removed the scaling options. (or something else is missing, idk)
The wine devs have a relevant commentary on the subject in the source code, but I can't find the link right now.

I also tried to change the video card on my laptop to an AMD one to use the open driver, but found out that HP (my laptop is a HP), only allows their overpriced, outdated hardware parts to work. Any other video card, wi-fi card, you name it, is blocked by the BIOS, which is encrypted, cannot be modded, and cannot be downgraded.

Same experience with Sony SD cards years ago, since then I swore to God to always google about the product before even thinking to buy it because minutes/hours of googling might save you months/years of frustration.

Well, it has some xrandr support, but it's incomplete. Only the native resolution of the screen is exposed through xrandr 1.2+, which makes it kinda useless.

It's very complete, actually. That is how xrandr1.2 is supposed to work if you go strictly by the spec, which is what Nvidia is doing. If the app does xrandr1.2, it's supposed to provide detailed info about what it wants. Few apps do so, but you could argue that's an app problem. You could also argue it's inefficient, each app having to duplicate detailed resolution handling.

You only see one resolution, because your display reports it supports only that resolution. Which is completely true. If you want other resolutions, set up metamodes with appropriate ViewportIn and ViewportOut parameters. Yeah, there should be a facility to make this simpler, like the xrandr properties that open drivers have. But that's not about not supporting xrandr1.2, it's about supporting it too strictly.