Arcade1993
-
Posts
68 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by Arcade1993
-
Anyone? Please?
-
You have to add LEDBlinky to the startup folder for it to load automatically. When I removed LEDBlinky, I also removed its entry in my startup folder.
-
Yep, I mentioned earlier in the thread that getting rid of LEDBlinky made no difference. Basically LaunchBox refuses to load the game properly after a reboot. It will eventually load it, but after a really long wait. And if someone presses a button either on purpose or by accident while it is trying to load MAME, LaunchBox will try to load the ROM again, each time the button is pressed. Then the cabinet is trying to load a bunch of MAME instances at once, which makes everything go insane. This does not happen again after the first time it happens. It's always only after the first boot.
-
I don't remember saying I had VLC issues, haha My issue is that the first time I load any game, LaunchBox starts LEDBlinky and MAME refuses to load the first game unless I sit there and wait for 2 minutes. If I press any button on the cabinet, instead of skipping the button instructions and starting the game, LEDBlinky just keeps repeating itself, and eventually MAME tries to open like half a dozen instances of MAME, making the computer completely lock up for 2-3 minutes. When I exit out of everything and try again, everything works fine. But this is obviously not an enjoyable experience for a MAME cabinet to have to do this every time I turn it on. Thinking it could be a Windows 10 issue, I completely wiped Windows 10, and reinstalled a bare-bones issue called Win 10 LTSB that has zero bloat (and is on a very old version of the OS, so the blame can't be put on a Windows update.). When that didn't work, I spent $200 and put all of my ROMs on an SSD because I figured maybe my spinny hard drive was getting slower with age. Unfortunately this too did not work. Here is the video of what happens so it makes more sense:
-
Anyone?
-
OK so I can with 100% confidence say it's something with launchbox and MAME. I got rid of my spinny HDD and bought a 2TB SSD (not cheap!) I reinstalled an old version of Windows 10; a 2016 release that is LTSB meant for things like ATMs and such, and it has absolutely zero bloat. It doesn't even come with the Edge browser. After all that, and setting EVERYTHING up all over again (took FOREVER), I still have the issue. There is no way it's anything I am doing and this is really starting to make me give up on this whole thing. Is it MAME? Is it Launchbox? Is it the way BigBox is launching MAME?
-
I appreciate that, however I am using the same drive I have always been using and never had an issue before.
-
So I did a bit of research on this. It appears a LOT of people have this issue with either the 1803 or 1809 update to Windows 10. Unfortunately I see no way to downgrade to 17XX without losing all of my settings/reinstalling an old Windows 10 disc. Some people said that they fixed it by turning off a feature that has to do with not allowing notifications to interrupt a game window (a new "focusing" feature). Unfortunately turning that off did nothing for me. Is there anything else I can try? Any way to get back to 17XX without losing all of my setting?
-
Thanks, yeah I did update Windows 10. I tried to uninstall all the updates but it only let me go back so far. What is needed for a full reinstall on MAME? Kind of a confusing verbiage only because MAME just kind of gets extracted to a folder.
-
I am just so glad to see it's not just me. Thank you so much for checking it out for me. I tried the latest version of LaunchBox, as well as the latest 8.X release. I checked to see in task manager if any high CPU or RAM usage was going on during this time, but nothing was. I did not use any system logs, though. What do you think the culprit is, since you have the same issue as me? LaunchBox, or is MAME to blame? Or both? Thanks again so much.
-
Thanks for the reply. It happens with any ROM. It could be Pac-man, it does not matter. The lockup *always* happens if I try to load a game within a few minutes of Windows 10 booting up. After the first round of it locking up, it will always work fine. However, this is not a good solution because the entire reason I bought an SSD and Windows 10 was for the incredibly fast boot-up time. Adding an extra 5-10 minutes is not really acceptable. Especially because there's no way if my kids go to play it that I am going to have them hook up a keyboard to force close LaunchBox and MAME every single time. Also, force closing takes forever to work. It takes a good minute of waiting just to show the desktop when I press Win+D or CTRL ALT DEL. It is completely unresponsive this entire time. Any help would be incredibly appreciated!
-
Oh and I want to make it clear that LEDBlinky was not the problem.
-
I greatly appreciate that. And yeah, updating MAME and the ROMset is such an aggravating process that I too only do it maybe once per year.
-
I am going to sound like such an idiot but I have no idea how to do that (and I am pretty good with computers). I mean I can find the command prompt I need to run MAME and load Killer Instinct but I have no clue how to tell it to use LEDBlinky as LEDBlinky is set up to use Big Box.
-
Thanks but I have determined the issue is not LEDBlinky by renaming the LEDBlinky.exe to LEDBlinky2.exe so it would not load up. Unfortunately, MAME has a huge issue loading with BigBox still. Basically when I first go to a game after BigBox starts, the game refuses to start. I can hit enter in Big Box 5 times and nothing will happen. Then like a minute later it tries to open like 5 instances of MAME (one for every time I pressed it) which completely screws my computer up to the point where pressing WIN+D won't even give me my desktop. I have to wait a while (about 2-3 minutes) before everything will finally close. Then when I start BigBox up again and select a game, the issue goes away. But this is a very big issue to be dealing with. None of my kids or tech-unsavvy friends are ever going to want to play this thing like that. I thought it could be that maybe some weird process was starting with my computer that was revving my CPU up to 100% or something, but I checked task manager and the CPU never went over 12%. BigBox seemed to use a LOT of RAM (800 MB when I checked, which seems like a lot since I have the least-flashy setup possible), but I have 12GB of RAM regardless. I have no idea what else I can try here. I can start a new thread if I got too off the original topic since I now know LEDBlinky is not to blame. Also remember that I did nothing to this computer besides update MAME and BigBox at the same time. I didn't install anything new. My cabinet isn't even connected to the internet. So I have no clue what is going on.
-
Did you mean the mame.ini file?
-
OK so I ran it again after deleting the VLC folder and those pop-up errors disappeared. However, I am still having the LEDBlinky issue. I think it might have something to do with how LaunchBox talks to MAME in the MAME versions released in the past 6 months or so. All these issues started creeping up when I updated MAME. I had no idea how MAME could effect any of this but apparently it is because I am using the same LEDBlinky version, and now verified that the older LaunchBox still gives me issues. The MAME version before the latest I noticed I had an issue where a lot of times my MAME games would not boot full screen. This happened right after I updated MAME. I didn't think of it until now. Is there something new in MAME since, around mid summer last year or so, that would affect the way it talks to LaunchBox and/or LEDBlinky?
-
OK I installed version 8.9 but I get these two errors upon launching (not sure if it's related) and then Big Box opens and just freezes when it opens and refuses to do anything. Yeah I am on the latest MAME and the latest LEDBlinky
-
I made a video of the issue:
-
Thanks for the reply! Unfortunately this did not fix anything. I did notice an oddity with 9.x that also might shed light onto it. In 8.X and lower, I would select my game, it would say out loud "Street Fighter 2" and then would start blinking the buttons and telling me what each button does (via LEDBlinky). In 8.x if I pressed any button it would stop the voice announcement of the buttons and would then proceed to load the game. That no longer happens in 9.X. If I press a button to skip it, it just keeps repeating the buttons over and over, every time I press. When the game finally loads, it tries to load a ton of MAME.EXE processes. So If I tried to skip it 3 times, it will load up 3 instances of MAME. Did 9.x change the way it handles LEDBlinky or something? To tell you the truth I am not even sure it's related, but it's something that also happens randomly. Sometimes it loads the game properly and lets me skip the instructions as well!
-
Hello! I've been using LaunchBox for about 2 years now, ever since I finished my MAME cabinet. I never had an issue until the 9.x update. I am currently on the latest version. I am running MAME 0.203. Ever since updating, I always have an issue launching my first game. For example, I'll click on Street Fighter 2 in Big Box mode. 9 times out of 10 it will start correctly flashing the buttons and speak its commands (LEDBlinky) and everything will go well. But then the game will never start. I will either get a black screen, or it will get stuck at the first screen where MAME tells you the info like screen res and such. I always have to force close Big Box and then start it up again, and then everything works fine. Obviously this is a pretty big issue because my young children want to play it sometimes when I am not home and it's not easy explaining to them or my wife how to force close a program and then open it again, especially with arcade controls. Does anybody know what changed from 8.x to 9.x that is causing this? I doubt it's my computer as it's an i7 @ 4.0ghz with 12GB of RAM and an SSD. And this issue did not exist with 8.X for me. I disabled "show loading screen" but that didn't seem to fix it. I even have issues sometimes when I exit games, where I exit and it takes forever and I have to force exit (kill Big Box then open it again), though this exiting issue is a lot less common than the startup one. I am running Windows 10 Pro. Any info would be greatly appreciated!
-
Thanks so much. I have been messing with every setting under the sun but I cannot make 320x240 look good for some reason. It has weird lines everywhere and the picture is a mess. Is there something I am doing wrong? I even set the NAOMI BIOS to 15khz.
-
Thanks so much for all the helpful and reassuring replies!
-
This is a new one for me. I was on Launchbox 7.x (lifetime purchase version) and changed the checkbox to allow for beta releases to get in on 8.0. It downloaded and installed, but right after the install, some sort of UAC prompt popped up and I cancelled it by accident. It was so fast that I didn't even see what the prompt was. I kept exiting launchbox and restarting it trying to get it to pop up again but it wouldn't, so it must have been something related to the install. Does anybody know what that could have possibly been? Launchbox 8.0 seems to be working fine but obviously something wasn't installed that should have been and I am trying to figure out what I am missing
-
Thank you. I feel embarrassed I have to ask this but did you both mean tinkering with the actual driver itself? Or some sort of setting in DEMul?
