![]() ![]() The other day I was watching WWE Network Show Down special event from Saudi Arabia on the TV and throughout the entire show (3 hours) it buffered every 10 seconds causing the entire show to stop/go while it buffered. I figured I had nothing to lose so I clicked on Yes and bingo the mouse pointer appeared on the TV screen. This got me into a panel of various settings and then at the bottom of the list I see this button that says "Reset Video - Yes No". Why I had to do this is beyond me as I never mess with the TV settings but I just thought I would give it a try so I picked up the TV remote control and clicked on Settings. I understand about MS updating behind your back and for awhile after you made you post 9 I thought maybe that just might be the issue but it turns out that it was the TV. I guess you may want to try to change the desktop theme or mode to see if it would have any effect. switching from a standard window theme to an Aero theme, or vice versa). Or, perhaps the theme, or scheme, of the desktop was changed recently that is leading to the problem (i.e. And perhaps that capture doesn't capture the mouse, so you "loose" it. It may be that something happened, so that rather than treating the two displays as two displays that need to be drawn on to maintain the same image, something else is happening, essentially, the screen is drawn once, and then a screen capture is done and displayed on the second monitor to "replicate" it. the old Aero mode, and current Win10 modes, there are various options to how displays could be replicated. Now with displays being composited, or built in memory before display, i.e. Everything drawn no the first display is also drawn on the second display so the graphic card is doing a lot of work internally to maintain the replicated display. ![]() And the reason for that, is that to duplicate a display wasn't a simple matter of drawing the display once and through hardware display it on two monitors, the display actually had to be drawn twice. It sounds like the mechanism of how Widows is replicating the second screen has changed somehow.īack in the day, when we would set up a PC to duplicate a display on a second monitor, we found that the update of the display took a performance hit. Its not like the cursor is implemented as a separate feature of the HDMI video specification. But this problem is either an edge case or something else in combination with win 10 CU is causing it since it is not widely reported on technet.I'm not sure how an HDMI cable could affect only the cursor, and not the rest of the video signal. So basically Microsoft did something that broke scaling support for older apps (MS Office as well). Or at least the app needs to be updated (RDCman 2.7 was released in 2014, and it was updated at the time to support win 8, 8.1, 2012). That that is not true after Win 10 creators update. This was the basis for the workaround posted on the technet - if the app implements scaling correctly then there should no be any problems. But RDCman is per-monitor-aware when it comes to scaling (just like mstsc). The problem also affects MS Office (word, outlook 2016) applications - the cursor disappears or is cut there as well (the effect sometimes goes away after PC restart as well).Īll of the mentioned RDP programs use system scaling. The problem affects all of the RDP applications (RDCman, mRemoteNG, MobaXterm, Terminals) other than mstsc. So I restart my PC and check if the problem is there and restart again until I can see the cursor. ![]() Different scaling will cause a different effect and sometimes after restarting the PC the problem will go away on some scaling settings (125% in my case). The problem happens only after Win 10 Creators Update and it happens on any scaling setting that is higher than 100%. I've had an opportunity to test this problem on a PC with a single 4k monitor. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |