Problems with tiled display topolgy (cru)
|
05-25-2025, 03:04 AM
Post: #1
|
|||
|
|||
Problems with tiled display topolgy (cru)
![]() ![]() ![]() |
|||
05-25-2025, 12:45 PM
Post: #2
|
|||
|
|||
RE: Problems with tiled display topolgy (cru)
the problem only occurs when i add tiles display topology not on the version of the displayid so no matter on 1.3 or 2.0 i have the problem with both :/
|
|||
05-25-2025, 03:47 PM
Post: #3
|
|||
|
|||
RE: Problems with tiled display topolgy (cru)
Why are you adding tiled display topology? What are you doing?
|
|||
08-13-2025, 04:37 PM
Post: #4
|
|||
|
|||
RE: Problems with tiled display topolgy (cru)
(05-25-2025 03:47 PM)ToastyX Wrote: Why are you adding tiled display topology? What are you doing? I'm not the OP, but just wanted to chime in about this. Recently, there's a guide going around about a tweak that supposedly reduces monitor latency and improves motion clarity (here). The tweak involves adding a Tiled Display Topology DisplayID 2.0 data block using CRU, which explains the OP's actions. According to the author of the guide, this “removes a 3 frame frame-buffer” by tricking Windows into running the screen as if it were a VR headset. I'm very sceptical about all of this, and while I have tried this tweak in some machines, I have not found any improvements at all (and it even caused issues in some cases). Perhaps some myth busting is required here. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)