1
General / Re: Writing to SFML Console
« on: June 14, 2017, 10:19:14 am »
Ok must be a VS setting somewhere, thanks.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
General / Writing to SFML Console
« on: June 14, 2017, 10:15:06 am »
Hi,
I want to know if the SFML console can/should be used to output text to.
There are lots of threads about hiding it but i'd actually like to throw in some debug stuff if that's appropriate.
std::cout doesn't seem do anything.
I want to know if the SFML console can/should be used to output text to.
There are lots of threads about hiding it but i'd actually like to throw in some debug stuff if that's appropriate.
std::cout doesn't seem do anything.
3
Audio / Re: Unhandled Exception Openal32.dll
« on: June 08, 2017, 12:38:05 am »
@melcx Thanks!
I also just went to http://kcat.strangesoft.net/openal.html and grabbed the openal files from their bin directory, renamed them, used them instead of the openal32.dll files from the SFML source and it's working fine.
Made my day.
I also just went to http://kcat.strangesoft.net/openal.html and grabbed the openal files from their bin directory, renamed them, used them instead of the openal32.dll files from the SFML source and it's working fine.
Made my day.
4
Audio / Re: Unhandled Exception Openal32.dll
« on: June 07, 2017, 11:35:59 am »
I have the same issue as this. It occurs on my Win10 Dell XPS 9560 (All drivers up to date @ time of post).
When I run the same game on another Win10 Desktop my wife owns the issue does not occur.
This seems to indicate the issue is with a driver/audio card root cause and/or how the underlying openal code interfaces with it.
To cover a few things I've done on my XPS (still get a console warning and crash with all the following cases):
1. Static and Dynamic setups tested
2. X86 and X64 builds tested
3. sf::Music objects created and used in the same class(different functions)
3. sf::Music objects created and used in the same code block
4. Filename and SoundBuffer patterns used
The issue is best identified by the console output warning at runtime:
AL lib: (EE) MMDevApiMsgProc: Unexpected message: 49403
This warning occurs when a sf::Music object is created. The object can be used as expected (played, stopped etc.) until the crash occurs (3-5mins).
I've not yet used sf::Sound but will update if I get the same issues when I do.
When I run the same game on another Win10 Desktop my wife owns the issue does not occur.
This seems to indicate the issue is with a driver/audio card root cause and/or how the underlying openal code interfaces with it.
To cover a few things I've done on my XPS (still get a console warning and crash with all the following cases):
1. Static and Dynamic setups tested
2. X86 and X64 builds tested
3. sf::Music objects created and used in the same class(different functions)
3. sf::Music objects created and used in the same code block
4. Filename and SoundBuffer patterns used
The issue is best identified by the console output warning at runtime:
AL lib: (EE) MMDevApiMsgProc: Unexpected message: 49403
This warning occurs when a sf::Music object is created. The object can be used as expected (played, stopped etc.) until the crash occurs (3-5mins).
I've not yet used sf::Sound but will update if I get the same issues when I do.
Pages: [1]