MichaelBolton
-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by MichaelBolton
-
-
Did you download the cores in retroarch? Did you set the emulator preference s up for retroarch?
Sent from my Nexus 5X using Tapatalk -
I'd suggest using the Mupen64plus core, it has all of the good stuff from GLupeN64 rolled into it now.
Too bad it doesn't work on Android or 64b retroarch
Sent from my Nexus 5X using Tapatalk
-
It works perfectly in 32 bit but has a black screen in 64 bit. It also doesn't work on any of my android devices.
Sent from my Nexus 5X using Tapatalk -
Yeah, this was a fantastic game. Can it be played split screen? I think there is a GameCube version that has split screen.
Sent from my Nexus 5X using Tapatalk -
Wow, that's interesting. I'll take a look to see what I can do about that; if that's the case, I'm surprised it hasn't come up before.
I have tested it. It is reproduced.
Sent from my Nexus 5X using Tapatalk
-
so it seems that if the launchbox exists on the root of the drive, all paths that are created have a ..\ in front of them. This is okay as long as it doesn't exist elsewhere in a folder like z:\launchbox\launchbox.exe instead of z:\launchbox.exe. I guess I will start fix all my paths once I move it one folder deeper and hope it works from there, or start over and rebuild an entirely new library.... ugh!
-
2 hours ago, Jason Carr said:
Yeah, but I've never seen it cause weird folder issues like that; that still puzzles me a bit. Also, LaunchBox goes out of its way *not* to cause problems like that if possible. For instance, only XML files that actually change get updated, and files are always refreshed before rewriting them. That way, it shouldn't cause any issues to have two copies of LaunchBox open on two different computers. So I honestly don't know what might have happened to cause all that trouble.
Yeah, It looks like I messed up the paths. I've solved it now, thanks for the input. To be clear, I had launchbox and everything in it on the root of a drive (a mapped network drive). For some reason, some of my paths had ../ in front of them and some didn't! this worked on other computers with the same mapping because everything lived in the root and that was a far back as ..\ could go. Once i synced it to another computer and it was now z:\launchbox\launchbox.exe instead of z:\launchbox. I just have to fix all the relative paths once and my library should work from then on.
-
1
-
-
Dropbox would have done the same thing had I made this mistake. It too creates conflicted files if you try to save something that is open on another computer.
Sent from my Nexus 5X using Tapatalk -
I have discovered dozens of conflicted files. Seems I didn't close launchbox before I launched it on another computer. It made a horrible conflicted file problem. May god have mercy on my soul.
-
the correct path would be "images\arcade"
the path changed itself to "..\images\arcade" so now it thinks the images folder has been moved outside of the launchbox folder....... but only a couple of systems or some roms or some folders.
-
This is a disaster! My entire launchbox system was working perfecly for several days. I used amazon drive to sync the entire thing to other computers. I was under the assumption that everything would stay portable and all the paths were relative. I just launched launchbox and found that randomly a huge portion of seeminly random things have broken paths now. I discovered that some paths have "..\" appended to the beginning of them. This doesn't make any sense, I didn't change any paths, and that wouldn't be the path. I am watching these paths break in real time! For examlpe, n64 was just working, but now the path for the images and video and manual have all changed to up one folder and now it's broken. It also changed the path to the emulators, so literally every single rom is broken now because the emulator it expects has changed to ../
Please tell me I am not crazy!
-
2 hours ago, spycat said:
If you run MAME itself outside of LaunchBox and then select BIOS in the left panel, the main panel will list all bios by name, and the right panel (Infos tab) will show more information including the romset name.
You can also export the bios list to an xml or txt file.Unfortunately, there seems to be no option to identify the MAME Devices files which will also be mixed in with your games.
thanks for the help. I simply moved the entire collection into the rom folder in mame. Then I imported into launchbox without moving the files and set the correct rom path in mame and all is working now!
I'm wondering though, is the mame rom path relative? It seems to say z:\launchbox\games\arcade\ and that isn't relative so I'm afraid it won't be portable unless the other computer uses the same drive letter.
-
Okay thank you that makes sense. So I'll move the other 20gb of files in there. I was being lazy because I'm using Amazon drive to back this whole thing up and didn't want to add 7000 more files than it needed, but I get it now.
Sent from my Nexus 5X using Tapatalk -
I understand all of that, and thank you for your quick reply! However, the problem I am having is I don't know which files in that mame folder are BIOS and which are games. There are 11k files in that folder and they all have inconspicuous names and the same extension.
Sent from my Nexus 5X using Tapatalk -
First off, hello! I built myself an arcade cabinet using hyperspin and rocket launcher and had a lot of fun. Weeks later I'm itching for more and I discover launchbox. This interface is beautiful and feels much more polished! I immediately bought it (and emumovies) and have not looked back. My last system to import is arcade!
Let's say I have the 0.183 complete mame set. When I set that complete folder to be a ROM folder in mame, everything works. I then used the launchbox import tool and chose to copy Roma to games folder because I loved how launchbox weeded out all the games I wouldn't want. Problem is I have no idea what BIOS files from that ROM folder I need to copy over. How can I tell what files are BIOS and what are Roms? Does launchbox have a way to export a list of rejected files during an import? Am I doing this all wrong? Thanks for the help!
Sent from my Nexus 5X using Tapatalk
BigBox always crashes for me lately (eventually) running in attract mode
in Troubleshooting
Posted · Edited by MichaelBolton
I have a cabinet built and I have to restart it big box several times a day. It seems to crash while trying to load the video during attract mode. I just uninstalled VLC. Hopefully that fixes it, I'll update if it does.
edit: it lasted overnight without crashing! yay! uninstalling VLC and setting big box to use WMP