VOGONS


First post, by kcajjones

User metadata
Rank Newbie
Rank
Newbie

I have UT2004 installed from GOG with the Creative X-fi patch installed so supporting EAX 5.0 via OpenAL. I output all my audio via HDMI from a GTX 1080 ti to my Onkyo TX-SR705 with a 5.1 speaker configuration.
With OpenAL Soft v1.23.1, I can't get UT2004 to output any sound at all with H/W 3D + EAX setting in game. I've followed a few different guides online suggesting to rename the soft_oa.dll file to OpenAL32.dll and place it in the UT2004/System folder but no joy - I get no sound at all. I've checked the OASoft info program and it states that the EAX5.0 effects should be emulated. Most of the guides online focus on HRTF and headphone output which I'm not interested in as I run 5.1 speakers.

Has anyone got this to work properly?

Reply 1 of 9, by DracoNihil

User metadata
Rank Oldbie
Rank
Oldbie

What does the log say?

Also what is this "Creative X-fi patch" I've never even heard of this patch. I had hardware mixed audio working just fine on Windows 7 Ultimate with a X-Fi Titanium HD (a system I nolonger have anymore) and I didn't need any kind of patch; I only needed the last version release of Creative's proprietary OpenAL library. On other soundcards including intergrated audio, OpenAL Soft has always worked fine for me when making UT2004 use it as the OpenAL provider rather than Creative's own OpenAL libraries.

“I am the dragon without a name…”
― Κυνικός Δράκων

Reply 2 of 9, by Joseph_Joestar

User metadata
Rank l33t++
Rank
l33t++
DracoNihil wrote on 2024-06-08, 06:09:

Also what is this "Creative X-fi patch" I've never even heard of this patch.

Unreal Tournament 2004 originally shipped with EAX 3.0. To promote their X-Fi cards, Creative later released a custom patch which adds EAX 5.0 support.

It improves positional audio, adds customized dynamic music (which sounds terrible IMO), introduces (crappy) new weapon sounds and adds some other stuff. I've shared some of my experiences with that patch in this thread.

PC#1: Pentium MMX 166 / Soyo SY-5BT / S3 Trio64V+ / Voodoo1 / YMF719 / AWE64 Gold / SC-155
PC#2: AthlonXP 2100+ / ECS K7VTA3 / Voodoo3 / Audigy2 / Vortex2
PC#3: Core 2 Duo E8600 / Foxconn P35AX-S / X800 / Audigy2 ZS
PC#4: i5-3570K / MSI Z77A-G43 / GTX 980Ti / X-Fi Titanium

Reply 3 of 9, by DracoNihil

User metadata
Rank Oldbie
Rank
Oldbie

Also since you're trying to use OpenAL Soft with UT2004 put a alsoft.conf text file in UT2004's System folder with this in it:

[general]
drivers = wasapi
channels = surround51
frequency = 48000
period_size = 1024
periods = 2
stereo-mode = speakers
stereo-encoding = basic
hrtf = off
resampler = linear
output-limiter = off

[wasapi]
spatial-api = false
allow-resampler = true

[eax]
enable = true

The WASAPI backend in OpenAL Soft doesn't seem to allow picking a device, so you need to make sure you set your default device properly in Windows' global settings.

“I am the dragon without a name…”
― Κυνικός Δράκων

Reply 4 of 9, by kcajjones

User metadata
Rank Newbie
Rank
Newbie

Thanks for the feedback.
Indeed I have installed the EAX 5.0 Creative patch and I'm running the 32bit version of UT2004.
I've tried adding the above config in the UT2004/System folder but get the same error.

The UT2004 log shows:
Log: ALAudio: AL_OUT_OF_MEMORY in Init (creating transient source)
Error: ALAudio: couldn't allocate transient source
Error: Audio initialization failed.

ALsoft log shows:
[ALSOFT] (WW) Querying error state on null context (implicitly 0xa004)
[ALSOFT] (II) Increasing allocated effect slots to 4
[ALSOFT] (WW) Error generated on context 0D3659D0, code 0xa005, "Exceeding 256 source limit (256 + 1)"

I have onboard sound but it's disabled in the BIOS as I just use HDMI output from the GTX 1080ti to my AVR.

I can upload the entire logs if required but that's the error messages I'm getting. No idea why the game seems to request more sources than is allowed in EAX mode. I've tried changing the sources limit from 256 but it always requests +1 so is over the limit.

Last edited by kcajjones on 2024-06-08, 10:15. Edited 1 time in total.

Reply 5 of 9, by DracoNihil

User metadata
Rank Oldbie
Rank
Oldbie
kcajjones wrote on 2024-06-08, 09:37:

Log: ALAudio: AL_OUT_OF_MEMORY in Init (creating transient source)

I have no idea why you'd be getting that message.

Only thing I can think of trying is enabling one of those "memory status lies" that hopefully are still part of Windows these days, but I don't remember how to work Application Compatibility Administrator in years.

Does anything happen if you run UT2004 under; say "Windows XP" for compatibility mode?

“I am the dragon without a name…”
― Κυνικός Δράκων

Reply 6 of 9, by kcajjones

User metadata
Rank Newbie
Rank
Newbie
DracoNihil wrote on 2024-06-08, 09:42:

I have no idea why you'd be getting that message.

Only thing I can think of trying is enabling one of those "memory status lies" that hopefully are still part of Windows these days, but I don't remember how to work Application Compatibility Administrator in years.

Does anything happen if you run UT2004 under; say "Windows XP" for compatibility mode?

No change for Windows XP compatibility modes sadly. I just edited my post to include the error from the ALsoft log.

*EDIT*
Just managed to fix the issue. Increasing the sound sources from 256 to 512 and sound is restored!

Reply 7 of 9, by DracoNihil

User metadata
Rank Oldbie
Rank
Oldbie
kcajjones wrote on 2024-06-08, 10:17:

Just managed to fix the issue. Increasing the sound sources from 256 to 512 and sound is restored!

I'm only even more confused why that fixed the problem.

“I am the dragon without a name…”
― Κυνικός Δράκων

Reply 8 of 9, by kcajjones

User metadata
Rank Newbie
Rank
Newbie
DracoNihil wrote on 2024-06-09, 10:34:

I'm only even more confused why that fixed the problem.

Yes, as far as I know the X-fi processor could do a maximum of 128 sound sounds. I've posted the issue on the OpenALsoft github.