I need to run my DirectX app with RemoteDesktopConnection because theconnectedPCis in another room. I found that,when using Remote Desktop Connection to runDirectX apps(DirectX SDK demos included), theycan work wellon Vista, but don't workon XP. Buton both OS, apps work well in localwithout Remote Desktop Connection. In other words,no matter whatthe OS version of client PC is, if the OS of connected PC(server side) is Vista,DirectX apps on the server sidework well, but in XP,the Direct3D APICreateDevice failed(ErrorCode = D3DERR_NOTAVAILABLE). So, what arethe new features of Remote Desktop of Vista? Doesit mean that DirectX is supported in Remote Desktop of Vista?

Nobody knows theDirectX-relatednew featuresof remote desktop?

Is there any way to avoid that CreateDevice failswhen app runsinremote desktop? Any idea is welcome, i am urgent...

Hi Omnix, First I would like to confirm the symptom. Would you like to say DirectX applications work properly when connecting from Windows Vista to Windows XP or Windows Vista? Does the issue occur when connecting from Windows XP to Windows XP or Windows Vista? For DirectX and Remote Desktop issues, Iwould like to provide you withthe following information for your reference: https://windowshelp.microsoft.com/Windows/en-US/help/f55326fa-e629-423b-abba-b30f76cc61e61033.mspx http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=599132&SiteID=1 http://www.computing.net/drivers/wwwboard/forum/1646.html As our forum support has a time delay due to the Time Zone difference, it appears as if this issue may be better addressed over the telephone. If this issue is urgent, I suggest contacting our Phone Support as they can provide you with immediate help. Please include your case ID, which is displayed in the subject line, so that we may more efficiently access your information. Windows Warranty Support: (425) 635-3311 Mon-Fri 5.am - 9.pm Pacific Standard Time Sat 5.am - 3.pm Pacific Standard Time Sun 9.am - 3.pm Pacific Standard Time Hope it helps. Tim Quan - MSFT

Hi, Tim. Thank you for your attention. The symptom is that: DirectX applications work properly when connecting from Windows XP/Vista to Windows Vista. But the issue occur when connecting from Windows XP/Vista to Windows XP. That is to say, it depends on the OS version of the connected PC. No matter which OS you connect via remote desktopfrom, when the OS of the connected PCis XP, it occurs; butif the OS of the connected PC is Vista, it is OK.

Hi Omnix,Did you find any more information about this? We are seeing something similar here with a video component that we have created. If Vista/XP connects to an XP computer, then we get various error codes related to DX and video which indicate that DX9 isn't available, which is fine. Where as if we connect to a Vista machine instead, everything goes through without any errors, but we still don't get any video.Cheers

Hi - I am having the same problem.... I have a direct x app I am building in c++.... Im using my laptop today to remote connect to my main build PC, and when I try to run my app remotely, it fails with the same error. I know the app works on my laptop when it's running local, so I don't understand why it wont work running it remotely. Both my laptop and PC are Windows XP. The default adapter returns no DISPLAY MODES when running from a remote computer so the entire app fails after that. Here's the bit of code I used to test this.Thanks for all assistance.- Mike D3DDISPLAYMODE mode;for (int adapterNum = 0; adapterNum < adapterCnt; adapterNum++) {int modeCnt = iDirect3D9->GetAdapterModeCount(adapterNum, preferedDisplayFmt);string str0 = "* Adapter Number ";str0.append(intToString(adapterNum + 1));str0.append(" - Mode Count = ");str0.append(intToString(modeCnt));AppLogs::printTrace(&str0); for (int modeNum = 0; modeNum < modeCnt; modeNum++) {HR(errCd, iDirect3D9->EnumAdapterModes(adapterNum, preferedDisplayFmt, modeNum, &mode));string str = "Mode ";str.append(intToString(modeNum + 1));str.append(" - width=");str.append(intToString(mode.Width));str.append(" height=");str.append(intToString(mode.Height));str.append(" format=");str.append(intToString(mode.Format));str.append(" refresh rate=");str.append(intToString(mode.RefreshRate));AppLogs::printTrace(&str);}}

Hi! I've heard some people say that they will start the DirectX app on the server side, before remote logging in, and then, when they log in with the client, the application will work fine. On my setup though, I can use DirectX no matter what OS I'm remote logging into, or from. Works pretty nice, because it lets me use DirectX apps even when I'm using rdp from like an iPad or something. You can have a look at what I did here, http://electronicsfanboy.com/index/technology/remote-desktop-with-direct3d-support-is-finally-possible-for-any-os/

at present the GPU is designed for a single task, but with the rise of compute servers using the GPU, AMD and NVIDIA are looking towards partitioning the GPU to better support virtual workloads i run a popular gaming site, so I am very literate with DirectX and its issues Windows MVP 2011-12, XP, Vista, 7 and 8. More people have climbed Everest than having 2 MVP's on the wall. Hardcore Games, Legendary is the only Way to Play Developer | Windows IT | Chess | Economics | Vegan Advocate | PC Reviews