Opened 11 years ago

Closed 11 years ago

#1766 closed defect (fixed)

[PATCH] ERROR: OpenAL error: Invalid Value; called from InitOpenAL (line 154)

Reported by: Jonathan Waller Owned by: stwf
Priority: Must Have Milestone: Alpha 13
Component: Core engine Keywords:
Cc: sound Patch:

Description

See #1737, the cascading errors caused by this one have been fixed but this error remains. Still easily reproducible with the combat demo on my machine (linux).

Attachments (1)

soundManagerEntity.patch (24.8 KB ) - added by stwf 11 years ago.
first draft of new SoundManager code

Download all attachments as: .zip

Change History (5)

comment:1 by stwf, 11 years ago

Status: newassigned

comment:2 by stwf, 11 years ago

Summary: ERROR: OpenAL error: Invalid Value; called from InitOpenAL (line 154)[PATCH] ERROR: OpenAL error: Invalid Value; called from InitOpenAL (line 154)

by stwf, 11 years ago

Attachment: soundManagerEntity.patch added

first draft of new SoundManager code

comment:3 by stwf, 11 years ago

OK, I believe this problem is fixed. The solution is in this patch. Hopefully someone can check this out during the next week, and we can roll it in when I get back.

This version does contain some logging to note when the sound manager goes into distress mode. That means it is expected to play more sounds simultaneously than it can.

So the logging will tell you when it goes into and comes out of distress mode. O n MacOS there seems to be an OpenAL bug that sometimes returns an unknown internal error in distressed situations. This will be counted and displayed in the logs. I'm interested to see if it can be reproduced on other platforms. I haven't had any luck (which is good).

comment:4 by Jonathan Waller, 11 years ago

Resolution: fixed
Status: assignedclosed

Tested this with r12309. Distress mode is entered but no errors occur.

Note: See TracTickets for help on using tickets.