- 30 Jul, 2022 40 commits
-
-
Sebastian Lackner authored
Based on a patch by Mark Harmstone.
-
Sebastian Lackner authored
The previous version had several problems (see wine-staging bug 195): * IDirectSoundBufferImpl_Duplicate doesn't initialize EAX properties * Various race-conditions between initializing EAX and setting buffer properties * Missing locks while iterating through the list of sound buffers To fix problems 2 and 3 it might seem useful to introduce additional locking, but testing reveals that it slows down the mixer thread too much. Some applications use a huge amount of buffers, and its a waste of time to update them all immediately. Thats why this patch adds a 'reverb_update' variable, the mixer thread will update it later when necessary (-> much faster). Moreover, to avoid unnecessary locking, we initialize the EAX-specific properties always (for both the device and the buffers).
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Mark Harmstone authored
-
Sebastian Lackner authored
Based on a patch by Mark Harmstone.
-
Alexander E. Patrakov authored
-
Alistair Leslie-Hughes authored
-
Alistair Leslie-Hughes authored
-
Jetro Jormalainen authored
-
Jetro Jormalainen authored
-
Andrew D'Addesio authored
-
Christian Costa authored
-
Michael Müller authored
-
Michael Müller authored
-
Michael Müller authored
-
Michael Müller authored
-
Sebastian Lackner authored
-
Christian Costa authored
This patch fixes last problem of bug 32572.
-
Christian Costa authored
d3dx9_36: Filter out D3DCompile warning messages that are not present with D3DCompileShader. (try 4) This patch fixes vertex processing issue of bug 33770. The problem comes from the fact that even if the call succeeds, the game interprets a non null error_messages pointer as an error. By calling D3DCompile we use a newer version of the compiler which is more strict and generates the following warning. - warning X3206: 'dot': implicit truncation of vector type - warning X3206: implicit truncation of vector type - warning X3206: 'mul': implicit truncation of vector type D3DCompileShader does not generate such warnings. These is confirmed in the DX SDK release note: New Warning X3206: Implicit Truncation of Vector Type Beginning in the August 2009 release of the DirectX SDK, the compiler will warn when an implicit truncation of a vector type occurs. The warnings cannot be disable so this patch filters out these strings in D3DCompileShader and reset the error messages pointer if the resulting buffer is empty. Try 2: - only filter out lines containing "X3206:" in case d3dcompiler_43 has localization Try 3: - use move in place instead of copying the buffer Try 4: - filter simplification by Sebastian and remove 'mul' testing left-out in search string
-
Christian Costa authored
-
Christian Costa authored
-
Alistair Leslie-Hughes authored
Signed-off-by: Alistair Leslie-Hughes <leslie_alistair@hotmail.com>
-
Christian Costa authored
-
Christian Costa authored
-
Sebastian Lackner authored
-
Christian Costa authored
Changes in v2 (by Christian Costa): * More generic code for D3DXDisassembleShader.
-