summaryrefslogtreecommitdiff
path: root/Source/Core/InputCommon/ControllerInterface/Device.cpp
diff options
context:
space:
mode:
authorJosJuice <josjuice@gmail.com>2017-11-27 14:31:52 +0100
committerJosJuice <josjuice@gmail.com>2017-11-27 14:32:27 +0100
commit6344997fad69b82881cf83d24a41b5573bd71c72 (patch)
tree74930906663ab8b3390ab3ef777e70a5814f5057 /Source/Core/InputCommon/ControllerInterface/Device.cpp
parent9fe5dd7fa9996989b124b5f1a8d2190a689384ad (diff)
Don't forcibly enable immediate XFB in game INIs
Forcing people to use hacks is a bad idea in general, and there are two practical problems with doing it for immediate XFB in particular: 1. It breaks the GC IPL, which some users run when launching games. 2. Competitive players don't necessarily want the lowest possible latency - they might want the latency that's the closest to console, so if they're playing locally with a low-latency monitor, they might not want to use immediate XFB. (This isn't a theoretical concern - I've seen Melee players want to increase their latency.) Besides, it feels arbitrary that just these five specific games should have immediate XFB forced on.
Diffstat (limited to 'Source/Core/InputCommon/ControllerInterface/Device.cpp')
0 files changed, 0 insertions, 0 deletions