Boris I. Bendovsky
Boris I. Bendovsky
Even if I'll decide to add such compatibility it's not gonna happen in the near future. I have to close existing issues. Supporting or developing other projects adds delay too.
> Disabling chorus probably breaks EAX support, since EAX has chorus running by default on the second effect slot (not sure why since it couldn't be controlled in EAX1/2/3, although...
This could be my oversight. Initial value of `Room` parameter in Host OpenAL for EAX2 is `-10000` (muted reverb).
> Fixed that with commit [964a11e](https://github.com/kcat/openal-soft/commit/964a11ef629fa3a89e827516a47949c858ce864c). Sorry, I don't get it how this commit fixes the problem. EAX properties already initialized with proper default values (`eax_ = EAXREVERB_PRESETS[EAX_ENVIRONMENT_GENERIC];`). Why to...
> I think the issue is what I mentioned up before, that either sources shouldn't default to having any active fx slots, or the active fx slots (if not all...
> This confuses me since all the EAX versions are accessing the same underlying functionality. As it is, an app can create and use sources before making any EAX calls,...
> For instance, if you set a non-default EAX2 source property (e.g. `EAXSOURCE_DIRECT`), then a different non-default EAX3 source property (e.g. `EAXSOURCE_ROLLOFFFACTOR`), does the changed EAX2 property audibly revert back,...
> Hello there :) Is there some kind of controller support planned? Something like ecwolf? > > For now i have to use xpadder to get through the menus and...
> I'm curious if there's any updates for this. OpenAL Soft has native EAX API support on Windows now, and DSOAL has been changed to use it. Is the behavior...