The DirectX runtime is not available on this machine

[johnsonx42]

I'm wondering if the issue has something to do with the VC++ runtime? All of us in the testing group had already installed the later VC++ before sub included the needed .dll files with NPVR, theoretically eliminating the need for users to install it separately. What if something in that complete VC++ runtime has some interaction with the DX9 runtime? Everyone suddenly has this problem only after upgrading to 3.1.1, and Agerdin has backrev'd to 2.6.2 and the DX9 problem has gone away again... the only difference I can think of is that 2.6.2 is using the older VC++ and .NET runtimes.

Could we maybe get just one user afflicted by this to try the full VC++ runtime? If that proves it, then maybe sub can figure out which additional VC++ file(s) is needed, and can post it as a patch and get it rolled in to the next installer.

[sub]

Yep, it could be something like that.

[johnsonx42]

Here's the full VC++ runtime that I know I installed and I'm pretty sure everyone in the testing group installed early on: http://www.microsoft.com/en-us/download/...x?id=30679

[agerdin]

Could we maybe get just one user afflicted by this to try the full VC++ runtime? If that proves it, then maybe sub can figure out which additional VC++ file(s) is needed, and can post it as a patch and get it rolled in to the next installer.

Thanks for trying johnsonx42 but to no avail.

Uninstalled 2.6.2 again
Installed 3.1.1 (warning appear)
Installed the full VC++ runtime (warning still there)
Rebooted (warning still there)
Applied Subs fix from http://forums.nextpvr.com/showthread.php...s-expected which made the menu to work but still the DirectX warning.

\\Agerdin

[bgowland]

Is DirectX 9.0c specifically required? The only reason I ask is DirectX is part of the actual Windows OS installation starting with Vista I believe. The dxdiag output from agerdin shows v11 which would have been installed with W7. Vista would show v10 and Win 8 v11.1 I think.

[Zeb]

Actually Vista with SP2 also shows DirectX 11, but the 9.0c end-user runtimes are something else sub uses for the UI that's faster than software rendering. I suspect that johnsonx42 is on the right track.

[Edit] Or maybe not, judging by agerdin's last post. Windows 8 users have reported DirectX problems in the past, but the novel thing about this thread is all the Win7x64 users posting.

[johnsonx42]

no idea then. I can come up with no explanation for this.

[bgowland]

Actually Vista with SP2 also shows DirectX 11,

The versions I mentioned are those installed with the original OS versions as I understand it (might be wrong). Service Packs obviously update various components.

but the 9.0c end-user runtimes are something else sub uses for the UI that's faster than software rendering.

Yep I get that but my question was whether or not 9.0c is a specific requirement or if v10, 11, 11.1 should be backward compatible with v9.0c functionality. Based on the fact v2.6.2 works for agerdin I'd guess "yes". Just trying to eliminate possible causes.

Cheers,
Brian

[mvallevand]

No sub specifically needs DirectX9 run time.

The irony of this is my 8.1 Preview VM doesn't give the error for the first time.

Martin

[johnsonx42]

... but my question was whether or not 9.0c is a specific requirement or if v10, 11, 11.1 should be backward compatible with v9.0c functionality. Based on the fact v2.6.2 works for agerdin I'd guess "yes". Just trying to eliminate possible causes.

The DirectX 9 runtime installs additional components not normally included, but needed by NPVR for UI rendering. They're no more present in DX 10, 11, or 11.1 than they are in DX 9, until you install that runtime.

I run 32-bit Windows 7 on my desktop and HTPC, but my son has 64-bit on his computer. When he goes to work in a couple of hours, I'll try installing NPVR on his system and see what happens.