| 19 Jul 2025 |
 K900 | The AMD driver can inject FSR2 into basically anything | 07:17:22 |
| K900 | And they also have "AMD Fluid Motion Frames" which is kinda FSR3 frame gen retrofitted to be purely spatial | 07:17:42 |
| K900 | That can be injected into uh | 07:17:54 |
 olivia | my impression reading through the vkd3d-proton stuff earlier was that there was a bunch of driver interaction that existed for effectively no reason | 07:17:58 |
| K900 | Some things, but not all of them? | 07:17:58 |
| K900 | I don't know why | 07:18:02 |
| K900 | Oh do you mean for FSR4? | 07:18:13 |
| olivia | is fsr4 different? | 07:18:21 |
| K900 | Yes | 07:18:25 |
| olivia | structurally | 07:18:26 |
| olivia | fun | 07:18:28 |
| K900 | I think what's going on is they basically want to move the actual scaling algorithms into the driver | 07:18:45 |
| olivia | this stuff is so fucked | 07:18:46 |
| K900 | So that the game doesn't have to constantly update to get better upscaling | 07:18:59 |
| K900 | Instead it just asks the driver to do the thing, and the driver does the thing however it considers optimal | 07:19:14 |
| olivia | hmm | 07:19:25 |
