Closed jspjutNV closed 1 year ago
Unless we can think of a place where missing guarbands will create visual artifacts/other issues I'm in favor of merging this ASAP. It fixes discrepancies I was seeing in the AimAssist
FoV visualization and seems to be a generally positive fix for the incorrect horizontal FoV specification.
Okay, I'll do a little testing to see if there are any edge artifacts with the TAA. I know there's other TAA issues, but we might want to avoid any huge additional issues. It's possible it'll be just fine. I'll test now, then merge it if I don't find any problems.
As we discussed, I'm not too worried about this introducing issues, it seems like we weren't necessarily filling guardbands in the compositing pipeline anyway, so hopefully this has minimal impacts. I'm happy to wait for more testing before we merge though.
I tested and don't really see anything broken. It also passes all tests. I'm merging it.
This PR sets the guard band to 0 instead of 64 like it was previously. This effectively fixes and issue that the configured FoV was 93.75% of the intended value (1920/2048) at 1080p.
I'm not sure if this is the fix we want for this issue yet.
IMPORTANT: This breaks backwards compatibility with older experiments since the FoV setting gives different results.