eatkinola

UPDATED to v1.7 -- support for LB10+ (now requires 10+)

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

Thanks, Guidope. I had to update it to support LB 10+. I'm almost done and hope to post an updated Nostalgia this weekend.

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.

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.

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.

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.

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.

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?

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 (?).

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.

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.

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.

After cropping those pngs, you'd need to adjust the @INDEX files in the AVLF subfolder to correctly position the videos. Then (and this is probably the hardest part), you'd need to edit each view's xaml file to adjust the layout. You'd probably also need to scrap some design elements in the process to make things fit. It could be done but will take a good bit of work.

I'm in the bezel camp and prefer aesthetics over authenticity. You can use RA per-game overrides as needed for games with black bars. It's a bit of a pain to setup, but once it's done it's done. It'll obviously be more of a pain to setup if you have a complete collection of a26 games; my collection is limited to about 90 games. Per-core override STELLA.cfg: Per-game override Barnstorming.cfg: Nevermind the moire effect -- that's just how the screenshots come out when using the shader: P.s. Oh man I'm rusty at this game

Just cleaning out my inbox ... took awhile to sort these memory leaks, but it should be fixed now. https://forums.launchbox-app.com/files/file/1259-rξfδktφr/ The current version of Refaktor supports the current release of LB/BB. Once Jason releases 10, I'll post a theme update that supports it.

Interesting -- I suspect without DS4Windows the DS4 is used via dinput ... maybe that's why the difference? I'm using the newer forked version by ryochan

Yes I have. I've not run into that problem, though I did not specifically try mapping the R2 and L2 buttons in BB. One issue I had early on with DS4Windows was that it would result in two controllers being available for every DS4 plugged in -- you can prevent this by using the "Hide DS4 Controller" option under the Settings tab in DS4Windows. P.s. Just confirmed I also cannot map the R2 and L2 (trigger) buttons in BB, but the R1 and L1 (shoulder) buttons work fine. I never noticed this before, but it doesn't bother me anyway. I wonder if this is something @Jason Carr could handle in his xinput interface for gamepads? P.p.s. I don't have a real Xbox controller (only the emulated one whereby DS4Windows turns my DS4 into an "Xbox Controller". I wonder if a real Xbox controller's L2/R2 or "trigger" buttons work in BB.

Updated to v1.5.1 -- see download page for details https://forums.launchbox-app.com/files/file/1619-wootlauncher/

Glad you like the theme, @Guidope. It's designed for 16:9 screens and won't look as intended at 4:3. However, you could allow it to stretch and fill a 4:3 screen. Look in the ThemeSettings.xml in the root of the theme's folder. There should be a tag called Force16x9... set to true -- set this instead to false, and it should then allow stretching to 4:3. <Force16X9AspectRatio>true</Force16X9AspectRatio> ...change to false The "inception" look will always happen if you use viking's videos, as I used his videos to make the backgrounds with screen cutouts. While Nostalgia is one of my favorite themes, not that I'm biased :), you might want to look into a 4x3 theme for your cabinet. There are a few out there. Another theme I created called Refaktor should work well for either 4x3 or 16x9. https://forums.launchbox-app.com/files/file/1259-rξfδktφr/

Just make sure there is always a computer running that has the most recent sync and you should be fine. For example, I run syncthing on my NAS which is always on (FreeNAS which runs on freebsd). You can install syncthing on a variety of platforms; even a raspberry pi if you wanted to make a simple low-power server.

DualShock4 for everything emulated in RA -- I like the grips, layout, and the d-pad. Agree with monkus on the very low latency. DS4 will work out-the-box with Windows, but I find it's a much better experience when used with DS4Windows (which essentially turns it into an Xbox controller as far as Windows is concerned). When used with DS4Windows, connects and disconnects when turning the controller on and off are handled much better, and DS4Windows also modulates the DS4 light to show battery status.

Regarding LB folders, I ended up syncing Data (excluding LaunchBox and BigBoxSettings), Backups, Images, Manuals, Music, and Videos. I've pretty much got LB setup the way I want, but inevitably I'll add or edit something and only want to have to do this once. Syncthing lets you exclude subfolders or files pretty easily, so you can sync Data with a few exclusions, for example. Glad it's working out for you. Yes, that made me a little nervous at first because of the time it took to curate games, metadata, and media -- didn't want to see all that work get blown away by a program. Just in case, I made a zipped backup of my LaunchBox install, though I'll probably never need this backup zip. One other tip (?) -- I put everything I want to sync into one folder I call "Emucloud", and LB or emulator folders will have symbolic links into this folder. I use the windows command "mklink /J", for example, to create a directory junction from E:\meta\LaunchBox\Data to E:\meta\Emucloud\LaunchBox\Data. That approach keeps all my synchronized data in one place (Emucloud), and I only have to setup this folder in syncthing. Making symbolic links is pretty easy, and I just threw these commands into a simple batch file I can run on a computer when setting it up for emulation.

Syncthing will keep these two folders in sync, so if the newer version is on PurpleTentacle it'll be copied over the GreenTentacle. It will occasionally ask for clarification about which file you want to keep, but I've not seen this often; when I do see it I just select the newer file. If you delete the file on one computer, syncthing will delete this file on the other computer(s). I've not noticed syncthing to be resource heavy. It's starts quickly when I start windows and hides out in the tray. If you don't like its windows notifications, you can turn those off. I use it to sync emulator saves, launchbox data xamls, and launchbox media. I use a three computer setup: a general purpose NAS and two computers on which I play games. I've tested retroarch and dolphin savestates made on one computer and have had no problems loading these states on the other computer. The sync is of course not instantaneous, but it's pretty quick in my experience on my home network (which uses powerline ethernet is not super fast). Of course, you could see where clashes would occur if you were trying to update the same file on both computers at the same time; syncthing would probably ask for clarification about which file you want to keep. This is a problem with any type of filesync service.

UPDATED to v1.6.1 -- fixes exception sometimes generated on options page when switching from another theme