RTSS' Scanline sync equivalent for linux?

[deama]

So for linux gaming, is there a scanline sync feature alternative? Something that allows the user to adjust the tearline, to hide it. This would also have to work for games under wine too I'd imagine.

[Chief Blur Buster]

So for linux gaming, is there a scanline sync feature alternative? Something that allows the user to adjust the tearline, to hide it. This would also have to work for games under wine too I'd imagine.

Not currently, unfortunately.

Someone with classic beam racing / raster interrupt knowledge (and applying it to modern GPUs, ala Tearline Jedi) would have to create this.

[deama]

So for linux gaming, is there a scanline sync feature alternative? Something that allows the user to adjust the tearline, to hide it. This would also have to work for games under wine too I'd imagine.

Not currently, unfortunately.

Someone with classic beam racing / raster interrupt knowledge (and applying it to modern GPUs, ala Tearline Jedi) would have to create this.

Can RTSS be used in wine? Including it's scanline sync feature?

[Chief Blur Buster]

Can RTSS be used in wine? Including it's scanline sync feature?

Hugely doubtful.

<Programmer Technical>
I doubt that the D3DKMTGetScanLine() reports accurate data in the GPU drivers for WINE.

If an open source programmer wishes to virtualize D3DKMTGetScanLine() in a simulation, by improving the WINE source code, as a time-based offset between two VBlanks, then it is theoretically possible, although RTSS is a driver hook, and I don't know if driver hooks works in WINE.

It's kinda a low-level call, that I've never seen successfully virtualized in any emulators or virtual machines on another OS than its host, though it is not impossible -- though it requires an open source programmer familiar with the raster delivery pipeline of pixel delivery from GPU to display (programmers who used to do raster interrupts in the olden 8bit days of the 1980s, will learn this kind of stuff fairly quickly, but some modern programmers will probably stare blankly at these kinds of concepts)

An estimated scan line number can be extrapolated as a time-based offset between two vertical blanking intervals, so no direct GPU access to a raster scanline register is needed, but knowledge of ModeLines is also an asset, so you can get a Vertical Total, to know how many scanlines there are between the vertical blanking intervals (where the last scanline finishes -- bottom edge of screen -- finishes transmitting out of the GPU output, but before the blanking interval that separates refresh cycles)
</Programmer Technical>