Jump to content
LaunchBox Community Forums

eatkinola

Members
  • Content Count

    748
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by eatkinola

  1. All the plugin does is convert a platform, playlist, or category name to a SolidColorBrush. I'll need to update it to work for games views, but that should be easy.
  2. @viking You could try tinting an image of white stars like this. I used this tinting approach in Minimal-AO: https://stackoverflow.com/questions/28247010/tint-a-partially-transparent-image-in-wpf That should work, and you should also be able to use it with the platform to color converter I provided you.
  3. Glad you like the theme. For the fade-ins to work as in the video (in theme description above), you'll need to also use my WootLauncher plugin for LB/BB. Please note WL is not compatible with BB's built-in startup and pause screens; you'll have to deactivate those. Also, in the video it looks even more integrated because I use the same bezels in FluxCRT for retroarch cores. https://forums.launchbox-app.com/files/file/1619-wootlauncher/ I noticed you sent me a pm; we can work on this issue there.
  4. You don't have to scrap anything -- you can setup RetroArch as another emulator and just point LB to it while testing to see if you like it. That being said, RetroArch is not good for Dolphin and only so-so for Atomiswave/DC (the reicast core is coming along nicely). RetroArch works very well for a bunch of other systems such as NES, SNES, Genesis, GB, Atari, etc. (a very long list). The systems for which I personally let WL do the bezels include: GameCube, PS2, and demul stuff (though I'm moving over to RA's reicast core). You shouldn't have to do much for setup, but yes it does need to map emu/platform names at some point, e.g., Nintendo GameCube > DOLPHIN@GAMECUBE, to match how the overlay images are named. Caveat: this is off the top of my head -- I can provide more help when back home later. There should be a file in the Config subdirectory of WootLauncher (these files self deploy when you first use the plugin) that has this mapping. The WL download does not include bezels for NES etc. since RA does such a great job w/bezels, though WL could of course apply its own overlay for NES games if one wanted it to.
  5. Yeah -- I totally get that ... one of the reasons I made this plugin; empty spaces of the black bars really bothers me, and stretching games to fill the screen looks funny. I use RetroArch for most systems, and its overlay system works well once setup.
  6. You can certainly try it (enabling only the overlay function of WL), but I don't think it will work and will have to be all or nothing. WootLauncher and the built-in startup/pause screens work differently. Like RocketLauncher, WL needs to capture the emulator window so it can apply an overlay.
  7. @Wonderwhy: You might consider setting up Syncthing to do this. I use it to sync my libraries between Windows and Linux (NAS/backup) devices, and I think there's also a client for android. Just a thought ... I think it's easy to use. Syncthing is mentioned in another thread, and I don't want to hijack this one just thought I'd mention it. Here's the thread: https://forums.launchbox-app.com/topic/50502-does-anyone-have-a-method-for-keeping-their-save-states-updated-across-multiple-computers/?tab=comments#comment-324017
  8. Nice to hear it's working well. That's a great catch with the SEGA_GAME_GEAR; I'll fix that for the next release. I'll check out the video positioning issue. FYI, the ALL CAPS naming convention (e.g., AMIGA_CD32) is something I use internally to get things to match up -- this is how the files and images in AVLF are named. There is a mapping in Plugins \ Ao.Bigbox.Themer.v3.9.6.dll.config that defines how to get from user-defined names to my standardized name. The files in Nostalgia \ Images \ Platforms do not employ this mapping and must be renamed manually to match how you name the platforms. P.s. I fixed the Amiga naming for the next release, too. Thanks again!
  9. For the most part, you should be able to edit the section where the FontFamily resources are defined. That section in PlatformWheel3FiltersView looks like this: ... <!-- FONTS DECLARED HERE BECAUSE DOES NOT SEEM TO WORK FROM WITHIN NOSTALGIA.XAML --> <FontFamily x:Key="NostClockFontFamily">/Ao.Bigbox.Themes.Nostalgia;Component/Fonts/#Arcade</FontFamily> <FontFamily x:Key="NostLoadingFontFamily">/Ao.Bigbox.Themes.Nostalgia;Component/Fonts/#Arcade</FontFamily> <FontFamily x:Key="NostVertYearFontFamily">/Ao.Bigbox.Themes.Nostalgia;Component/Fonts/#Neon Pixel-7</FontFamily> <FontFamily x:Key="NostWheelShadowListFontFamily">/Ao.Bigbox.Themes.Nostalgia;Component/Fonts/#Bebas Neue</FontFamily> ... These references pull fonts from the Nostalgia DLL, but you could also pull a font installed on your system. There is a new(-ish) way to use fonts in BB themes without installing them on your system, but I've not used that approach so cannot comment on it. When editing the fonts above, you'll need to leave the key name alone; just change the content of the FontFamily tag, e.g.: ... <FontFamily x:Key="NostClockFontFamily">SomeFontInstalledOnMySystem</FontFamily> ... Changing fonts for certain view items (e.g., most of the lists) might change spacing a little and therefore mess with the layout. When I use lists in my views, for example, I space items so that none are cut off on the top or bottom of this list when scrolling since that irks me.
  10. UPDATED to v6.0 -- support for LB10+ (now requires 10+)
  11. UPDATED to v1.6 -- support for LB10+ (now requires 10+)
  12. UPDATED to v1.7 -- support for LB10+ (now requires 10+)
  13. UPDATED to v2.0 -- support for LB10+ (now requires 10+) ... Turned off by default is when then selection wheel fades to platform/game details. You can turn this back on if you want by quickly editing Views\Styles\Nostalgia.xaml ... near the top of the file, and the bundled PDF describes what to change. @Guidope
  14. @bundangdon, @neil9000 -- updated to support LB10+ ... Turned off by default is when then selection wheel fades to platform/game details. You can turn this back on if you want by quickly editing Views\Styles\Nostalgia.xaml ... near the top of the file, and the bundled PDF describes what to change.
  15. Thanks, Guidope. I had to update it to support LB 10+. I'm almost done and hope to post an updated Nostalgia this weekend.
  16. If you want to pm me the current version of your theme I can take a look. Or you can pm just the xaml file in question.
  17. Yes, that was the right thing to do to match the version of the DLL you have. 3.9.6 is my current development version for LB 10+; 3.9.4 should work for LB 9.10. I'm not sure why you're getting that error. While I use visual studio to develop the plugin, I don't actually use it to work on themes; I just use notepad for that. Does the theme work despite this error in VS, e.g., perhaps you could ignore the error? The syntax looks correct to me.
  18. Try this -- been awhile since I tested this myself but it should still work. Please note since Ao.Bigbox.Themer depends on LB libs, it's updated every now and then to work with LB updates (only needs to be done when the LB libs change significantly). The current version of Ao.Bigbox.Themer works with LB 9.10+, and I have a new version ready to upload once LB 10 is released. For updates, you would need to change the part of the xmlns string (see below) that refers to the Ao.Bigbox.Themer version. ...add this reference at the top of the XAML xmlns:aov="clr-namespace:Ao.Bigbox.ViewModels;assembly=Ao.Bigbox.Themer.v3_9_6" ...SelectionSnoopVMP object gathers the data <aov:SelectionSnoopVMP x:Name="SelectionSnoop" /> ...display properties from SelectionSnoop, e.g. <TextBlock Text="{Binding ActiveGameCustomFields[MyCustomFieldFoo], ElementName=SelectionSnoop}" /> <TextBlock Text="{Binding ActiveGameCustomFields[MyCustomFieldBar], ElementName=SelectionSnoop}" /> <TextBlock Text="{Binding ActiveGameCustomFields[MyCustomFieldBaz], ElementName=SelectionSnoop}" /> <TextBlock Text="{Binding ActiveGame.Title, ElementName=SelectionSnoop}" /> ... Hope you find this helpful -- let me know if you run into any snags.
  19. The About page is about the program and developer. It's totally appropriate for Jason to have that content there. Ok I really didn't want to comment on this issue, but people just need to be more accepting of one another, and we all have the ability and personal obligation to filter out from the world what is important to us.
  20. Thanks @Tony for the troubleshooting efforts. To others reading this, bear in mind switching to VLC in my themes (i.e., using the Ao.Bigbox.Themer plugin) might lead to instability; it may work, it may not depending on the videos. That's why my themes force WMP by default. In my experience, WMP runs smoothly and efficiently. WMP does not support as many codecs out the box as VLC, which can be an issue for some users; depending on how you source your videos. I've had great experience with emumovie vids.
  21. Just in case it's a theme issue, could you try using LB with the default theme and see if you still get this error?
  22. Thanks for the info. Pardon all these questions -- just trying to narrow it down a bit more. Was it working before you upgraded LB or the theme? Does it only occur for games where you use theme videos? Anything else the games for which videos do not play have in common? Does it show something besides the video, e.g., screenshots, or just the tv-static video? Also, if you want to pm me a few of the videos that aren't playing that might help, though I assume you're using the same videos as me from emumovies (?).
  23. Thank you. I already have shaders configured per core and sometimes per game, using video_shader. I just need to figure out how to convert these cfg files to work with the new shader system, since video_shader is no longer a valid cfg parameter.
  24. 1.7.8 changed the way it handles shaders, and video_shader is no longer a recognized option in cfg files. I've not yet figured out how to use the new shader stuff, so guess I'll stick with 1.7.7. It's a real bummer they removed this option.
  25. At least the notifications seem to be popping up over the bezels now -- that bothered me about 1.7.7 (they were half hidden behind the bezels) and looks like a step in the right direction. I think the new notification framework is pretty recent, so hopefully they will continue refining it.
×
×
  • Create New...