Quote: "Anyone without the June 2010 DirectX runtime libraries installed, which includes all vanilla Windows 8+ installs, will receive the xaudio error on AppGameKit and any apps compiled through it. TGC is using XAudio 2.7 to retain XP support, but that version is no longer shipped with the default Windows 8 DirectX packages."
Hi, Windows 7 user here, who, with June 2010 runtimes installed, is still having these problems, sporadically.
I would really, really love a coherent and reliable solution to this problem. I've wiped runtimes and SDKs and related programs and then reinstalled them about ten times now, trying to get and keep this magical June 2010 runtime library in its proper place, and it's exhausting. It takes hours. And no matter which way I install which things, it's only a matter of hours before I get an XAudio error again.
And ok, I get that this is 'my fault' in some sense, in that as a developer I'm responsible for making sure I have all the prerequisites installed and working properly. But at the same time, I'm not a developer, and I bought AGK2 because I thought it would let me create some apps despite not knowing a whole lot about the inner workings of computers and devices.
I guess nothing I'm doing actually uses anything completely new to AppGameKit v2, so I could just forget the $67 I paid for v2 and forget the awesome new IDE and go back to AppGameKit v1. But the fact that that solves the problem leaves me all the more confused: if AppGameKit v1 didn't use XAudio 2.7, and worked just fine, why does AppGameKit v2 use XAudio 2.7?
Quote: "This is very simple to fix on TGC's end for the AppGameKit installer and anyone else who wishes to create installer packages for AGK-based desktop apps. I did this recently with a desktop app I deployed. You simply have to include the minimum required DirectX files from the DirectX SDK [DSETUP.dll, dsetup32.dll, DXSETUP.exe, dxupdate.cab, Jun2010_XAUDIO_x86.cab] and allow the installer to silently install them alongside the app. This only adds about 2.5MB overhead to your application and adheres to Microsoft's redistributable guidelines; then users will have no trouble running the app."
Your "very simple" is my "slightly beyond comprehension" -- can you explain how we can go about doing this? Maybe I can solve my own problem.
It's mean time. *averages*