Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port/Finish OpenAL-soft support #6

Open
ensiform opened this issue May 28, 2017 · 2 comments
Open

Port/Finish OpenAL-soft support #6

ensiform opened this issue May 28, 2017 · 2 comments

Comments

@ensiform
Copy link
Member

Currently I have left it out because of lack of OAL-soft libs in the repo.

@ghost
Copy link

ghost commented Jan 13, 2021

Hi Ensiform!

Well, I know this isn't a forum, so please excuse me to 'hijack' this issue ticket to ask a few questions.
Probably you remember that we talked on Discord about OpenAL-soft support. For good reason I quit using Discord, so I will talk to you here.
My plan is to port my own project(s) to your ETe code. I managed to make use of all the 'efx' effects OpenAL-soft currently supports, my maps are even using those effects. This means it would be nice to have OpenAL-soft support in ETe.
Here are the questions, before I'll move to ETe:


  1. Is OpenAL-Soft support still a task you consider for ETe? On Q3e you made a feature request, for ETe you set the priority to 'Low'?

  1. Iirc on Discord you once said that OpenAL is badly implemented. Well I inspected a few engines that supports OpenAL and I don't know what you mean by 'badly implemented', I'm no coding guru but I can't see so much differences between various implementions, so what are the biggest issues you have with OpenAL-soft?

  1. We also talked about how to access OpenAL's environmental effects, currently I do this via CONTENTS mask. Can you please point out your thoughts how to access map dependant environmental effects for ETe?

Once again, I'm sorry if my comment looks a bit out-of-place and please don't curse me if I quoted you wrong but I really don't remember exactly what you said on Discord.
Thanks in advance!

@ensiform
Copy link
Member Author

ensiform commented Jan 14, 2021

Most implementations I have seen which are based on ioquake3/idtech3 code in general have poor performance, don't handle most features, and generally "suck" compared to standard DMA or even SDL DMA backend.

I put the issue on Quake3e because I was hoping to see Cyrax add it for Quake3e first before merging here as I lack the skill to really see what I want to have in it.

I have no idea how contents would be successful, as efx to fully take advantage requires tracing and such. See: quake2xp and some of this stuff isn't exposed to mod API.

Not sure why you quit discord instead of just leaving servers you no longer wish to partake in but okay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant