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

The current openal32.dll appears to have problems with new hardware and Windows 10 #1247

Closed
GatoRat opened this issue Jun 22, 2017 · 0 comments · Fixed by #1260
Closed

The current openal32.dll appears to have problems with new hardware and Windows 10 #1247

GatoRat opened this issue Jun 22, 2017 · 0 comments · Fixed by #1260

Comments

@GatoRat
Copy link

GatoRat commented Jun 22, 2017

The current openal32.dll appears to have problems with new hardware and Windows 10, at least in 64-bit. It will throw an invalid access exception after about three minutes. We observed this on a Surface Tablet running Windows 10 Creators Update. In the forums, there is a very similar report on a Dell XPS (https://en.sfml-dev.org/forums/index.php?topic=22000.0.)

I determined that SFML is using OpenAl 1.15.1, which is from December 2012. I took the release binary for 1.18.0, renamed it to openal32.dll, replaced the earlier version and the software has been running without issue for almost 18 hours.

I suggest replacing the opeal32.dll with the latest version.

@eXpl0it3r eXpl0it3r added this to the 2.5 milestone Aug 1, 2017
@eXpl0it3r eXpl0it3r self-assigned this Aug 1, 2017
@eXpl0it3r eXpl0it3r added this to Discussion in SFML 2.5.0 Aug 2, 2017
@eXpl0it3r eXpl0it3r moved this from Discussion to Review & Testing in SFML 2.5.0 Aug 23, 2017
@eXpl0it3r eXpl0it3r moved this from Review & Testing to Ready in SFML 2.5.0 Aug 23, 2017
@eXpl0it3r eXpl0it3r moved this from Ready to Merged / Superseded in SFML 2.5.0 Aug 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
SFML 2.5.0
  
Merged / Superseded
Development

Successfully merging a pull request may close this issue.

2 participants