blurt92
-
Posts
10 -
Joined
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by blurt92
-
-
I tried for months to figure this out myself and finally figured out it was a random video file during attract mode that was causing it to crash. It didn't matter if I used VLC or WMP. I happened to get lucky and was looking at the screen when it crashed. I'd start by narrowing attract mode down to one system and see if it still happens. If it doesn't, go on to another system and repeat until it does crash.
-
You're right, windowed mode didn't help. When I tested it last night I didn't realize it was loading the rom from scratch (I have autosave on) after I changed it to windowed mode. The rom's sounds hadn't started yet.
I ended up finding the Wootlauncher plugin and the pause function is working exactly how I want with the added benefit of actually stating the controls through LEDBlinky. Launchbox' pause screen wouldn't do that as it doesn't appear the keystroke was sent to Mame prior to suspending it.
Bottom line, the combination of your batch file suggestion and Wootlauncher solved my dilemma. Thanks again!
-
Actually, the Pause screen won't work at all using the batch file as it goes back to the main menu after hitting "Resume Game" and Mame continues to play in the background. It went back to working when I changed it back to Mame64.exe instead of mame64.bat. @Headrush69 You mentioned borderless windowed mode, are you able to offer any help on that? I've searched and can't seem to find a way to do it in Mame. When I launch it in regular windowed mode it works but I have the ugly windows boarder up top.
-
8 hours ago, blurt92 said:
One downside of this is that the Pause Screen no longer works properly. Am I correct in assuming that it's trying to suspend "mame64.bat" instead of the actual executable? My work around is changing the pause key in Mame to something other than 'P' and pressing that first prior to loading up the pause screen by pressing 'P'.
-
52 minutes ago, Headrush69 said:
As soon as LB shows the Startup screen, LEDBlinky begins speaking the controls. I don't know your system specs or if possibly you have debugging enabled on LEDBlinky, but I don't think it waits until the startup screen is done.
One issue is if MAME is used in full screen mode, no matter what delay you set in LB, it will switch to the MAME once it takes control. There is no way around that unless you want to run in borderless window mode.
RocketLauncher tends to run a lot of emulators in this mode, so without looking at the module, it's likely why it can keeps it's loading screen up and waits for the completion of LEDBlinky as well.
As a simple workaround, you could make a mame.bat file in your MAME directory with the following:
Set this as your mame executable in LB and it will pause 10 seconds or until you press a key while LedBlinky does it's thing. You can change the 10 to whatever number of seconds you need.
Brilliant! Thank you so much, this does exactly what I was hoping.
-
Just now, Headrush69 said:
Can you explain this a little clearer? Can you list some specific roms where this happens?
It appears LB sends the message to LEDBlinky before calling MAME, so if you have a game with lots of controls for LEDBlinky to speak, and it's a game that loads fast in MAME, it might be a a delay you want.
It happens with every rom whether they have many different controls to announce (MK2, SF2) or just a couple (Galaga, DK, Pacman). LedBlinky doesn't start speaking until after the game startup screen is done and Mame launches. In RocketLauncher it announces the controls while it loads.
I've tried changing the startup screen display time and that doesn't have any effect, it just waits until the game starts and then starts talking over it.
-
I was mainly using it for the loading and pause screens and having one less piece of software to tweak and troubleshoot would just make things easier.
-
Is there anyway to have LedBlinky announce the controls during the Big Box game startup screen? I used to use RocketLauncher's fade in and that worked great but trying to get away from RL if at all possible. Right now, it starts to announce it as soon as the game starts in Mame and tends to get muffled by the game's own sound.
Also, anyone have any ideas on how to get LedBlinky to announce the controls when using Big Box pause screens with Mame?
-
On 7/11/2019 at 1:57 PM, JedExodus said:
If anyone cares I'm very close to what I consider a SEAMLESS Wiimote experience...
- Control everything with Wii Remote
- Full use of BigBox frontend with Wii Remote. Launch your games and shutdown your system with the remote
- Switch between MAME Lightgun games and Dolphin seamlessly
- Touchmote closes down for use in Dolphin then restarts to use LaunchBox again
and most excitingly in my opinion....
- Close Dolphin with Wii Remote from the Wii Home Menu. No need to grab Keyboard to hit ESC or a controller with a HotKey
What's holding the whole thing up is... I cannot get the Wii Remotes to reliably behave when launching Touchmote on startup. 4/5 times they'll be grand. But the fifth time even though I have IR mapped to analog stick, it'll control the mouse, on turning off the Wii Remote the cursor will pull to one side. If anyone knows how to fix this please please let me know. I have tried WiinUSoft but it has it's only particular issues on startup and with retaining the analog stick settings in my experience.
Regardless I'll release what I have some point soon. FYI I have no idea what i'm doing and it's gonna be messy and hacky, but it should work. If someone wants to help me tidying it up that'd be great. Just please don't be a tosser about my implementation
Any update on this?
Bigbox randomly exiting to desktop
in Troubleshooting
Posted
It was just corrupt on my end. I redownloaded it and it worked fine after that.