- #Xear audio center could not find any device how to
- #Xear audio center could not find any device install
- #Xear audio center could not find any device serial
- #Xear audio center could not find any device drivers
Different game but it dealt with the exact same issue, almost verbatim, that I was having. I found the "fix" on a Reddit page for the game "Rise of Nations". Qaeylen: ** I posted this in another thread here, it might work for you as I was getting similar errors.
#Xear audio center could not find any device how to
Credit goes to the user "Helios210", who posted how to rename that file.
![xear audio center could not find any device xear audio center could not find any device](https://blogstudio.s3.amazonaws.com/parker-gwen/d31bfe0bf1ec942d1925327215d19f85.jpg)
I haven't tried playing anything yet, but I can see the menu, and the UI and so.
#Xear audio center could not find any device install
I didn't have to mess with any other DirectX versions, this was on a clean install direct from GOG, no additional patches and it wasn't run or installed in compatibility mode. In the install folder of the game, there should be a file called dbghelp.dll.Īll I had to do was rename it to dbghelp_old.dll and it frickin worked! I was able to load up the game, full screen, no problem at all.
#Xear audio center could not find any device drivers
After working with support most of the day, updating drivers and trying varying degrees of compatibility mode, I found one thing through Reddit that actually worked for me. I would get the "No Direct 3D Device" error, along with "Fatal Exception" errors as well. I had the same issue as most, the game would launch in the background and I could hear audio but nothing would appear. I've manually reinstalled DirectX9.0c, and still no change.Īnybody getting the same? ** I posted this in another thread here, it might work for you as I was getting similar errors. I've messed with dxcfg.exe, but nothing changes.
![xear audio center could not find any device xear audio center could not find any device](https://present5.com/presentation/534fb19deda8d661a65743880572bcb7/image-123.jpg)
"Could not find any compatible Direct3D Devices. I don't see any game window or change in resolution, when I do get to the main menu I get this error: probably RBE is wrong, because i don't think can ever be correct that a simple load/save cycle changes the binary.Stormcrow900: So when I start SFC3 from Galaxy, I don't see any cutscenes, but I can hear them. If you save your bios with GPUZ you get a different bios then if you save it with RBE.Īnd lol, there is no way of knowing which one is the correct one (unless the sources float around here somewhere). So forget everything I said about this offset related stuff, it is all based on FUD. Simple example: take your or NEX'es original file, load in RBE, CHANGE ABSOLUTELY NOTHING, but immediately save it in RBE again: kazinga, the saved file is not equal to the loaded file. I just did a few more tests, and the whole thing with differences at positions 0x0007, 0xDE39, 0xDE7A, 0xDE7E -> turns out that it actually is RBE that is doing this !!!! gotta love just looked at NEX'es files and he has the same combination of orig and RBE modded as you. since A is after 9 I would have expected it to be locked as well, but now that NEX says his B9 is unlockable nothing is certain anymore).
#Xear audio center could not find any device serial
On a different note: I just got word from a person selling his 2GB DCII who says its serial is BAxxxxx and that it is unlockable (don't know how thrustworthy that is of course, since he is selling it so he has a slight bias. Maybe you downloaded some other bioses that day and overwrote the ones you made yourself ?Īnyway, it is not really that important of course. So either there is a flaw in the steps above, or otherwise you have to admit that there is something fishy going on with your originals. But they are not in the originals you provided, so your originals are not your real originals. I think it could only have happened if you started from a bios retrieved from your card that contains these bytes. : I currently do not know a place where you can download a bios that has at positions 0x0007, 0xDE39, 0xDE7A, 0xDE7E the bytes you have in your modRBE.bin. (you can try this for ourself, if you do find a way, be sure to let me know) : In the files you uploaded, there is no way that you can get from your original(2).bin to your modRBE.bin using the RBE or w1zzard php tools. The logic I use to get to my conclusion is:
![xear audio center could not find any device xear audio center could not find any device](https://present5.com/presentation/534fb19deda8d661a65743880572bcb7/image-9.jpg)
The difference is in bytes 0x0007, 0xDE39, 0xDE7A, 0xDE7E, see a few post back where I made the list.