| T O P I C R E V I E W |
| pbrown |
Posted - Feb 12 2009 : 12:06:13 AM
I'm running with build 1715 in VS2008 on 32-bit Windows Vista. I connect to it via Remote Desktop from a system running 64-bit Windows Vista.
When access my system locally, I have no display-related problems.
When I am connected to the same system via Remote Desktop, I am getting a number of display-related problems enumerated below. This occurs if I have VS2008 running before connecting via remote desktop, and it also occurs if I restart VS2008 while remoting in.
When I open a file in the editor via VAX enabled, it displays normally. If I page up or down, the contents of the editor window don't visibly change at all. (The toolbar thingy displaying the function that the cursor is in does update.) When I move the cursor up or down, it leaves behind a bar-shaped outline (as though the cursor didn't erase). Once I move the cursor past the bottom of the screen, it appears to smear the contents of the bottom-most line upward. After scrolling down 50 or so lines, my editor window displays ~50 slightly garbled instances of the line that was a the bottom of the screen.
When I disable VAX, everything displays normally. Disabling various display-related features in VAX (including extended syntax highlighting) seems to have no effect.
I assume my problem is connected with the change in 1715 purporting to fix remote desktop-related flickering. I can confirm that I am seeing no flickering, but that's because the screen isn't refreshing at all. :-( |
| 7 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Mar 30 2009 : 09:12:28 AM
case=23919 is implemented in build 1721
To control Remote Desktop display optimization, use this registry entry:
HKCU\\Software\\Whole Tomato\\Visual Assist X\\VANet9\\OptimizeRemoteDesktop = 01
Use VANet9 for Visual Studio 2008
Replace VANet9 with VANet8 for Visual Studio 2005, VANet for Visual Studio 2003, or VA6 for Visual C++ 6.
Default value is 01, which enables optimization. Set this value to 00 to disable. Optimization is disabled automatically for Vista-to-Vista sessions with Aero enabled.
|
| feline |
Posted - Feb 16 2009 : 12:41:48 PM
I am currently connected from a Vista machine to a winXP Pro machine, and while I selected 32bit colour in the remote desktop settings, the display does not seem to be running in 32bit colour.
I am not sure why, and I have not actually tried to find out why. |
| pbrown |
Posted - Feb 13 2009 : 6:15:13 PM
One other piece of data for you -- after I remoted into the same system using the Linux remote desktop client, I noticed that the "24 bit" mode that worked for me was actually falling back to 16 bits (5/6/5). The Windows client is behaving the same way.
So the only actual "True Color" setting is the 32-bit version that doesn't work. |
| feline |
Posted - Feb 12 2009 : 7:47:31 PM
We are adding a setting in the next build to turn off the optimisations for remote desktop, which should fix this problem:
case=23919
This does not really get to the root of the problem, but it should help. |
| pbrown |
Posted - Feb 12 2009 : 5:24:23 PM
I've done some more experimentation on the system where I reproduced the failure. The failure is connected to the display settings specified when connecting to the host system.
On the Remote Desktop connection "Options" screen, my settings for a failing configuration were:
Display:
Remote Desktop Size = full screen
Colors = Highest Quality (32 bit)
Display the connection bar = checked
Local Resources:
Sound = leave at remote
Keyboard (windows keys) = in full screen mode only
Local devices = printers, clipboard
Experience:
LAN (10 Mbps or higher), all boxes checked
If I change the color bit depth to 16 or 24 bits, I have no obvious display-related problems with 1715. So the problem is specific to 32-bit depth. I hope that helps narrow down the problem.
I have been heavily using remote desktop into the same host system with the same client settings for many months, running lots of different apps. I have had no display-related issues other than this new issue with 1715. |
| pbrown |
Posted - Feb 12 2009 : 2:20:04 PM
quote:
Originally posted by feline
What video card are you using on the two machines? Are you using the latest drivers on both machines?
The Vista32 system I am remoting into and running VAX on has an NVIDIA GeForce 7600 GS. The Vista64 system I am using is a laptop with an NVIDIA GeForce 8800M GTX. Drivers for both are recent but not "latest".
I am not experiencing anything like the ATI BSOD referenced in the other thread. My understanding of Remote Desktop is that it shuts off the display driver on the target system and instead substitutes a software-based display driver. Most likely, there is some bug causing the ATI driver to blow up when the OS shuts it off.
I did one quick test, and the plot thickened. I connected to the same host system from a third system -- my test system, a desktop running Vista32 with an NVIDIA Quadro FX 4600. I get no corruption -- scrolling up and down worked well. The visual settings of the remote desktop client are different; maybe something there is relevant. I'll do some more experimentation this evening and let you know what I find. |
| feline |
Posted - Feb 12 2009 : 10:01:50 AM
What video card are you using on the two machines? Are you using the latest drivers on both machines?
Several users have reported that the changes have helped them with remote desktop, but you are not the only person reporting problems. This thread is interesting, if rather depressing:
http://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=8495
and indicates that some video drivers can cause a lot of problems for remote desktop. |
