To be clear, I was originally against the removal of DXVK_FRAME_RATE (and I still am), but since it has been decided that it is going to be removed, I see no point in keeping VKD3D_FRAME_RATE.

Yes, they are different projects, but the arguments for keeping or removing the frame rate limiter are mostly the same for both.

I don't understand, you're against it but are you propose to remove it here too? Even DXVK there is still a way through DXVK_CONFIG (which I think is stupid but ok), will there be a way through VKD3D_CONFIG?

And I saw your comments and interactions on the DXVK project and you don't seem to be against it, laughing and defending the removal encouraging the use of MANGOHUD is not something for those who are against it.

Regarding VKD3D_CONFIG, I don't know if there is currently a way to limit the FPS through that, but if there is, I think it would be kept with the same reason as DXVK's (to work-around some game bugs).

Even DXVK there is still a way through DXVK_CONFIG (which I think is stupid but ok)

Yeah, I also do. But the intention is to remove the option from be user-facing, and that certainly accomplishes it.

And I saw your comments and interactions on the DXVK project and you don't seem to be against it, laughing and defending the removal encouraging the use of MANGOHUD is not something for those who are against it.

I did not laugh or encourage the use of mangohud as an alternative. I am against the removal of DXVK_FRAME_RATE, but the project's lead developer decided against keeping it, so I don't have a reason to bother him anymore. I am just respecting his decision. If he was not convinced to keep it, even now, then I can only accept his decision and recommend viable alternatives due to the removal.

There is no config based alternative in vkd3d-proton, so I need no point in removing it for no reason. Nothing actionable in this issue.

Phillip's intention when removing it for DXVK was to make it not a user-facing feature. Even though DXVK and VKD3D-proton are different projects, I think this would make some people question something like: "Why can I limit my FPS easily in D3D12 games and not D3D9 games?"

I am in favor of keeping both env. vars. But if DXVK's was removed (which covers 5 Direct3D versions), I find it weird to keep it in VKD3D-proton and create this kind of inconsistency.

I really hope this stops spreading. It's already bad enough as it is that it was removed from DXVK.