-
Posts
5,176 -
Joined
-
Last visited
-
Days Won
18
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by C-Beats
-
Typically the cache job starts when you press a side bar filter option and load the grid. You'll see a real small progress bar toward the top of the UI (in Default) that is the cache build progress. It also gets cleared/rebuilt for ALL items anytime you change the image group or box size. If possible could you take a small vid of what you're experiencing and maybe I can see exactly what you are and let you know if that's "normal" or not.
-
I don't use LedBlinky so I want to make sure I'm understanding your report. When starting Big Box LedBlinky isn't being told the front end was started? Not sure what you mean by "front end controls"
-
What you may be experiencing is your image cache building. LaunchBox will take your displayed media and create a smaller version that is quicker to load the next time. If the cache hasn't been built yet though this process CAN add delay in loading items. Once the cache has been built this should speed up since we just read the smaller file from that point on. Swapping side bar values and reloading the grid can take a second and will cause that fade out/in though you are referring to.
-
-
Theme has been updated to version 1.2: Made changes to the Platform Details view - Updated strings - Adds tooltip to play button to see which game will be played Made changes to the Game Details View - Updated logic for the play button version dropdown to only display versions you can play - Added a manage button to manage game installations with
-
Can you post a screenshot of the games "Additional Apps" section in the Edit Game window?
-
Full size images can be used in the UI, they just aren't in the wheel because the load times become problematic at times (especially for older machines). Also if the source is higher quality the scaled image produced is also higher quality because it has more accurate data to use in the scaling process. If you wanted to you can change the normal image folders for a platform via the Edit Platform window and then store the non-cached image one a different drive than the cache is stored if you're running into HDD size issues. I will say however this needs to be done manually per folder, per platform so can be pretty time consuming and tedious to do.
-
In the future if you need to change theme outside of the app because of a corruption like that you can alter the BigBoxSettings.xml file located in \\LaunchBox\Data\. Change the value in the <Theme> brackets to Default and then start Big Box back up.
-
Could you two be a bit more specific what you mean by sorting them with a custom filter? Do you mean by a custom field like Rlad is talking about, or something else? How are you setting this custom filter?
-
Auto-Populate Playlists can be built based on support level. You select Controller Support as the Field and then in the comparison column (middle) you can pick the support level you want there, then in the third column the name of the controller (or controller group) you wish to check that support level of.
-
LaunchBox completes closes without an error window? If so could you go to Event Viewer and look in the Application error logs. There should be a record in there as to what is causing it. I would also run the installer again over your current setup. This DOES NOT override your data and is safe to do. This would potentially fix any issue with a dependency getting corrupted or incorrectly quarantined by some over zealous AV app.
-
Top Left menu just keeps closing (Odin 1.0.2.68)
C-Beats replied to Recyclebinhero's topic in Android
I have an Odin Pro and saw this issue after the latest OTA firmware update. All you need to do is push the button that is ghosting once and it should stop. I've never had it happen AFTER doing that. I've also seen this behavior both in LaunchBox and in games I've been playing so it definitely isn't just a LB issue on my device. -
Look in Big Box Sound Options, we have options in there that is the volume level while in attract mode or the themes demo. I think it defaults to a pretty low value, if you want to hear it better crank it up
-
I know BIg Box is ran on laptops by quite a large number of people (myself included) and they don't have issues. I'd make sure to check your settings inside of the Nvidia Control Panel and make sure your system is using the dedicated graphics card to run Big Box and isn't rendering it with your CPUs integrated GPU for some reason. I've heard of users in the past having a issue similar to that and it causing issues.
-
I've not used the theme enough to know what wheel/view you're referring to but if you look in the XAML file there is probably a "DoubleAnimation" changing the opacity from 1 to 0 and vice versa. Would just need to search for said animation then change the number to what you want.
-
Probably easiest to just re-import the ROMs. If you're not using the full set import make sure in the ROM import wizard you check the "Force use MAME metadata" and it should scrape the names correctly
-
When this happens can you hold alt down and press tab (leave alt held so the UI doesn't disappear) so see which window is displaying the black screen?
-
I was able to locate the cause of this issue and it's corrected internally. I'm hoping to get it into the next beta release. Thanks all for the in depth repro steps, it really helped in identifying the issue
-
No you use the Export to Android tool, but you use the zip it creates on your PC. You don't have to use it on an Android device
-
The way it works is that the image will now always take up the entire screen. To make that happen the image is stretched or shrunk until is big or small enough to fit on the entire screen. If the host machine's ratio is different than the image ratio (I assume 16:9) then yeah the image will look zoomed in compared to 16:9 users. Otherwise you'd either have to distort the image or have letterboxing. If you want it to exactly match what you're doing in SystemView you'd just need to change the alignments from Stretch/Stretch to Top/Left and it'd be the same exact thing you have there.
-
Try using the Export to Android feature to export that game to a directory. Then try using the zip file that process creates in the "Games" folder in the directory you pointed it to and see if you have the same issue there. I'm fairly sure I've ran that game successfully on that core with my Odin so do believe it's possible. You don't need to use that zip on an Android device, that export process has logic in it to help zip things up in a way that works better with that core though so worth trying the file it creates vs the zip file you're using now. If using ExoDos collection you will want to ensure the game is installed before using that tool though.
-
Not real sure how it's done via CTC but if you do the following the background should display correctly: Open \\LaunchBox\Themes\Neon Arcade Deluxe\Views\OptionsView.xaml Locate the image control who's source is backgroundoptions.jpg (was line 98 in my file) Replace Width="2194" with Height="{Binding ElementName=Canvas, Path=ActualHeight}" Width="{Binding ElementName=Canvas, Path=ActualWidth}" Save changes
-
The file you're referencing is a .NET Framework file which what LaunchBox is built with anymore. You can attempt to add the line to LaunchBox.runtimeconfig.json found in \\LaunchBox\Core\ but I honestly have no idea if it will do what you want it to do as I've never needed that flag to be set for any application I've used or developed for.