Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sample programs fail to initialize ADLX #1

Closed
tylercamp opened this issue Dec 27, 2022 · 1 comment
Closed

Sample programs fail to initialize ADLX #1

tylercamp opened this issue Dec 27, 2022 · 1 comment

Comments

@tylercamp
Copy link

tylercamp commented Dec 27, 2022

Environment:

  • Windows 10 (22H2/19045.2364) on a Ryzen 9 3950X in a KVM virtual machine with GPU passthrough
  • RX 6700XT with AMD Adrenalin 22.11.2
  • Developing over a Remote Desktop connection (directly attaching peripherals is complicated with my setup)
  • MSI Afterburner and AMD Adrenaline operate just fine over Remote Desktop (am able to enumerate GPU and apply OC settings)
  • When I had a display attached, Call of Duty MW2 performed without issue
  • I'm able to build and run the ADL samples without issue

After cloning (and no other setup actions), I've built and attempted to run all sample programs under the Samples/CPP directory using the provided build instructions. There were no issues building. (Tried latest version of VS 2019 and 2022.)

All provided sample applications fail with the message "ADLX initialization failed" (or some variation of this).

The only exceptions are:

  • DisplaySettingsEvent - "Destroy ADLX result: 0"
  • GPUService - Closes immediately, no output
  • DesktopsEvent, all Sync* samples - Same error message, but closes immediately
  • WorkWithADL - Shows "ADL initialized successfully", but ADLX initialization fails

There are no relevant messages in Windows Event Viewer.

I'm not sure if this is user error since there are no mentions of system or third-party requirements in the documentation. There are occasional mentions that the ADLX SDK must be "installed", but this is not expanded upon.

Please let me know if there's somewhere I might collect more useful diagnostic information.

@tylercamp
Copy link
Author

Thank you PeterTh for submitting issue #4 , as I didn't think the DLL had to be downloaded manually. Kudos to you for finding it at all, that fixes this "issue"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant