Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
208 user(s) are online (110 user(s) are browsing Forums)

Members: 1
Guests: 207

MartinW, more...

Headlines

 
  Register To Post  

OpenAL 1.20 Clib2
Not too shy to talk
Not too shy to talk


See User information
@all

I am trying to solve that OpenAL1.18 crash after quitting the VanillaConquer.

I have succesfully compiled openal 1.20 for clib2 (salas00 port - https://github.com/salass00/openal_lib) with SDL2, AHI, Wave and null as backends.

I can also link the library with my VanillaConquer port.

However when I try the Vanilla Conquer exe., VanillaConquer crashes when opening alcdevice ?

AL lib: (II) Initializing library v1.20.1-unknown UNKNOWN
AL lib: (II) Supported backends: sdl2, ahi, null, wave
AL lib: (II) Loading config /etc/openal/alsoft.conf...

Is there somemuch difference between OpenAL 1.18 and 1.20 AmigaOS4 ports ?

Is there a OpenAL 1.22 port that I can compile for clib2 ?

Sinan - AmigaOS4 Beta-Tester
- AmigaOne X5000
- AmigaOne A1222
- Sam460ex
Go to top
Re: OpenAL 1.20 Clib2
Just can't stay away
Just can't stay away


See User information
@SinanSam460

and with v1.18 (recompiled using beta/new clib2) no problems (with the same "plugins")?

Go to top
Re: OpenAL 1.20 Clib2
Not too shy to talk
Not too shy to talk


See User information
@jabirulo

There is no SDL2 backend for 1.18 but, yes no problem with 1.18 while launching and running the game. (1.18 can't cleanup ahi device after exiting the game)

However 1.20 has problems while launching the game..

Sinan - AmigaOS4 Beta-Tester
- AmigaOne X5000
- AmigaOne A1222
- Sam460ex
Go to top
Re: OpenAL 1.20 Clib2
Just can't stay away
Just can't stay away


See User information
@SinanSam460

Don't bother with version 1.20.1. It isn't working which is why there are no releases so far of this version and the main makefile is still set to build version 1.18.2.

As for the cleanup problems there is very little that can be done if programs refuse to clean up after themselves. Theoretically it might be possible to do something with an atexit or destructor function that cleans up the audio driver backend if the program hasn't done so yet, but this could also cause problems for correctly written programs so it isn't worth it IMO.

Go to top

  Register To Post

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project