2009-12-11, 09:47
Not sure where to put this so I figured here would be ok. I'm having issues launching Nestopia with Launcher. I don't think it's an issue with launcher since I'm getting the following message from Nestopia:
"Can't start! Direct3D is busy!"
Checking some reference source code for Nestopia shows it's clearly a D3D handle error - the application cannot initialize a D3D resource for some reason.
The strange part is that it always works 100% the first time I try and launch a game from XBMC. After I quit and Launcher returns me to XBMC I am unable to launch a second game. If XBMC is not running, I can run and close Nestopia indefinitely without the error. The XBMC log shows nothing unusual, and a second emulator (ZSNES) runs flawlessly from Launcher. So I wonder if anyone would have some more insight into the problem? Is there some inherent D3D conflict that's created by using XBMC? I suppose I could always try another emulator but I've grown fond of Nestopia.
"Can't start! Direct3D is busy!"
Checking some reference source code for Nestopia shows it's clearly a D3D handle error - the application cannot initialize a D3D resource for some reason.
The strange part is that it always works 100% the first time I try and launch a game from XBMC. After I quit and Launcher returns me to XBMC I am unable to launch a second game. If XBMC is not running, I can run and close Nestopia indefinitely without the error. The XBMC log shows nothing unusual, and a second emulator (ZSNES) runs flawlessly from Launcher. So I wonder if anyone would have some more insight into the problem? Is there some inherent D3D conflict that's created by using XBMC? I suppose I could always try another emulator but I've grown fond of Nestopia.
