We were hacked. Several times over the past two weeks, in fact.
While all passwords are encrypted and salted, it's recommended that you change your password here when you can.
Anybody tried the new X-Fi drivers with an Audigy?
Re: Anybody tried the new X-Fi drivers with an Audigy?
Yep, same process as if you were replacing BF2OpenAL.dll w/OpenAL32.dll.
Also, this is interesting (from sound.con in mod\BF2\Settings directory):
rem ** Number of MB we require from the OpenAL provider. Some native drivers
rem ** can't always give us that (Creative).
sound.setProperty required-buffer-size 90
I don't know if it's still valid. Only a couple of the files in the Settings directory and subdirectories are actually used by the game. The rest is just old obsolete stuff I guess.
Re: Anybody tried the new X-Fi drivers with an Audigy?
ct_oal.dll is only included in the ZS beta driver release (hence the release note about improving OpenAL performance) and newer.
However, after more testing, I don't think you should replace BF2OpenAL.dll with it. It is loaded from the system32 directory automatically by BF2.exe if you select hardware in the audio options. It did seem to work but I also got some crashes after a while that may or may not be related (no assert in dump file to check). So I believe you should replace BF2OpenAL.dll w/the OpenAL32.dll installed by OpenALwEAX.exe.
Also, there is something strange I noticed -- depending on which version of OpenALwEAX.exe you run, it will sometimes replace ct_oal.dll in the system32 directory w/a copy of OpenAL32.dll, just renamed to ct_oal.dll. I'm guessin earlier versions of OpenALwEAX.exe do this b/c they expect older driver releases that did not include a native ct_oal.dll or something.
I installed the 5.12.1.1161 drivers from StationDrivers and first ran the OpenALwEAX.exe included w/them (which is older than that available at creative site). And I think this replaced the 5.12.1.1161 ct_oal.dll w/OpenAL32.dll. So I copied the original 5.12.1.1161 ct_oal.dll back into system32 directory and then ran the latest OpenALwEAX.exe w/OpenAL32.dll v6.14.357.9. Then replaced BF2OpenAL.dll w/this 6.14.357.9 OpenAL32.dll version. Now everything seems to run perfectly and no crashes.
Re: Anybody tried the new X-Fi drivers with an Audigy?
Originally posted by Hugh G. Wrection
ct_oal.dll is only included in the ZS beta driver release (hence the release note about improving OpenAL performance) and newer.
However, after more testing, I don't think you should replace BF2OpenAL.dll with it. It is loaded from the system32 directory automatically by BF2.exe if you select hardware in the audio options. It did seem to work but I also got some crashes after a while that may or may not be related (no assert in dump file to check). So I believe you should replace BF2OpenAL.dll w/the OpenAL32.dll installed by OpenALwEAX.exe.
Also, there is something strange I noticed -- depending on which version of OpenALwEAX.exe you run, it will sometimes replace ct_oal.dll in the system32 directory w/a copy of OpenAL32.dll, just renamed to ct_oal.dll. I'm guessin earlier versions of OpenALwEAX.exe do this b/c they expect older driver releases that did not include a native ct_oal.dll or something.
I installed the 5.12.1.1161 drivers from StationDrivers and first ran the OpenALwEAX.exe included w/them (which is older than that available at creative site). And I think this replaced the 5.12.1.1161 ct_oal.dll w/OpenAL32.dll. So I copied the original 5.12.1.1161 ct_oal.dll back into system32 directory and then ran the latest OpenALwEAX.exe w/OpenAL32.dll v6.14.357.9. Then replaced BF2OpenAL.dll w/this 6.14.357.9 OpenAL32.dll version. Now everything seems to run perfectly and no crashes.
That's a tongue twister...once I have figured out where all of my different file versions reside and back them up, I'll give this a go and let you all know.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment