![]() ![]() NET 2.0 compatible runtime (2.0, 3.0, 3.5) continue to use existing deployment mechanisms See 3.4 Install Windows Resources Properly. As always, if you use DirectSetup for your title, trim your title down to the minimum required set of CABs. While Windows 8 has an application compatibility behavior to resolve this issue automatically (which requires network access), we recommend that games that continue to deploy DirectSetup update to the DirectX SDK (June 2010) refreshed version of the REDIST files. But, this issue does not apply to any version of. NET 4.5 by default, and fresh Windows XP computers with the. This issue applies to both Windows 8, which comes with. NET 4.0 installed due to the deployment handling of the legacy Managed DirectX 1.1 assemblies. The DirectX End-User Redistribution package runs successfully on Windows 8, as it does on Windows 7, to deploy D3DX9, D3DX10, D3DX11, XINPUT 1.3, XAUDIO 2.7, XACTEngine, and so onīut, a known issue exists with DirectSetup on systems with only. Windows 8 passes the current minimum bar tests that we recommend for game deployment. Games that run on Windows 7 can and should run correctly on Windows 8 x86 and 圆4 platforms. Only a limited set of desktop Win32 apps are supported on Windows RT See 1.4 Support the Xbox 360 Common Controller for Windows. All versions of Windows can also use the existing DirectX SDK version XINPUT 1.3, which requires DirectSetup to deploy. All versions of Windows can use XINPUT 9.1.0 for simplified common controllers, but there is no redistribution package with XINPUT 9.1.0. ![]() Both Windows Store apps and desktop Win32 apps can use XINPUT 1.4. There are now three choices for using the XINPUT API depending on your requirements See 1.2 Support Family Safety / Parental Controls. We recommend that you run the Windows SDK version of GDFMAKER on the released version of Windows 8 to ensure that it can populate all currently supported rating systems. Registration with the Game Explorer APIs continues to be the mechanism for registering your game with Windows Parental Controls To download the Windows 8 SDK, see Downloads for developing desktop apps. Continue to test your Games Explorer registration by using Windows 7, and verify that the new Windows UI tile shows up when you install it on Windows 8 (see 1.1 Games Explorer Integration). You also use the existing mechanisms for deploying the metadata. You still use the Games Definition File Maker tool (GDFMAKER.EXE), which is now available in the Windows Software Development Kit (SDK), to author the metadata. Here is a summary of the key differences when applying these technical requirements and best practices to Windows 8.Īll games that you register with the Games Explorer are surfaced as tiles in new Windows UI, but much of the metadata that is associated with the title is no longer visible. Guidelines for Game Middleware Products.Xbox 360 Common Controller for Windows Terminology.4.3 Support Windows Error Reporting and File Version Information.4.2 Eliminate Application Verifier Failures.3.2 Support User Account Control for Installation.2.1 Follow User Account Control Guidelines.1.6 Support Launch from Windows Media Center.1.5 Support Multiple Aspect Ratios and Resolutions.1.4 Support the Xbox 360 Common Controller for Windows.1.2 Support Family Safety / Parental Controls.These best practices also generally apply to desktop Win32 games on Windows 8. We wrote these technical requirements and best practices primarily to cover Windows Vista and Windows 7, as well as the legacy Windows XP operating system. This article provides technical requirements and best practices for games that run on Windows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |