Posts: 18
Joined: Nov 2010
Reputation:
0
Jurai
Junior Member
Posts: 18
I've just upgraded to the latest version after being on an 0.7 build for awhile, I'm seeing constant problems where mednafen will launch but xbmc will still retain focus. It also seems like the time between selecting a rom and the application launching has substantially increased from what I remember
I'm also using a 360 pad as my xbmc input device with the eventlistener application, seems that XBMC is still receiving and responding to input from the 360 pad when the emulation app launches as well
Posts: 159
Joined: Jan 2010
Reputation:
1
What OS are you on? Windows, I guess, because I'm having no troubles with mednafen, the 360 controller and the launcher...
Posts: 18
Joined: Nov 2010
Reputation:
0
Jurai
Junior Member
Posts: 18
went back to 0.7.5 of the addon and none of the mentioned problems seem to occur, im on win7 with dharma 10.0 release version. yes I'm aware the commandline changed. guess ill reinstall xbmc from scratch and see if that helps.
Posts: 18
Joined: Nov 2010
Reputation:
0
Jurai
Junior Member
Posts: 18
K, fresh installed with latest version of plugin (0.9.3), it appears to still be allowing xbmc to process input in the background, causingg me to launch mednafen multiple times as im playing the game. XBMC did NOT process the events in the old version while app was running.
In 0.7.5 (and not sure how far past) I know there was specifically an option in the config to choose whether to Freeze XBMC when the app launched or just launch the application, does the plugin no longer offer the option to freeze xbmc while your application is running?
Posts: 65
Joined: Dec 2010
Reputation:
0
Hey Angelscry,
I've changed the default info scraper to GameFaqs, because I like my "Description" field to be the text from the back of the game boxes. I also turned on automatic Boxart import for US boxes (also from GameFaqs). However, ALA is automatically pulling in FanArt too, even though I do not have this option turned on. I believe this is a bug.
Also, ALA doesn't store the info for the Roms anywhere. It would be really nice if ALA read the info from a ROM.nfo file that was stored with the emulator in the same way that fanart and thumbs are stored. Even better, if you mimicked the current file layout that XBMC uses for Movies! Store the Fanart.jpg, Boxart.jpg, Rom.* and Info.nfo files in a folder with the same name as the rom:
"Rom Folder"
|====="Rom Name"
|======|------Rom Name.zip
|======|------Fanart.jpg
|======|------Thumb.jpg
|======|------Info.nfo
|====="Another Rom Name"
|======|------Another Rom Name.zip
|======|------Fanart.jpg
|======|------Thumb.jpg
|======|------Info.nfo
What do you think?
Posts: 13
Joined: Dec 2010
Reputation:
0
Thought I would share a bit on why my emulators weren't launching. The issue is that was causing them not to launch is a space in the path.
I was running my testing of emulators from my desktop. My username in windows 7 has a space in it, and it was causing a failed addon.py error.
I changed all of my emulators to a more standard c:\games\ , and they boot right up!
Not sure if the new version of advanced launcher needs to put "" around the path in the launchers.xml, just in case to cover peoples scenarios?
Posts: 2,710
Joined: Feb 2009
Reputation:
12
ppic
Skilled Python Coder
Posts: 2,710
just a question, why do you import xbmc here ?
seems to be not used.