Jump to content
LaunchBox Community Forums

lightfox

Members
  • Posts

    5
  • Joined

  • Last visited

lightfox's Achievements

4-Bit Adder

4-Bit Adder (2/7)

2

Reputation

1

Community Answers

  1. Yeeep, very possible those cyrilic characters were converted into broken asian characters because of my weird config ^^;
  2. I AM morbidly curious! =D Thank you for pointing the folder \LaunchBox\Metadata\Temp out, thanks to that, and found some file with no extension that turned out to be the real XML Launchbox uses for importing games. ...and at line 4292731, I found this. "Column 47" is also very misleading here, because the tag is prefixed with two tabs, each counting as one character for launchbox, but as 5 characters for my notepad++... ThIS is the issue. the value of the "name" attribute is broken, and as a result breaks the entire XML. And this is only visible in LaunchBox's own XML because it's being clever, and imports data from other files that have charsets that are incompatible with the way my system is setup. The root cause? Well..I'm also playing japanese language video games. For that to work, I have set up my PC a certain way that LaunchBox didn't like. By going to Control panel > Region > Administrative > Language for non-unicode programes, I have set it up to "Japanes (Japan)". Switching it back to English did the trick, and now launchbox finally could import my MAME fullset! => SOLUTION: Go to Control panel > Region > Administrative > Language for non-unicode programs and make sure to select "English (United States)" (this requires a restart of the computer if it was something else before),
  3. I did, several times, same error every time
  4. I guess that we want to consider that line 1 = line number of of the <mame> tag, I have to subtract 163 lines, not add them? So that would lead to line 4292568. Still nothing there: For good measure though, nothing wrong at line 4292894 either: Also, unless there is something specifically forbidding it inside the code of launchbox, it's perfectly legal to have an xml attribute starting with the character "8", so something like this for example should be parsed as valid xml: Besides, the example here is way before line 4000 000, so it was probably parsed properly already. There is also nothing similar around line 4000 000 in that file: I'd also like to point out that the problem coming from this file is an assumption on my part, no idea if this is the correct place to look. It doesn't help that launchbox doesn't provide more detail info with regards to this error. I also searched all the xml files in the folder where Launchbox was installed, and didn't a single match for the string "<8"
  5. Hello! I obtained the MAME 0.285 ROMs (merged) , copied it in separate folder from the one being tracked by bittorrent, and tried to import it via Launchbox v13.26 (on windows 10). After maybe 10 seconds of parsing, I'm getting this error: I tried to go into the MAME downloaded by Launchbox (which I confirmed is indeed v0.285 by runing mame.exe -version), and generated the catalog with mame.exe -listxml > list.xml When I go to line 4292731, I see this, which doesn't seem invalid to me: I also looked for any occurence of "<8" in the file, and found nothing, which means that file shouldn't have any tag whose name starts with the character '8' The "Logs" directory of Launchbox is also emtpy, and I don't see any sneaky folder in the appdata. In every youtube tutorial I found on this topic, the presenter doesn't go into details about this step. It's just a simply one-click, no trouble step with no mention of what could go wrong. I may have missed, but didn't find any topic on this forum with that issue. So I am rather confused as to what's going on. Anyone can help me? Launchbox looks like a really cool app, and it's a shame it immediately fails like this with a pretty cryptic error message and no hint as to how to fix it.
×
×
  • Create New...