Middcore
-
Posts
26 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by Middcore
-
-
In my case everything including ROMs are on my C drive, an internal SSD which is the only drive in the PC.
-
1 hour ago, neil9000 said:
Yeah. This is Bannerbox on my system, literally downloaded a minute ago via Bigbox's built in theme downloader.
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.
-
5 minutes ago, neil9000 said:
That is the Critical Zone theme though, you can tell by the green text which the default theme doesnt have, so it is displaying one of the Critical Zone views, or using settings from it still. Can you try switching views via the menu or from a keyboard/controller button set to switch view?
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.
-
8 minutes ago, neil9000 said:
Could you share some images? as any theme not working is certainly not the norm at all. And just to test for my own sanity as i dont use Critical Zone as my default, i just switched to it and it works just as expected on the current beta 5.
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.
-
2 hours ago, Jason Carr said:
Yeah, I know. Still puzzled though because most people aren't running into this issue, and I haven't been able to replicate it.
I did; unfortunately they're as expected, so that doesn't appear to be the issue. Can you confirm if installing fresh (without copying your data folder over) still has the same issue? If not, then at least we know it's something in the Data folder somehow.
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.
-
2 hours ago, Jason Carr said:
It should be easy enough to copy your data and media folders over. It would be nice to know what's causing it though in the old folder. What I would do first, is copy the LaunchBox\Data folder over from the old folder to the new folder. Be sure to do it while LaunchBox is not running of course. It'll be interesting to know if you start running into issues after doing that or not.
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?
-
23 hours ago, Jason Carr said:
The themes manager does require an Internet connection to gather the details of all the themes. If you don't have an active connection, you can still change themes by simply changing the Theme setting under the Big Box View options.
I haven't seen this or been able to replicate it elsewhere at this point. @Middcore and @KM_Zero, can you send me a screenshot of your LaunchBox\Core folder in Windows Explorer? Also, does it help anything to update to the latest beta? You can update to the beta by going to Tools > Options > General > Updates and checking the box to update to beta releases. You may also want to disable background updates in order to trigger it immediately on a restart.
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.
-
8 minutes ago, neil9000 said:
In the Launchbox/Data/Platfoms folder is where they are stored, lists named after the platforms that list the games you have. Just copy it to the same location in the new install, its just quicker than importing a platform. Dont forget to copy your license also.
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.
-
5 minutes ago, neil9000 said:
If you install a fresh Launchbox to a different location, and copy across one of the platform.xmls and add a theme that currently errors do you still get the same issues?
I don't understand what you mean by copying one of the platform.xmls. Where would I find these?
-
Just now, Jason Carr said:
Well, I'm pretty puzzled then, as I haven't heard of this issue from anyone else. What theme are you trying to use?
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.
-
1 hour ago, Jason Carr said:
Okay, try completely uninstalling .NET Core from add/remove programs, then reboot, download, and run this:
If that doesn't work, what version of Windows 10 are you running? You can get the details on the version by typing "winver" into the Start menu.
Done, didn't make any difference. I was on version 1903, just updated to version 2004. Problem persists after update.
-
7 minutes ago, Jason Carr said:
If it did indeed repair some corrupted files, then I'm fairly certain that Windows corruption is the culprit, unfortunately. From what I've read, sometimes you do have to run the "sfc /scannow" command multiple times in order to fix everything, so that would be worth trying. The best course of action is to run it after a fresh reboot, and keep rebooting and running it until it no longer reports any errors. Let me know if that makes any difference.
I've done it twice more and it no longer finds any errors. The problem in Launchbox persists.
-
If it might shed any further light... here's what happens when I try to use the AllNightLong theme (just an example, no themes other than default work)... you can see it loading the AllNightLong platform images inside the box the default theme uses for platform images, but that's all it manages.
-
10 minutes ago, Jason Carr said:
Thanks @Middcore. What theme were you running when those errors appeared? Unfortunately, I'm guessing you have some sort of corruption with your .NET Framework or .NET Core installs. It might be worth trying to uninstall and reinstall them. It also might help to run "sfc /scannow" from a command-line to see if it finds and fixes any Windows errors or corruption.
Hello Jason, thanks for the suggestion. I have run scannow and it said it repaired certain corrupted files but it makes no difference with the problem. I am at a loss as to how I would uninstall and reinstall the .NET framework and instalk. My understanding is they cannot be uninstalled from Windows 10 anyway. My framework is 4.8, which is the newest, and I've just installed the latest version of the core. The problem persists.
-
2 hours ago, Jason Carr said:
What specific errors are you getting?
Screenshots attached. This happens with any and all themes other than the default in Retroarch 11.6, it even happens switching to the other included theme, CriticalZone.
-
Getting this same error. Bigbox throwing errors for any and all custom themes and none of them work. I do not have anything on an external drive. I have deleted Lunchbox/Core and reinstalled 11.6 on top of it without any result. It actually throws the errors even when I switch back to the default theme now.
-
4 minutes ago, klepp0906 said:
Middcore ever resolve this?
If i cant use bigbox via steamlink (actually steamlink app) then its become very close to useless for me.
I tried a DS4 wired to the shieldtv unit. Ive tried the steam controller wireless over bluetooth.
all work to launch bigbox, but once im in the bigbox menu, My controller(s) simply stop working.Nope, I gave up, and therefore gave up on LaunchBox as well until I ever get around to building a dedicated emulation PC I suppose.
-
5 minutes ago, neil9000 said:
I did say it may be needed, what i didnt do however is tell you to rush out and buy it immediately.
I didn't have to rush out, I just did it sitting on my butt on my computer. Ah the dangers of online impulse buying, you sounded pretty definitive and I was eager. ? But I've requested a refund and I'll sit tight for the moment and hope someone can enlighten me about this.
-
5 minutes ago, neil9000 said:
If i was you i would refund it, at least until you know how it works and what it does specifically.
You told me above I needed this application to solve my problem? Just looking for some help here, folks.
If I start streaming through SL, start VirtualHere through SL, then start Big Box, I still don't get any controller input.
I've enabled VirtualHere for my controllers through the Steam Link settings and it still doesn't seem to do anything.
-
OK, just paid $13.99 for VirtualHere on Steam. If it's running, the Steam Link now believes that there is a "game in progress" on my computer, so when I start streaming from SL I get my desktop mirrored and it's difficult/impossible to start anything else. Obviously I am missing something about how to use this?
-
1 minute ago, neil9000 said:
Yep, its a known issue with steam link, it knows that you launched launchbox/bigbox, it doesnt however know that that program then launched another (the emulator). You need to look into a paid steam app called "Virtual Here".
I see. Is this a relatively recent problem? I was watching this guide video from ETA Prime where he makes it sound like the Xbox One controller works smoothly with no reference to Virtual Here.
I'm still puzzled by why it would work initially and then stop. I can't think of any setting I would have changed that would make a difference. Should I reinstall LB/BB from scratch just to see?
.png.91a4cff88b0a354ea0ab9854164946a1.png)
.png.f974a7129e156da4bfcd3cd08cc562a9.png)
.png.7184b693f282e1de63229ca4e1126b3b.png)
.png.6044c7233ef7658c8c46726d4c155efa.png)
BigBox Error Messages When Applying New Theme
in Troubleshooting
Posted · Edited by Middcore
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.