I have Intel HD 3000 graphics which are not compatible with DirectX 12. I am having issues in some games so I thought maybe I could install DirectX 11 on Windows 10 which is compatible with my GPU. Please help me if you know how to solve this issue/
No, you don't have to and you shouldn't, too.
DirectX 11 and DirectX 12 are two different APIs, they are not compatible with each other. What DirectX version that the game will be using has been decided when the game was made. It means you can't "upgrade" or "downgrade" DirectX by installing different drivers or by any other configurations.
Related
I was trying to start to learn programming in DirectX 11, but I'm still using Windows 7 OS. My IDE is Visual Studio Community 2019 and I've tried to create a DirectX 11 project, but I got the error message saying that I need to upgrade my system to Windows 10 to be able to use this feature. I've downloaded Microsoft Development Kit, SDK and another extensions VS offered to me thinking it would actually work, but it didnt. I'm sorry if this seems a silly question, but I'm new on this and I would find it a great help if someone is able to tell me what I'm doing wrong or if there is really not other way to program in DirectX 11 on windows 7.
As noted by Simon in the comments, the "DirectX" templates built-in to VS 2019 are for Universal Windows Platform (UWP) apps only which requires Windows 10.
I maintain a number of similar templates for UWP and Win32 for DirectX 11 & DirectX 12 on GitHub.
Windows 7 supports DirectX 11.0.
Windows 7 can support DirectX 11.1 "software features" but not "hardware features" with KB2670838. Basically this means you won't get D3D_FEATURE_LEVEL_11_1. See Microsoft Docs. Most any Windows 7 system that's updated from Windows Update should have it.
My Win32 templates assume you have DirectX 11.1 these days. For the details on handling DirectX 11.0, see this blog post.
VS 2019 can support targeting Windows 7 Service Pack 1 for Win32 desktop development. Officially Windows 7 RTM is not supported.
VS 2019 comes with the Windows 10 SDK which includes everything you need for basic Direct3D 11 system headers and libraries. You do not need the legacy DirectX SDK at all. That said, if your learning materials still reference legacy stuff like D3DX11, you can install it but beware there are some special setup details. See Microsoft Docs.
For XAudio2 on Windows 7 SP1, use the XAudio2Redist instead of the legacy DirectX SDK. For XInput, you can use the basic XInput 9.1.0 which is built-in to Windows 7.
You may want to take a look at the DirectX Tool Kit tutorials.
Environment: Windows 10 (fresh install), using Monogame 3.6 (same goes for 3.5 for this matter) on DirectX projects.
Problem: I can’t hear any sound effect unless I reinstall DirectX.
Before reinstalling DirectX, there is no exception or status information I could use to trace why the sound is not audible. After reinstalling, it just works. Same code, even same binary.
I don’t want my users to have to reinstall DX. This will be awkward as Win10 comes with DX pre-installed.
So I wonder if someone knows which additional DX libraries I may include in project folder so that the sound effects are audible without reinstalling DX?
It's important to understand that you cannot "Install DirectX" on Windows 10 or any version of Windows back to Windows XP Service Pack 2. The DirectX End-User Runtime package (a.k.a DXSETUP) doesn't actually install Direct3D, DirectPlay, DirectSound, etc. It doesn't even include the CABs needed to install DirectX on older versions of Windows.
Not So Direct Setup
The version of "DirectX" installed is only ever updated via Windows Update, installing a new version of Windows, or some kind of Service Pack. Windows 10 includes all supported components of DirectX 9.0c, DirectX 10.x, DirectX 11.x, and DirectX 12.0 as part of the OS.
Direct3D 11 Deployment for Game Developers
What the DirectX End-User Runtime package does install is the various legacy side-by-side helper components: D3DX9, D3DX10, D3DX12, XAUDIO2.7 or earlier, XINPUT 1.3 or earlier, XACTENGINE, and the legacy Managed DirectX 1.1 assemblies. That's it. Furthermore, it installs about 100 MB of these things including every version that has ever shipped for both x86 and x64, which means your game is never going to use most of them. Likely Monogame is set up to use XAudio 2.7 which is the last version of XAudio to support Windows 7. As such, it needs just a handful of CABs from DXSETUP.
KB179113: How to install the latest version of DirectX
XAudio2 and Windows 8
Finally, the DXSETUP files that shipped in the end-of-life DirectX SDK (June 2010) are actually not the latest version of the DirectX End-User Runtime. I fixed a number of bugs in an online only April 2011 refresh.
DXSETUP Update
Is it possible to use Delphi XE5 or RAD Studio XE5 to create apps for Windows 8 RT (ARM based tablets) and Windows Phone 8, using the same code (Firemonkey) as for Android and iOS?
I searched Embarcadero's website on windows development but it goes a long way to avoid mentioning Windows 8 RT and Windows Phone 8. It states that
Your apps will run on Windows desktops and x86 based tablets with Intel and Intel Atom hardware such as Microsoft Surface Professional, Slate tablets from HP, Asus and others, as well as AMD processor based tablets from Acer, Samsung and more.
Does this mean that Windows 8 RT and Windows Phone 8 are not supported by Delphi/RAD Studio XE5?
Delphi XE5 cannot produce apps that run on WinRT or Win Phone 8.
Work is being done on Windows ARM/RT, Linux Server, TBD.
Take a look Embarcadero RAD Studio Roadmap
http://edn.embarcadero.com/article/42544
To confirm David's accepted answer, I just received a response from Embarcadero support:
Yes, you are correct we DO NOT support Win8 RT or WinPhone8 with Firemonkey. We have not seen a huge demand for these platforms, if there is an increase in demand they might be support, but at the moment we are not supporting them sorry.
So it does not sound like they have any plans to support those platforms in the near future.
I am planning to upgrade my OS to Win 7 (32bit or 64bit). I would like to know whether we can install and run Delphi 7 on Win 7 successfully or not.Share your thoughts on installation of 3rd party components as well.
This would help me to take decision regarding OS up-gradation.
I am using Delphi 7.0 on Windows 7, 64 bit, without issues. I have previously installed it on Windows 7, 32 bit and used it without issues as well.
Windows will bother you about an incompatibility when you run the installer. You should probably ensure that anybody using Delphi 7 will have full write access to the folders in Program Files that need to be writeable by Delphi 7.
I have my copy installed in Program Files, and I only use it from an account with admin priveleges, so I can write/modify files inside the Delphi installed folders, without problems.
Some people think it's better to install to C:\Delphi7.
Nobody can know for sure about your components, but you should just try them.
I'm using Windows 7 64 bit. When installing delphi 7 it prompt for compatibility issue. Just accept it, click run. Then delphi 7 installed succesfully without problem. I'm installed it on X:/app/Delphi7. 3rd party component added without problem, example i'm adding AlphaSkin component without problem.
I'm working on deciding between Managed DirectX (through MS API Codepack), SlimDX library (managed wrapper for DirectX), XNA (managed wrapper++ for Directx9 only), or unmanaged Directx (20%+ extra development time).
So, the MS API Codepack interests me, because it has support for DirectX. However, I get a feeling that they might not support future versions with the Codepack. My thinking is that they just wanted something to support the version of DirectX that ships with Windows 7.
Is MSI API Code Pack DirectX functionality going to be updated as DirectX progresses?
Thanks
There is no way to know this.
However, I will say, I've been using SlimDX for a while now, and it's very, very well thought out. The advantage there vs. the other options I've tried, include:
Support for DirectX 9, 9Ex, 10, and 11
Clean API - Very easy to port from DirectX samples, but still feels more like .NET
32 and 64 bit native versions
Kept very up to date with DX SDK releases (usually within a couple of weeks of a new SDK, there's a new SlimDX version)
The Windows API code pack has a nice wrapper included, but is problematic for me since it's DX10+ only, so no XP support.