29-03-21, 16:48 | #21 |
Member
Joined: Aug 2008
Posts: 12,070
|
By the way years ago I mentioned the ALChemy method in another thread and there was a person with literally the same issue, so it's not strictly related to this wrapper. No idea if the guy fixed it though.
|
29-03-21, 17:08 | #22 |
Member
Joined: Jul 2020
Posts: 1,523
|
The only thing I can possibly think of right now if everything is installed correctly, and it definitely is in your case, plus the registry edits being in place - is a conflicting driver or something that is intercepting DSOAL before it can be detected by the game. Other than that, I'm stumped at the moment.
The strange thing is that unlike ALchemy, the point of DSOAL is to be a generic workaround for the proprietary software used by Creative, so it should work straight out of the box. That's what's making me wonder if it's some conflict or something. |
29-03-21, 18:24 | #23 |
Member
Joined: Jul 2020
Posts: 1,523
|
Caesum, this might not change anything, but it can't hurt to try. I noticed from the first post you made in the thread you mentioned that you put the wrapper files "in both the main folder and the bin folder just in case."
I don't think DSOAL actually loads if not in the presence of the exe files, but if it's in both the main folder where Bin, Data, etc are alongside being in the bin folder itself, the game could be getting confused of there being two sets of the same files. Try removing the ones in just the main folder so that you have them in the bin folder only and see if that changes anything. Other than that, DSOAL documentation mentions that the presence of virtual surround software (Dolby Atmos, SBX Pro Studio, etc) can conflict with dsound.dll, but I don't run into that situation often with other people using DSOAL, so I didn't mention it. Don't think that's what's wrong here anyway. If you wouldn't mind doing so, could you also grab a couple of screenshots showing the registry edits you made? Only the tweaks of course. Just want to make sure they check out. Just wanting to make sure you're able to enjoy this like everyone else. Keep me informed. Last edited by Jathom95; 30-03-21 at 17:09. |
31-03-21, 22:27 | #24 |
Member
Joined: Jul 2012
Posts: 6,507
|
Jathom95, would you post this solution to the TRAOD PC Gaming Wiki article so that more people can learn about this? This is always my number 1 stop after installing an older game to make sure that I get the most out of it and I'm sure that others have the same habit.
|
01-04-21, 00:07 | #25 | |
Member
Joined: Jul 2020
Posts: 1,523
|
Quote:
I think there's something about it under issues solved, but strangely enough the solution is only posted as "Install EAXUnified Drivers", which wouldn't be enough to enable EAX even under ALchemy. Edit: Added to PCGW! Last edited by Jathom95; 01-04-21 at 02:02. |
|
01-04-21, 05:54 | #26 |
Member
Joined: Jul 2012
Posts: 6,507
|
Cool, thanks! Is is that easy to post something there? Somehow I always assumed that you have to get the okay from the moderators or something like that.
|
01-04-21, 11:59 | #27 |
Golden
Joined: Oct 2009
Posts: 11,534
|
Doesn't work for me either. Same as Caesum.
Last edited by klona; 01-04-21 at 12:03. |
01-04-21, 12:44 | #28 |
Member
Joined: Aug 2008
Posts: 12,070
|
I managed to make it work! I had to use the ALTERNATIVE method here in order to make it work. The changes made in CURRENT_USER wouldn't do anything. I had to strictly change LOCAL_MACHINE keys. Now it works and it sounds amazing.
So it seems Windows 10 forces applications to look for dsound.dll specifically in Windows/System32 folder. This means the file you put in your game directory folder is not used at all. For that to change you need the mentioned above alternative method. The problem is Windows 10 won't allow you to change values easily. You need to: 1. Ctrl+Alt+Delete and enter Task Manager 2. Click File / Run New Task. Then write regedit and check the 'Create this task with administrative privileges' field. Click Ok. 3. Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{3901CC3 F-84B5-4FA4-BA35-AA8172B8A09B}\InprocServer32 then right click the key and click on Permissions. 4. Click Advanced. Next to Owner click Change. Type your username or account type (eg. Administrators) and click Check Names. If done properly it should find it. Click Okay. 5. Return to main Permissions window and select your username/account type (eg. Administrators). Check "Allow" field next to Full Control. 6. Change (Default) value to dsound.dll 7. Repeat same steps for: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{47D4D94 6-62E8-11cf-93BC-444553540000}\InprocServer32 HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CL SID\{3901CC3F-84B5-4FA4-BA35-AA8172B8A09B}\InprocServer32 HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CL SID\{47D4D946-62E8-11cf-93BC-444553540000}\InprocServer32 Restart and see if it works. Apparently Windows 10 tends to reset these to default values during OS update so it is possible that you will have to repeat this from time to time. Last edited by Caesum; 01-04-21 at 13:21. |
01-04-21, 16:02 | #29 | ||
Member
Joined: Jul 2020
Posts: 1,523
|
Quote:
Hmm, that's strange. Could you try what Caesum posted below if you feel comfortable editing the registry and let me know if it changes anything? Quote:
I never would've thought it would've been the registry edits. I've always been able to make the first solution work for me flawlessly. It's possible that Windows just won't "detect" it for some reason on some configurations. In any case, whatever works, right? Yes, the guide mentions it's possible they will reset with the second solution. In my personal experience, that doesn't really happen very often. But keep an eye out, especially after system updates. If you notice anything strange or it stops working, check to see that the edits are still in place. Great work, Caesum! I knew you'd figure it out. Last edited by Jathom95; 01-04-21 at 17:05. |
||
02-04-21, 08:42 | #30 | |
Member
Joined: Sep 2007
Posts: 3,392
|
Quote:
|
|
Thread Tools | |
|
|