Let me start by saying everything is working fine except for the mouse input. My Comet is connected to a PC running Windows 11 with multiple displays. Windows is treating the Comet as an extended display which is fine, picture attached. The issue is the mouse isn't where it thinks it is so I'm not actually clicking on what I'm seeing, it's clicking somewhere else. This makes it unusable since I don't have working mouse input. Happy to screenshare and troubleshoot with you or test different things for the greater good. 
Shouldn't be "duplicated displays" instead of "extended display"?
I wouldn't say "should" be duplicate ... I would say this is a situation the Comet should be able to handle and still work correctly. If I wanted to connect and change the Comet to the main display or the setting to duplicate I'm not a le to send the WIN+P shortcut (if there's a way please share) or to right click the desktop and select Display and change it that way. I think this is a failure of the Comet to be adaptable to many situations if it's not able to handle this. What if after remotely doing a fresh OS install the Comet wasn't the main display? You'd be screwed?
1 Like
If you want the mouse to work on the secondary screen, please look forward to the relative mouse function in version 1.3.0. Under normal circumstances, COMET should be manually configured as mirror on the controlled computer for it to work properly.
2 Likes
I understand this might be hard to answer, but is there a timeframe you see 1.3 being released. Being on 1.1.1 now just trying to get an estimate.
The end of this month
1 Like