The Tink 4K already supports this if you disable the low-framerate BFI limit, and adjust the BFI settings. You can have
For nativeHz:frameRate ratio of 120:30, you'd be able to do the following.
- 1 visible / 3 black
- 2 visible / 2 black
- 3 visible / 1 black
Unfortunately 30Hz BFI does flicker uncomfortably. Personally I'd rather tolerate framegen lag or tolerate 60fps than 30Hz BFI. However, I strongly advocated for the ability to do 30Hz BFI for integer-divisible refresh rates (60,90,120,150,180,210,240...) which you can all do with the Tink 4K.
However, it doesn't detect the unchanged frame of a 60Hz signal, so it's crapshoot whether you're getting 1 additional frame of latency or not. That frame-synchronization feature would be so niche as not to be worth supporting (Sadly), given the limited number of people willing to tolerate 30Hz BFI. (60Hz and 50Hz BFI is already flickery, but more tolerable).
I do not recommend 30 Hz BFI if you have not pre-tested it with other software.
You can test 30 Hz BFI using TestUFO at 120 Hz.
Flicker Warning for Photosensitive Individuals
1. Set your screen to 120Hz
2. I have a hidden test, http://testufo.com/bfi-photo ...
3. Configure to 1+3, 2+2, or 3+1 for Visible+Black. That 4-frame cadence gives you a 30Hz flicker at 120Hz.
4. Stare at it for like a few minutes.
5. See how you feel afterwards
Note: If you are stuck at 240Hz (e.g. monitor does not have a 120Hz preset in Control Panel), double up the numbers 2+6, 4+4 or 6+2 to simulate BFI adjustments at 120Hz.
---
Related note.
While DLSS/FSR/etc is generally useless (currently) for esports that already maintains high frame rates, this type of game (GTA6) generally isn't nearly as latency critical. GTA6 would be an excellent candidate for framegen.
Therefore, I recommend waiting for the PC version and using one of the higher-quality framegen algorithms that will be available by its release. The current state of art in framegen appears to be DLSS 4.5 and its 6x framegen feature, when the priority is blur busting with minimum AI slop (so avoid DLSS 5 if you're more interested in temporal fidelity over spatial fidelity)
Generally in non-latency-critical games, using the "framegen compromise" can even become the overall preferable blurbusting method (than 30Hz BFI) for CP2077/GTA6 type games that aren't as latency intensive as a competitive esports game. Especially if you're playing the single player story mode.
While the "AI slop framegen" and "neural rendering" is an ongoing debate -- A better-than-average framegen on a base 60fps frame rate, for this type of game (CP2077, GTA6, Witcher, etc) now tend to produce excellent results for a 240 Hz OLED as a more ergonomic blur busting alternative to BFI, since the artifacts:fun ratio leans heavily more fun than it used to be.
Interestingly for my most recent round of CP2077 (Liberty DLC playthrough for first time while using 5x framegen)...
...I even turned off DLSS scaling and used DLSS 100% just for framegen, when playing my last round of CP2077. The artifacts of "DLSS spatial only" versus "DLSS temporal only" actually had slightly less fakeness for about 80-90% of CP2077 motion. If you're already tolerating DLSS scaling, try turning off DLSS scaling (and turn off any enhancements like DLSS neural rendering), and using only DLSS framegen if you have a low-pixel-density 240Hz OLED. It ended up being preferable!
You often notice artifacts no matter what kind of DLSS, but I preferred to milk the Hz of my 240Hz+ OLEDs, and getting motion blur reduction via brute framerate, with RTX ON. So one tactic is no DLSS supersampling, but only DLSS framegen. Set the in-game cap to the pre-multiplier pre-DLSS framerate, with a headroom to avoid the lag-yoyo effect (of VRR framerates hitting maxHz). For example, ~57fps CP2077 cap for 240Hz OLEDs for 4x DLSS.
I would assume the experience would be (roughly) similar with GTA6, assuming the DLSS framegen model doesn't glitch with GTA6 imagery, given GTA6 is also an open-world game with a story mode, though it will also have an optional online multiplayer mode (not as latency critical as FPS shooters).
