aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Robinson <[email protected]>2014-10-13 10:48:54 -0700
committerChris Robinson <[email protected]>2014-10-13 10:48:54 -0700
commit3585021a18e6a7ede1162b68c7a0cf6e6a9f45fd (patch)
tree9954085d44a57b12354d48233fe56c82cf5d84ff
parent87dcf65013d363989c989a9f749bb31a126c28da (diff)
Minor clarification for __ALSOFT_SUSPEND_CONTEXT
-rw-r--r--env-vars.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/env-vars.txt b/env-vars.txt
index 487067d5..b2268643 100644
--- a/env-vars.txt
+++ b/env-vars.txt
@@ -74,8 +74,8 @@ __ALSOFT_SUSPEND_CONTEXT
Due to the OpenAL spec not being very clear about them, behavior of the
alcSuspendContext and alcProcessContext methods has varied, and because of
that, previous versions of OpenAL Soft had them no-op. Creative's hardware
-drivers and the Rapture3D driver, however, use these methods to batch changes
-and protect against partial updates, which some applications make use of. In an
+drivers and the Rapture3D driver, however, use these methods to batch changes,
+which some applications make use of to protect against partial updates. In an
attempt to standardize on that behavior, OpenAL Soft has changed those methods
accordingly. Setting this to "ignore" restores the previous no-op behavior for
applications that interact poorly with the new behavior.