Jump to content
LaunchBox Community Forums

C-Beats

Administrators
  • Posts

    5,220
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by C-Beats

  1. Feel free to discuss it, just please do so in another thread.
  2. Another option would be to install a clean version of MAME, then add that clean version as a new emulator in LB and point to that when importing. Then after the ROMs are imported change the Arcade platform default emulator to the one you are using now and it will update the games to use it. Not ideal, but I don't know what it takes to disable the devreorder and how that burden compares.
  3. You can create a Platform Category and place playlists in those, as well as nest them to give you the ability to do what you ultimately want. Then in Big Box instead of opening to Platform view you would use Platform Category view.
  4. At this point I'm not sure the best way to proceed. You could potential create the xml file yourself that we parse and make sure it outputs correctly but I sincerely doubt that the official build has any problems doing so. To dump the XML file simply run the command line: mame -listxml > listdump.xml
  5. Ah ok. Thanks for the clarification.
  6. @bbweiners I'm not having that problem on my end, but I admit we have had several corrections to the code since the beta 6 release. @Jason Carr plans on releasing another beta today. Would it be possible for you to verify you still have the issue after that is released? Also just so I can confirm, is this happening to you while using WMP or VLC as your video backend (or both)?
  7. @Kiinkyfoxx Believe the executable should be a mame64.exe not mame.exe. Basically we are doing a command line call against that application and it reads like the XML file isn't formatted correctly when it gets it. Only time I've seen that happen is on unofficial MAME executables (though I admit I am not as well versed as most on this forums in regard to MAME).
  8. Do you still have GameDetails turned off when you see this happening?
  9. @RULLUR @Olivia232425 Did the errors you were reporting get resolved in this last push?
  10. @bbweiners Could you elaborate a bit about the animation thing you are reporting? Want to make sure I understand what is going on.
  11. @Hifihedgehog some of the features in that video are possible in this beta. Things like the grid where the video play after mouse over (see Default Theme - Wall View 2) are working in this beta.
  12. I would do the following: 1) Turn on debug logging it not on already 2) In the import screen when asked what emulator to use make sure the emulator you are picking is pointing to the right MAME file 3) Run the import again. 4) If the import fails go to \\LaunchBox\Logs\ and open the most recent log and see if there is any more details to the error in that file
  13. What version of MAME are you running? @Kiinkyfoxx
  14. The process been updated in the most recent beta release and should make logging into Epic far easier. You can also log out of Epic should you need to as well.
  15. Not with the default theme, no. If you are a premium user you could use a theme that does something like that though.
  16. Check to see if there is a installer sitting in your \\LaunchBox\Updates folder
  17. Code is in the latest beta release (11.10 beta 6) you can opt in to beta builds via the Options menu inside of LaunchBox.
  18. There probably won't be a tutorial made, but I do plan on updating the documentation we have to explain what all the controls/bindings are
  19. I use MAME but to do so in MAME you have to configure the controller as Player 2 controls as well, would imagine have to do the same in RetroArch. You can't join as player 2 and then use Player 1 controls to do the things so you have to bind the same controller to both players then just something different for player 2 coin/start than you do for player 1
  20. I believe I have found a way to get a easier to use SSO form to appear for the login screen. I have code committed and will comment on the thread when it is in a public build for you all to try.
  21. We have the IGameLaunchingPlugin interface that would tell you when a game closed. Wouldn't work for alt tab situations though. Could try subscribing to the Application.Current.MainWindow.Deactivated event to do it. I've not personally tried it so you will need to test it before releasing anything.
  22. The new one is called FlowVideo, if you have the beta you can see it in uses in WallView2.
  23. It's because most themes that play video use our ImageVideoView or VideoControl which Big Box then tells to pause when it loses focus. Looks like you are using a plugin in your theme and so it doesn't get told to pause the video.
  24. Yeah. Not trying to say those builds don't exist AT ALL. For the type of build you are referring to (VPIN) I can see it being more popular. Though what you are referring to now has very little to do with what the OP was originally referring to.
  25. Built into WPF theming, no need for a plugin, beta has a new video control we implemented that could make this even easier as well.
×
×
  • Create New...