Middcore
Members-
Posts
26 -
Joined
-
Last visited
Middcore's Achievements
8-Bit Processor (3/7)
0
Reputation
-
Can't give you a log file, unfortunately. Because after I installed Launchbox on another PC, got it working without issue, copied the whole thing over to my emulator PC, and immediately got the same errors again, I got fed up. I did a complete clean reinstall of Windows on the emulator PC and started over. The good news is all themes now work flawlessly. The bad news I still have no idea what was actually causing the problem before so I can't be of any help to anybody who might run into the same issue in figuring out if there was a less extreme fix. But I felt a week and a half of screwing around is enough and nuking it from orbit was the only way to be sure. I do appreciate the efforts to assist, though.
-
In my case everything including ROMs are on my C drive, an internal SSD which is the only drive in the PC.
-
Yep, I know what it's supposed to look like, it's pretty rad, that's why I wanted to use it. Unfortunately it doesn't work for me, like every other theme besides the default.
-
Here's what's supposed to be the BannerBox theme platform text list with details view. As you can see it's grabbed the appropriate platform image and done absolutely nothing else to actually alter the theme/layout, and of course there's a triple flurry of error messages to dismiss at frequent intervals.
-
As I said, sometimes it manages to use fonts from the chosen theme. Tell me what view you'd like me to use and I will switch to it and post a screenshot.
-
Here's a screenshot with CriticalZone applied as the main theme. Once the error messages are dismissed it does basically nothing, it's indistinguishable from just leaving the default theme on. I guess that green font is coming from CriticalZone? (SNES is the only platform I added some games back for to test after my fresh install so ordinarily there would at least be all of the platforms listed.) On the previous page I also posted a screen of an attempt to use the AllNightLong theme, where the best it can do is load one of the AllNightLong's platform images in the space the default theme uses for its platform images (box in upper middle of the screen) while changing basically no other aspects of the theme at all. Some themes like CityHunter do manage to change the text for the descriptions.
-
I have done a fresh install carrying nothing over. I don't even need to download a new custom theme, switching to the CriticalZone theme which comes with Launchbox triggers the errors immediately and of course CriticalZone looks completely broken as well. Use of ANY theme other than the default one appears impossible.
-
I have completely deleted Launchbox from my system and reinstalled, preserving only my data folder. As soon as I apply and install any custom theme the same error messages return. Did you see the screenshots I posted of my launchbox/core folder?
-
Attached are screens showing the whole contents of the Launchbox/Core folder (too much to fit in one screen and I didn't know what you needed to see). I just updated to the latest beta and it makes no difference, same errors.
-
Not trying to bother but it would be nice to know this is being looked at and taken seriously as an issue.
-
Bumping, hope that's ok. Anybody have any more ideas? Appears from the post above me that my issue is not unique.
-
Gotcha. Installed Launchbox to a different location (documents folder), copied over platforms xmls. Installed one of my problematic themes. Same error messages and reverts to default theme with bits of the installed theme frankensteined into it. In other words, same problem on a fresh install.
-
I don't understand what you mean by copying one of the platform.xmls. Where would I find these?
-
Like I've said, it happens on every single theme I have tried besides the default. The default is the ONLY theme that functions and does not throw these errors. A partial list of ones I've tried so far: AllNightLong BannerBox CoverBox CityHunter 2 RetroFresh I'm considering nuking my Launchbox install and starting over as a last resort but I'd like to avoid that as it will take half a day to reimport all of my games, etc.
-
Done, didn't make any difference. I was on version 1903, just updated to version 2004. Problem persists after update.