I have a sony vpcsc1afm which I use for intel widi regularly. I recently updated the widi software to 3.1.29. specs are:
intel hm65 chipset, latest graphics drivers and wifi 15.1.1
windows 7 64-bit
Now, the cursor is behaving wierd. In clone as well as extend mode, the cursor gets clipped to a smaller area vertically. so I can reach the left/right ends of my tv fully. But I cannot reach the full distance top/down on my tv with the cursor.
The remaining video image is still perfect - no problems with the actual video. ( with many different resolutions)
The funny thing is - the cursor's vertical distance seems to be compressed into a smaller vertical area. If i move my mouse all the way up, the cursor does not show that it is reaching the top of the video or some active window. however it i click there, it seems to do whatever should be done in the topmost part of the scree. For example, if i double click, a maximised window get normalized to its original size.
Also, there seem to be 2 cursors. If I drag a window onto the extended display, way till the top, one cursor follows movements correctly. There is a second ghost cursor below this cursor. When I finish dragging the window, the original cursor on the window bar disappears and only the ghost cursor below the actual position of the cursor is visible.
what is the issue here?
This was not present with widi version 3.0.13. I don't know if its because of the widi software update or the ptv2000 firmware update that came with it.
Thank you for your post.
There have been identified several things that interact with how the pointer appears on the TV, something that you can check that may help you is the mouse settings.
First open up the Wireless display software and go to the Properties. And click on the “Behavior” tab, check the last options “allow the pointer to change appearance based on context” if this does not improve the behavior of the cursor on the TV, then there is another place where you could change a couple of settings.
For this you would go to start, and type ‘Mouse properties’, then click on the option when it pops up.
Under the “pointers” uncheck both of the options at the bottom, “enable pointer shadow” and “allow themes to chance mouse pointer”. Then under the “pointer options” tab, un-check the “display Pointer tails” then just click on “Apply” and “ok”.
These pointer/curser related issues are actually being worked on, these can be fixed on future WiDi software releases.
Thanks for your reply. I tired all the things you suggested but there's no difference.
points to note: the 2 cursors I mentioned are not close by like the 'main+shadow or trail' type of thing. They are like an inch apart on the external screen.
The movable cursor on the screen is still getting clipped to a smaller vertical distance. No change in mouse or adapter settings is changing this behavior. note: this was not the issue with widi v3.0.13. the cursor used to behave correctly with that.
I too have the same issue described here. Let me see if I can describe it better and either get a solution or a recognition of the bug/problem which will be addressed in a future update:
Laptop - Lenovo Thinkpad x230
Intel WiDi version 22.214.171.124
Adapter - Belkin Screencast
Television - Standard Definition via RCA cables
Windows 7 64 bit
Picture is great and have no problems adjusting any settings. The only issue is as follows:
Though the picture is displayed correctly, the mouse cursor displayed does not display in the correct location. Horizontal location is correct. Vertical location is incorrect. The vertical location is offset by a factor of approximately 0.8. That is, if the correct cursor location is (x,y) with (0,0) being the center of the screen, the pointer is shown on the active portion of the display at point (x,0.8*y). When the cursor is centered on the screen, the mouse pointer is in the correct location. When the cursor is at the very top of the screen, the mouse pointer is in the right x-location, but about 10% away from the top of the active portion of the display. When the cursor is at the very bottom of the screen, the mouse pointer is in the right x-location, but about 10% away from the bottom of the active portion of the display. Even though the displayed location is wrong, a mouse-click will register at the right location (i.e. a click at the very top of the screen will register at the very top of the screen, not at the incorrect pointer location).
The mouse pointer display location is obviously decoupled from the rest of the display, and even from mouse click events, and for whatever reason, it is calculating the pointer display location incorrectly in the y-direction.
Please provide guidance as to a solution to this problem or acknowledgement of the bug. Thanks!
On this case I suggest you to install the latest wireless driver version 15.6.0 released the 2/20/2013, this might help in the specific case that you mention.
You can find the download at the following link:
Note that the full version for the 64 bit edition has the following size: 83.95 MB and the 32 bit edition have the following size: 75.47 MB.
Thank you very much for your post.
There is a new Intel® Wireless Display Software (126.96.36.199) available. Let us know about the results.
You may also want to reset or update the adapter’s firmware.
I tested it out today. i had high hopes from this but it has the same problems like 3.5.40 on windows 7 with ptv 2000.
Yes the cursor problem is solved. However, it keeps asking for the security code everytime. - it never remembers it.
why is this such a hard problem to solve?
Ty, indeed we recommend in all possible situations to use the drivers and software provided by the laptop manufacturer since those would have been tested with the exact computer set up you have.
Electronicsguy, thank you for the feedback, this seems to happen on some customer systems, and currently the recommendation is that if you use the latest generic update, to make sure that you also install the latest generic wireless driver (uninstall the ones that you have then install the latest one), and run the latest firmware for the push to TV adapter. We are currently investigating this situation.
The latest update (v4.xx) does indeed fix the cursor problem on my system but has its own set of problems (refer to my post above.) the problems are the same as outlined in the thread about the v3.5