Jump to content
LaunchBox Community Forums

C-Beats

Administrators
  • Posts

    4,496
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by C-Beats

  1. Check to see if there is a installer sitting in your \\LaunchBox\Updates folder
  2. 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.
  3. 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
  4. 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
  5. 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.
  6. 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.
  7. The new one is called FlowVideo, if you have the beta you can see it in uses in WallView2.
  8. 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.
  9. 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.
  10. 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.
  11. All those things would be displayed by your pinball app, not Big Box so not sure there'd be much point in adding extra monitors for those type of set ups. That being said if you are using LEDBlinky with a LED DMD you can technically already have 3 of the 4 things you just mentioned in Big Box now. Playfield would be primary monitor, LEDBlinky control the DMD, and backglass could be set up as marquee monitor.
  12. It's something you turn on in the options page of LaunchBox
  13. All of the features you are wanting to use in your theme are in the current beta release and use new property bindings to work. Everything you asked IS possible in Beta. Most of which has been revealed how in the beta testing thread. If wanting to pursue this path and are ok with XAML, I would grab the beta version and take a look at the new WallView's used in the beta and see if you can use them to guide you to what you want to build.
  14. Unsure what support you feel is missing. What exactly are you hoping for that can't already be done with the marquee?
  15. Only one Manual Path can be set per game. You CAN however add PDFs as Additional Apps to access them via LaunchBox and Big Box though
  16. Ironically went to test the work around and "failed" their new captcha challenge....
  17. We have code that clears cookie's related to Origin for this purpose. Epic at the time of integration didn't save cookies in any meaningful way that this was a problem when we first implemented it. I would assume some of the code on their servers have changed a bit and is causing the issues. I will look into adding an option to force login during import, or add something in options like we do with Origin. I'll see if I can get a work around figured out for you in the meantime.
  18. That captcha was pretty troublesome when testing the implement as well. Unfortunately that is all coming from Epic and we have no way of bypassing it. I recently had to change my password and login the actual Epic Game Library app again and had the same annoying things in their own app.
  19. Text is always done pretty immediate. FlowImages follow the following process "flow": Check if image cached, if not build cache item, load cache. If it has to build the cache item the load process can take a second to complete. If you entering a platform that doesn't have ANY cache items it can take a bit for the cache process to cache everything and load it. The other views did NOT have the same dispose logic in them as WallView which could have affected memory usage. That has been corrected for the next release.
  20. Nice catch. Was able to replicate and will get it taken care of.
  21. Thanks for this. I was able to replicate and will get a fix put in for it.
  22. Currently no. In the next release we have a new CoverFlow Theme Devs can use that would make it possible to do it, but there is no option you can set inside of BigBox to make the view behave that way.
  23. Did you get a hard crash with error report? If so is there anyway you could try to replicate and post the error you are seeing? Also what theme / view were you using when you had the issue?
  24. It won't get reset on start up, but any update WILL overwrite that file. Neil is correct that using a standalone in a separate folder as the emulator for your videos would work best.
  25. FlowVideo has a "StretchVideo" property that should make it fill the space it covers
×
×
  • Create New...