D graphics acceleration over Remote Desktop. A friend of mine tipped me off to an interesting post on DIRECTXDEV about GPU acceleration over Remote Desktop. After some investigation with a couple of machines, I discovered that yes, it is actually true that you can run 3. D apps over Remote Desktop (Terminal Server). The key is that the machine you are remoting into must be running Windows Vista with a WDDM driver. Beyond that, it actually works as expected, although a bit slow. Some details: Again, the machine you are logging into must be running Windows Vista. The machine you are remoting from (running mstsc. Windows Vista. You do not have to use version 6 of the terminal services client - - version 5 that comes with Windows XP works fine. This doesn't appear to have anything to do with Avalon remoting, which allows Aero Glass to be shown over RDP. Supposedly you need both machines to be running Vista to do that, and you definitely need at least Ultimate or Enterprise on the target machine do it (I tried it with Business and it didn't work). D acceleration works fine with XP to Vista Business. You do not need any of the . They can all be disabled. Both Open. GL and Direct. D 9 work. Regular D3. D9 is fine; D3. D9. Ex is not necessary.
By default, Windows Remote Desktop will only work on your local network. To access Remote Desktop over the Internet, you’ll need to use a VPN or forward ports on.Direct. 3D 7 does not appear to work. I tried the old . Even scanline queries work (!), although I'm not sure what it actually reads. Now, the downside: it's slow. Really slow. So slow that I'd say it's basically unusable unless you're on a LAN, and a fast one at that. It looks like Terminal Services tries to send over the data from every Present(), and it blocks the app until that happens, instead of just skipping frames. It eats a lot of CPU in the process, too, instead of just waiting. I was just barely able to push 6. Virtual. Dub's D3. D9 display minidriver, which was throwing about 1. MB/sec across the gigabit LAN here - - probably about the best that the consumer- level hub can do. Readback doesn't seem to be a problem, at least not on the Ge. Force 6 and 8 cards I have here, because everything speeds back up if you cover enough of the 3. D window. Basically, this means that 3. D support is usable with apps that just use it for 2. D acceleration or otherwise static rendering, but anything dynamic like a video player or a game is going to be far too slow. It might be more viable if Microsoft had implemented frame dropping, but it looks like VNC may still be better for that. What this is definitely good for, though, is running GPU accelerated apps remotely. On XP, this isn't possible over Remote Desktop because as soon as you log in all your apps are pushed onto the software- only driver. Editions for personal computers Windows Vista Starter Much like its predecessor, Windows XP Starter Edition, this edition of Windows Vista was sold in 139 developing. I will go through each of these steps so that you can see exactly what needs to be done in order to properly get remote desktop working. First, make sure you set a. On Vista, though, they could continue to run on the server- side GPU, and performance isn't a problem if the app isn't displaying the result continuously. Comments. Comments posted: hehe, same is possbile with teamviewer, but slow. Frames in the nic driver for you cards on both machines? Tommy - 0. 8 0. 6 0. Hard to tell about the current version 3, but it looks like Team. Viewer started as a VNC clone, and was compatible up to 2. Not too surprising, since a lot of other products are structured that way, like Fog Creek Copilot. VNC reads the screen via Get. DC/Bit. Blt(), which works with 3. D even in XP, but is slow and also requires the console to be unlocked as well. The really bad part is detecting what parts of the screen have changed; polling is the default, but it's very CPU intensive and particularly sucks for console windows. Some versions of VNC can use a mirror driver to detect screen changes to optimize this (Ultra. VNC), but that kills all Direct. X acceleration. The ultimate remote configuration I've found is to have two machines that both have Remote Desktop and Tight. VNC enabled; RDP is for regular usage, VNC for 3. D, and if one of the machines gets wedged the other one can be used to unwedge it.. Didn't try the jumbo frame optimization. CPU usage on the client was pretty high, but it's only a 1. GHz P- M laptop with a mediocre network card. Phaeron - 0. 8 0. Over 1. 00 mbit lan the limiting factor could be the cpu power. Try to load a still image in a video player at 3. On my old p. 4 notebook the cpu is the bottleneck, about at quater screen it gets maxed out, while the incoming data is only 2- 3 mb/s. Gabest - 0. 8 0. If CPU usage on the client is indeed a problem (I somewhat doubt it), you could try some alternative client like rdesktop on Linux, it might or might not work better. Reimar - 0. 9 0. This is good since without it it was difficult to justify using 3. D in desktop applications, even if they did not require high framerates (or animation at all). Hopefully it, and DX1. D hardware between apps, will mean it isn't just games that take advantage of 3. D hardware in the future. I don't expect much to use it until Vista is the baseline, though. On this subject, I wish Remote Desktop would detect when parts of the screen are changing rapidly (e. If the region stopped changing the protocol could then update it with a lossless version, but for video I'd much rather have a good framerate than see lossless copies of every Nth frame. Leo Davidson (link) - 0. Uhm, some time ago I ran one of my Open. GL apps remotely via 1. Mbit DSL on that nice Win. XP dual Opteron in Lab - slow, but usable. No need for Vista or Direct. X 1. 0 either. Igor Levicki (link) - 2. It's true that graphics applications can run very slowly in Terminal Services, particularly over a WAN. Ericom Blaze is a software- based RDP acceleration AND compression product that provides a superior end- user experience over WAN and congested LANs. Besides delivering higher frame rates and reducing screen freezes and choppiness, Ericom Blaze accelerates RDP performance by up to 1. Ericom Blaze works with any standard RDP host, including VDI, Terminal Servers and remote physical machines. You can read more about Blaze at: http: //www. It always drops back to software Open. GL emulation. In addtion, I could not find any other Open. GL application/demo that could make use of GPU- acceleration in RDP sessions. The only thing that I could confirm to work was that non- fullscreen. Direct. 3D 1. 0 works WITH GPU- acceleration in RDP sessions. Here my setup: - NVIDIA Quadro FX 3. Administrator login via RDPAre there any further hints from your side what we could try to still get Open. GL to make use of GPU- acceleration in an RDP session? In addition, could you maybe point me to the original DIRECTXDEVarticle that you are referencing in the posting? I tried hard but could not find it. Thanks a lot in advance! Markus. Markus Neff - 2. Comment form. Please keep comments on- topic for this entry. If you have unrelated comments about Virtual. Dub, the forum is a better place to post them. How to setup a remote desktop and connect to your PC from anywhere. Remote desktop, which lets you access another computer over the internet just as if you were at the keyboard, is incredibly handy when you need to make changes to your home Minecraft server, get Steam to start downloading a game, or just keep an eye on a progress bar. As an added bonus, it’s also the tool of choice for providing occasional family or friend tech support. There are a few ways to setup a remote desktop, but if you’re running Windows you’ve already got one built right in: Remote Desktop Connection. To get started with this useful, yet under- used Windows feature, you’ll just need to be comfortable changing Windows and router settings and have a few minutes to configure and test it. Pave the way. As you might expect, allowing a remote user full control over a computer isn’t something that’s enabled by default. So to get it working, you’ll first need to adjust a few Windows and router settings. On the machine you want to access, click the Start button, then right- click Computer and choose “Properties”. Along the left side of the window that comes up, click “Remote Settings”. Under “Remote Desktop”, choose the option to allow remote connections that use Network Level Authentication. With NLA enabled, the computer will ask for a username and password before fully creating a remote session, which makes it less prone to denial of service attacks. The only caveat to NLA is that any computer you connect from will need to be running Windows XP Service Pack 3, Vista, or Windows 7. Click Apply to save your selection. As long as your account is Administrator level, you can ignore the Select Users button. Uncheck the “Allow Remote Assistance” option — you can always turn it back on if you actually need it later. Now that the computer is ready for remote desktop, you need to configure your router to forward TCP port 3. This step requires a bit of technical know- how, but it only takes a few minutes and is a good basic networking skill to know. If you need help with your particular router, check Port. Forward. com for specific instructions. While you’re at it, you might also want to make sure that your router is set to always assign the same local IP to the computer you’re connecting to — if it assigns a different one each time the computer connects, the forwarding rule won’t be much good. Note: Opening up ports on your router carries an inherent security risk. If you’re uncomfortable with that, check the “Other options” section at the bottom. Test it out. Now that everything is configured, you can try connecting remotely. To start, look up the public IP address of the computer you’re connecting to by going to Google and searching “what is my IP”. On another computer, click Start- Programs- Accessories- Remote Desktop Connection. When the RDC client comes up, click the Options button and spend a few minutes looking around at the all the features you can adjust. You don’t have to bother with most of these settings, but you should at least configure the connection speed under the Experience tab, and if you’re a keyboard shortcut addict take a look at the Keyboard options under the Local Resources tab. Once you have everything the way you want it, go back to the General tab, put the IP you looked up into the Computer field, and click Connect. If everything is setup correctly, you should be prompted for an account name and password. Once you’ve logged in, the other machine’s desktop should appear in a window, and you’ll be able to interact with it just as if you were there. Other approaches. If you don’t mind installing additional software, there are a couple of programs that do remote desktop without fiddling with router settings. My favorite tool for the job is Teamviewer, which is free for private, non- commercial use. Teamviewer supports multiple versions of Windows, Mac, and Linux, plus it has a “Quick. Support” version for giving someone one- time access to a machine. If you’d rather use a web app to keep track of your machines, Log. Me. In is a solid free option. Both products have i. OS/Android apps that are surprisingly good at handling a desktop environment with a mobile device touchscreen. Once you’ve got a remote desktop solution in place, you’ll be surprised how many uses you find for it. Forgot to put a file into your Dropbox folder? Want to start downloading a program you just bought so it will be done when you get home? Need to install updates on a newly reformatted machine, but don’t want to babysit it all day? Remote desktop can help in all those situations, and more.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |