Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: flame on May 09, 2007, 10:32:45 pm
-
Every time I start the program I get cannot find openAl32.dll :confused:
-
Try installing OpenAl. http://www.hard-light.net/forums/index.php/topic,35766.0.html
Oh and by the way:
:welcome:
Welcome to the HLP Station. Do not feed the resident Shivan Carl as he will become voracious and chew your leg off. You can find him in the ventilation duct. Throw him your lunch and he'll leave you alone (usually). Flamethrowers can be found under your seat but due to financial constraints have been re-filled with holy water. Plasma rifles can be found in storage lockers. To prevent act of n00b, however, these can only be opened by Moderators, Volition, GOD or a hyperintelligent shade of BluE. Please, do not mention the sequel of FS2 if you want to remain undamaged. If you go in the Vasudan section of the station and find a box labelled “Headz”, please don’t open it. Enjoy your stay!
-
Use the Installer link in my siggy if you want FS1, more campaigns etc.
-
I got the same problem as Flame:
when I'm launching FS2open, I got an error message telling me that OpenAL1.1 or newer is required and so on. Well I go get it, I install it, I launch the game again and tada! I get the same message. If I'm launching the game (well, it launches it regardless), I get the fllowing error:
"failed to create the command recognition context"
and the game crashes. Is this a known error and is there a known workaround?
-
I got the same problem as Flame:
when I'm launching FS2open, I got an error message telling me that OpenAL1.1 or newer is required and so on. Well I go get it, I install it, I launch the game again and tada! I get the same message. If I'm launching the game (well, it launches it regardless), I get the fllowing error:
"failed to create the command recognition context"
and the game crashes. Is this a known error and is there a known workaround?
:wtf:
How long have you been here Nico!!!!!!?
:confused:
*Edit*
Sorry, that wasn't very helpful was it!
Try this:-
Check in C:\Windows\System32 for either ct_oal.dll or nvopenal.dll, and if either exists then delete them.
-
I tried that, I found the second dll, deleted it, but it still won't work ><
-
I tried that, I found the second dll, deleted it, but it still won't work ><
Try un-installing and re-installing OpenAL, otherwise do you have any renegade dll's in your Freespace directory?
BTW, What's SCREW CANON, is it something to do with the rifling in the cannon barrel! (j/k) :lol:
-
Nope, tried that, still not working :/ Don't have anything else in the folder either as far as I know, it's a brand new folder, FS2 had not been installed on my HD for a couple years at least, and I only used Turey's installer to install everything. The only DLL in there is the patchw32.dll file.
I can't play FS2 because of one stupid sound-related file ><
The screw canon sig comes from this thread iirc:
http://www.hard-light.net/forums/index.php/topic,30194.0.html
I was doing a HTL moloch with quite a personal vision of its design, which started quite an argument over the fact it was not "canon". As my stand regarding the original models is that they're low poly, don't include much details and so on, I take them more as guidelines than anything else, and then sometimes I just don't like the originals or parts of them, so I just decided that canon was a pain and therefore: screw canon :p (was also a stupid pun but heh).
-
Then I'm at a loss I'm afraid! ??? Maybe Kara or Goober could help you with this one? You are selecting General Software in the audio tab in the launcher aren't you? I don't think this will have any effect but you never know!
Sorry I couldn't be of any more help! :( :sigh: :confused:
-
K, I got it to work, but only w/o sound... no matter what I do, it won't find that stupid OpenAL1.1... Why the hell does it need that anyway?
-
Cause without it you have no sound. Basically all the game audio now goes through OpenAL instead of DirectSound like it used to.
http://www.game-warden.com/forum/showpost.php?p=62754&postcount=2
That was written with BtRL in mind but most of those problems affect FS2_Open too. If that doesn't work try grabbing the OpenAL dll's and sticking them in your FS2 folder.
-
Cause without it you have no sound. Basically all the game audio now goes through OpenAL instead of DirectSound like it used to.
Lol.
From my point of view, because of it I have no sound. What was wrong with using directsound? Using MS stuff isn't leet enough or something that support for it had to be completly removed altogether? That's pretty dumb.
-
From my point of view, because of it I have no sound. What was wrong with using directsound? Using MS stuff isn't leet enough or something that support for it had to be completly removed altogether? That's pretty dumb.
Because of something in your system config you have no sound, it's not OpenAL's fault. :P
But DirectSound had no support in the first place. It hasn't has a single upgrade or fix since the original code release. OpenAL is the only code path that receives any coder support, and that's because it's all I use. It only makes sense to drop DS completely and move entirely to OpenAL. It makes the code cleaner and easier to maintain, works on all three OSes, and it's always easier to implement new features for one API (like future 5.1 3D surround sound and EAX support in the OpenAL code) rather than trying to get it all working in multiple APIs.
You might as well get used to it anyway. Doom3 uses OpenAL, as does current/future Unreal/Unreal Tournament titles. And given the fact that OpenAL is the only way to get hardware accelerated sound in Vista/DX10, it's a good bet that most games will move to using OpenAL as well.
-
The thing is, Doom3 and LineageII that also uses OpenAL DO work fine on my PC, so please do tell me what's wrong?
Edit: I may sound harsh with my post above, so I apologize. I want to point out that you say that it has always been ApoenAL in the previous builds. I used to use these, and it worked before (well, I did have problems with sound parasites, but at least I had sounds), and I assume not many people have the problem I have, so the latest build is probably not at fault. Therefore, is there a possibility that there is a file missing or something with the installer that prevents a clean install from working? Because I'm honestly out of options there, I tried various installs of openAL, and they all result with the same problem ( the game stating that openAL 1.1 is needed and not present, regardless of any version I have installed). I also would like to know where exactly are the dll supposed to be installed when you install OpenAL? In the system32 folder? is there any other file installed besides the two dll?
-
The only thing I can think of is to make sure you've got the latest version, which is here (http://www.openal.org/downloads.html). (Open AL 1.1 version 1.9.9)
-
Edit: I may sound harsh with my post above, so I apologize. I want to point out that you say that it has always been ApoenAL in the previous builds. I used to use these, and it worked before (well, I did have problems with sound parasites, but at least I had sounds), and I assume not many people have the problem I have, so the latest build is probably not at fault.
OpenAL has really only been default since the latter half of last year. The DS code is still there, for now, but will be ripped out when I redo the sound code later this year. At that point the OpenAL code will be far cleaner than it is now (since it currently has to be set up to work more like the DS code than what's better for OpenAL). Hopefully that will help remedy most of the the more difficult issues that people are having. It will also not require OpenAL 1.1 at that point either, since it will load dynamically and adapt to the version installed, giving you the 1.1 features only if they exist.
Other people have had the same problems, so it's not new, but it has always been the same 3 basic causes/fixes. Either: 1) You have old hardware dlls from old sound card or motherboard drivers which force the version down to 1.0 instead of 1.1. 2) The install is screwed up, probably due to a conflict with something else on your system, and in this case it may not be possible to do a standard install to fix the problem. 3) Your sound card drivers are causing a problem and need to be updated.
#1 is the most common, that being the nvopenal.dll and/or ct_oal.dll files present. #2 is the most difficult to deal with, but is most often fixed by simply copying the openal32.dll and wrap_oal.dll files from your install of OpenAL 1.1 directly into the game directory. It can also mean that you just have a bad install of OpenAL 1.1, usually from an old installer and not the most current version from Creative's website. #3 usually only is an issue for users of certain Creative sound cards, but I think it can be an issue for out-of-date NVIDIA stuff as well.
-
Mmmh... Well I have gone through the option 1 fix, I've tried copying the dlls in the FS folder, which did not work either, and 3... well, I'll have to look furthur into that, because my PC is one heck of a mess regarding audio configs (there's an inboard nvidia chipset on the mobo, and I think I have that old SB pro, I know I connected/disconnected one of the two, but that was a long time ago, don't remember what I did exactly). I just can't understand why Doom3 uses it w/o any pb, but not the SCP; this kind of rules out any "hard" hardware problem, doesn't it?
jr2: that's the first version I tried.
-
I just can't understand why Doom3 uses it w/o any pb, but not the SCP; this kind of rules out any "hard" hardware problem, doesn't it?
I can't say for sure, but I'd bet that Doom3 includes it's own OpenAL dlls and runtime loads them. It's the most difficult way to do things, but it's the most flexible as well. It also helps get rid of any loading issues that the system itself might have. Those loading issues are probably what you are running in to. Old dlls, multiple dll versions, dll conflicts ... it's not called "DLL Hell" for nothing you know. :)
With the sound code rewrite later this year (which was actually started early last year) we will move to using runtime loading as well, which means that the game won't be linked directly against OpenAL. This basically requires a complete rewrite of the sound code, which is why it's taking a while. The Launcher already uses runtime loading of OpenAL, so that the Launcher itself will still work even if OpenAL isn't installed.
Until the new code is ready there is nothing we can really do though, since the current problems are compatibility/conflict issues which are specific to each system.
-
Oki... :sigh:
I've double-checked my sound drivers, my dll, everything, can't see anything wrong, so I guess I'll just postpone my playing FS2 again till the build that gets the runtime loading code... Too bad, I really was in a FS mood these days :(
Ah well.
-
Did you manually search for and rename every instance of openal32.dll and wrap_oal.dll and whatever else before reinstalling? Did you clean your registry after uninstalling OpenAL and before reinstalling?
I'm reaching here, I know...
-
you want to do that EVEN with the ones in Windows and system32 folders.
-
I did all that half a dozen times. I've given up.
-
You have the latest drivers for your sound card?
-
yes, I even reinstalled them just in case, no luck.
-
K, just in case, can you post your FS2 directory listing?
Can you post your directory listing? Start->Run, type cmd press enter
type dir "c:\games\freespace2" /s>"%homepath%\my documents\fs2dir.txt"(replace c:\games\freespace2 with your fs2 dir drive / path as neccessary)
Then, post it, hit "Additional Options", hit "Browse", find your fs2dir.txt file in your My Documents folder, then post it - if you don't see "Additional Options", then hit the "Preview" button first, then it will show up.
K? :)
-
Sure thing, there you go, but I think you're wasting your time ;) Anyway, thanks for willing to be helpful, I'm grateful :)
Mmh, all the characters with accents (like "é") are messed up, but there's nothing like that in the name files (or there should be), so it shouldn't be a problem.
[attachment deleted by admin]
-
Where did the OpenAL32.dll file in your main FS2 dir come from? Mine (latest version) is 131,072 bytes, in windows\system32
Yours is 21,504 bytes... something wrong or out of date...
Open a command prompt, switch to your \windows\system32 directory
type cd \windows\system32then type dir openal32.dllSee what the size is. If it's 131,072 bytes, then type copy openal32.dll e:\jeux\freepace2 and overwrite the other one.
Does this help?
-
Run the debug build and post the FS2_Open.log that will appear in your Data folder.
-
He said he deleted all the openal files from his hard drive, so how could he possibly have the wrong size file unless he's not using the latest installer? Sounds fishy to me.
-
I dunno, but look at his directory listing. It states he has openal32.dll in the FS main dir.. and it's size is different from the latest version. He also has another open al .dll in there, wrap_oal.dll (but that one is the correct size).
23/12/2003 19:37 21ÿ504 OpenAL32.dll
06/05/2007 23:55 171ÿ520 patchw32.dll
06/05/2007 23:55 6ÿ404ÿ494 root_fs2.vp
07/05/2007 04:48 123ÿ130ÿ194 smarty_fs2.vp
07/05/2007 01:18 260ÿ563ÿ452 sparky_fs2.vp
07/05/2007 02:43 265ÿ242ÿ014 sparky_hi_fs2.vp
07/05/2007 03:35 173ÿ166ÿ260 stu_fs2.vp
07/05/2007 12:22 <REP> Sync
07/05/2007 05:50 195ÿ887ÿ233 tango1_fs2.vp
07/05/2007 06:13 72ÿ778ÿ161 tango2_fs2.vp
07/05/2007 06:29 50ÿ497ÿ261 tango3_fs2.vp
07/05/2007 14:52 <REP> temp
07/05/2007 09:12 <REP> tools
07/05/2007 12:21 <REP> Transcend
06/05/2007 23:55 270ÿ336 UpdateLauncher.exe
07/05/2007 04:08 118ÿ858ÿ128 warble_fs2.vp
11/05/2007 18:23 409ÿ600 wrap_oal.dll
35 fichier(s) 2ÿ438ÿ386ÿ965 octets
-
Yeah, that OpenAL32.dll looks like a 1.0 version (and a pretty old one at that). The wrap_oal.dll, which does most of the work if you don't have full/native OpenAL support in your sound drivers, looks good. But even if the wrap_oal.dll is the 1.1 version, the version check is only going to report what version the OpenAL32.dll is, which most likely means 1.0.
-
It works! I've desinstaled everything (and I mean everything) sdound related on my computer, then I manually deleted all the registry entries, rebooted, did a second registry cleaning ( there was a couple things that refused to be deleted for somereason on the first wipe), reinstalled everything, and now it works ^^ thanks for your support people :D