Jason Carr

In the emulator settings in LaunchBox for ePSXe, there's a forceful activation option under the pause screens tab.

@MazJohn [Mr Arcade] Thanks for posting here. I do have a few questions for you: Have you tried disabling pause screens to see if it fixes the issue? Have you tried disabling startup screens to see if it fixes the issue? What hotkey are you using to exit? Are you using anything other than LaunchBox/Big Box to make it work?

For those of you with this issue, all that is necessary is to modify the emulator command-line options to remove "-keyboardprovider dinput". Upgrading is a better solution (of course), but if you'd rather not go through with it, you really don't have to.

Yeah, that does seem at least possibly feasible, but I think the first priority would be to support multiple save states. Until we can support multiple save states, there's really not much use for screenshots. I'll put it on the list though.

Probably not unfortunately. It would have to be implemented differently for every single emulator, and probably wouldn't be possible for most of them.

LaunchBox will pick up images that match the ROM name, so you should be able to just name the file 1941.png or 1941.jpg.

Apologies @radicalblues, I never saw this thread when it was created. Unfortunately it's difficult to see every single thread. The issue is that star ratings were added well before we opened them up to partial stars, and the old property is still there for compatibility's sake. It should work if theme developers bind to StarRatingFloat instead of StarRating. However, when images are used in custom themes for the stars, depending on the method used to display them, partial stars may not be supported by the theme (I've seen several different methods of converting the numeric value into the visual representation of the stars, and not all of them will work with partial stars). So it's really a custom theme issue, and depends on using the correct code for displaying the stars in the theme. To be honest, though, I haven't checked the default theme to see what it's doing, either.

I have noticed that Windows has issues if you change the DPI and don't reboot, or at least log out. So that may be the reason; you may just need to reboot. Other than that, the only other issues I'm aware of are related to dual-monitor setups with different DPIs on each monitor; Windows still has issues dealing with that, so that's not really a recommended scenario. Beyond that, idk, maybe it could be a driver issue?

Alright, I updated the first post of this thread. There's a new Google Sheets document with the previous grid and now scripts as well: https://docs.google.com/spreadsheets/d/1wuGiwg8I5QqulDncQvGBZP83BVDSXpbSOzdYqDrsCxI/edit?usp=sharing We'll work through getting the script contributions from this thread in there, and as we get more scripts and testing details, the moderators and myself have access to updating the document, so we'll get it updated as we go.

Thanks; updated the grid. I'm thinking we might create a new thread here soon to keep track of scripts as well.

Lol...yes. There are no issues here at all. Just edit the emulator settings. I don't really understand why this thread got quite so out of hand, but I'm glad it's all figured out.

Well now I feel like a mean parent.

Let's not throw shade...drama isn't helpful here.

Yes, LaunchBox and Big Box have separate settings for all of that stuff. Some people only want to use it all in Big Box.

We've had lots of beta testers testing it with many versions of Retroarch, including 1.7.7. Whatever is going on must be some kind of weird system-specific issue. Somehow the pause function isn't even being triggered. Have you tried other emulators? I would look for anything custom you have in your setup that isn't typical to try and narrow it down.

Yes, try that, and try setting the pause key in LaunchBox to a key that is not bound in Retroarch.

I guess we didn't see that one coming. Regardless, I don't expect many people will run into the issue, because that's a pretty old version of MAME. As long as you can get around it, we probably won't be changing anything, as we don't currently have anything in place to check the MAME version. Good to know though.

Nope! I'll get this in before the official release today. Thanks @alexposad.

Awesome! Welcome and thank you very much. We haven't heard back from @Wutex in a very long time, so I don't think he's working on it, and we definitely could use a Japanese translator. You can read the first two posts of this thread for details on how everything works, and download the translation files there. Let me know if you have any questions. Just make sure you understand the first couple of posts because there are a few gotchas. Thanks @k_kutsugi!

Beta 18 is out now with just some translation updates. The plan is to release the official version tomorrow morning. If anyone knows of any remaining bugs (outside of known emulator compatibility issues), please let me know.

Thanks for all that @sundogak.

Basically it's used for keyboard mappings. You can press a key to bind the mapping or wait five seconds to clear it out. Thank you all very much; I have all the translations updated for the next beta. Planning on putting out the official release tomorrow.

Beta 17 is here with just some minor updates: Updated translations Emulators no longer require the exact name for scripts to populate (now uses a Contains search)

Thank you Kondorito; all updated for the next beta.

What displays there is game fanart backgrounds, or platform fanart backgrounds if game fanart is not available. You can tweak the background priority settings in LaunchBox (uncheck them all) and then it will only use platform backgrounds if you want.