skizzosjt

close, but no cigar, as the saying goes lol one more step is needed first. make "a)" be "user must enter into the System Menu" It doesn't seem to actually write anything when closing Big Box so I must: go into system menu exit system menu / return to platform menu enter a platform exit the platform at this exit point is when the value is written if you do not go into the system menu first, going into platforms and exiting them does not write a value. and also, going into the system menu and doing these steps is only going to work once. once a new value is written, if you enter and exit more platforms no value will be written unless going into the system menu again and repeating the navigation steps. also it can write a wrong value depending on what a user does. it seems the value is getting stored when user enters system menu. for ex: user is on SNES platform goes into System Menu exit system menu / return to platform menu enter a platform...something different than SNES....lets say Sega Genesis exit the platform SNES is written as LastPlatform value That is the wrong platform! Should be Sega Genesis instead. So that is why I think it's storing the value, waiting for more actions to write it. Stores SNES when entering the System Menu because SNES was what was selected when going into the System Menu, but it's not going to be written until you enter and exit a platform. If the user enters and exits SNES, they are going to think it is working perfect. If the user enters and exits any other platform, they will notice a discrepancy. also note if the user was to exit Big Box at this point of entering the system menu the value never gets written. So, in my head that is why the value should be written when entering the system menu, or at least one of the triggers that prompt a write.

I reported this previously. LAST PLATFORM being properly recalled has been bugged for last few releases. last game being remembered is working fine for me I found it has some bad logic being used for when the last platform is saved. Previous post for reference. devs, please address this issue. in my opinion it should work where I don't even need to go into a platform for it to be remembered as last platform. for ex, scrolling through the platform wheel, land on Sega Genesis, back out to system menu, right then and there Sega Genesis should be written to BigBoxSettings as the last platform. instead it waits for users to enter then exit platforms to make that write, but the logic used isn't working right as it can save platforms that were previously selected rather than the most recent platform.

Yes I've seen this feature in Steam before. And you are correct. In my use case this install status feature in the frontend was a reminder which games are currently installed or uninstalled since I do move games around on disks and I don't always keep them all connected. Also was nice if I booted into the frontend and basically all my Steam games were marked uninstalled, that was an obvious "oops I forgot to power on the disk" reminder lol. My goal was to highlight the automatic updating behavior of the install/uninstalled status is not working as intended anymore and that is the important part to resolve in my opinion. Adding a new missing value would be extra credit from my perspective. I agree with your point on why "Missing" should technically be added but it's the automatic updating of the value that is the real pain point for me because the game's install and not install badges cannot be trusted to have the accurate value currently.

That is actually what I want to happen. Depending on which PC I am at, or which disk(s) are connected, I want the install status to follow suit. My desire is for example, affected uninstalled games would flip to uninstalled if they are not found at boot of the frontend. Then maybe next time I boot the frontend the disks with these games are connected and therefore they should automatically flip to installed at boot of the frontend. After review I think everything looks good on Steam's end, but I'll describe everything to make sure we are on the same page. I have several disks in use for Steam. Quick summary Main disk is always given drive letter E Additional disk is always given drive letter F I have TWO backup disks which are used for backup and storage of games that I don't want to play anytime soon. These two backup disks are always given drive letters X and Z All of these disks have their proper path in the "libraryfolders.vfd" but of course not all of them are connected. In this example, my backup disks X and Z are not connected and I would then have 30 games that are considered not installed because they are only on disks with drive letter X and/or Z These are all valid paths. If we need to be technical, then when disks with drive letter X and Z are not connected then technically that isn't a valid path in this exact moment in time.....but otherwise, it's a valid path. libraryfolders.vdf So these are the disks that I primarily keep connected. Nothing is stored on main OS C drive letter and all my games are on additional disks E and F Steam is doing OK detecting which games are installed and where they are installed at that. I'm not seeing a redflag within Steam's behavior. The frontend is no longer interpreting that info correctly is my suspicion.

Steam games continue to report as "Installed" even if they are not installed. Their install status is not being detected automatically anymore. The "automatic" drop down value (used to be a checkbox) doesn't work properly. Been a problem for last couple releases I keep mentioning in the betas since 13.28 beta-6 Marking them as installed or uninstalled does at least force that value since as you can see from previous reporting even that didn't work for a couple releases. All Steam games were reporting installed no matter what value was entered and they were getting automatically updated to installed status. I've logged in and out of Steam within the frontend a few times now and confirm my API key is still working fine. Issue is on the frontend side Games are installed in the frontend and I have Steam in the background showing they are greyed out, NOT installed per Steam. Steam is correct, the frontend is incorrect. The game should be marked UNINSTALLED per how the feature is intended to work. I put in the proper value of automatic and have tried logging out and back in on both Steam, Steam within the frontend, and toggling the installed value to installed/uninstalled and back to automatic. Each time I return to automatic they go back to INSTALLED even if they are not installed. The program you are referring to that you have tested: LaunchBox Your hardware specs and OS - Windows 10 / Z390 Aorus Master MB / Intel i9-9900k / 32 GB DDR4 What you were doing in the app and how you were doing it - Browsing library Which theme you are using - Default The type of input you were using during your testing: controller, keyboard, mouse, trackball, etc. - KB + Mouse List of community plugins that you have installed I have removed these and tested without them as well. Issue persist even with ZERO plugins present. If you have a crash (LaunchBox or Big Box crashes to your desktop / close without notice), we'll need the whole crash report, which includes Windows event logs (a lot of times its multiple logs related to the same crash) and the mini memory dump that is stored in your Logs folder. The dumps may be large and include private data, so reach out if you want to share privately - Not a crash Your LaunchBox and/or Big Box debug logs (which are on by default during beta now) - File attached as an archive Logs.7z

hmm, I'm confused about a couple of your comments. I don't understand why you have said in general terms, "but I could do that without the frontend". I'm not sure how you landed on those assumptions. Both LB/BB are going to function the same whether you have one, two, three displays, whether they are extended or duplicated. Using an extended or a duplicated display would not make using either LB or BB pointless.

that is "overscan" seeing how it's just a handful of pixels getting cropped off equally on all edges. if it was an actual aspect ratio issue it would be totally whacked (stretched or compacted) and/or would have black bars on sides or top/bottom. your TV is 1366 x 768. If you set that as the output from your laptop and it is still cropped, then that confirms your TV is always doing some overscan routine and would in fact require you to resort to some extra tools on your laptop like what you landed on with the Intel iGPU software, in order to make it all fit (scale) onto the TV screen. with that said, don't extend the display. you should duplicate the display. it would eliminate any issue regarding stuff launching on the wrong display.

Big Box is not properly remembering the last platform that was selected. Here are the steps I must take to get the value "LastPlatform" in the BigBoxSettings file to update. From what I can tell this value is only getting updated with a pretty specific input sequence from the user. In the Platform Wheel the user must back out into the System Menu Whatever Platform is currently selected when backing into the System Menu is important here as you will see reading on. We will call it "Platform A" for this explanation. User then exits the System Menu to return to the platform wheel User then enters the current selected Platform ("Platform A") User then exits the Platform ("Platform A") Now LastPlatform value gets updated! In this case to "Platform A" Here are more notes for understanding In the Platform Wheel the user must back out into the System Menu Whatever Platform is currently selected when backing into the System Menu is important here as you will see reading on. We will call it "Platform A" for this explanation. User then exits the System Menu to return to the platform wheel User then SELECTS and then ENTERS a different platform, we will call this "Platform B" User then exits the Platform ("Platform B") Now LastPlatform value gets updated! In this case to "Platform A" NOTICE I SAID IT UPDATES TO PLATFORM A HERE AND NOT PLATFORM B So in that second sequence of inputs it is not even updating to the last platform the user would expect. It's as if whatever platform is selected when entering the system menu is going to be what will be entered as LastPlatform value even though the user could have selected a different platform since entering and exiting the system menu. Video example doing these steps. I am tabbing quickly between Big Box and the BigBoxSettings file as well throughout to show when the value is or is not being updated. In the first example it is Microsoft Xbox 360 as current LastPlatform value. I select Arcade, back into system menu, return to platform wheel, enter Arcade, exit Arcade, only at exiting Arcade does LastPlatform update In the second example is now Arcade as current LastPlatform value. I select Windows, back into system menu, return to platform wheel, select a different platform that being Sony Playstation, enter Sony Playstation, exit Sony Playstation. At this point LastPlatform value updates to WINDOWS which is the wrong value to update to. Note you can enter and exit as many platforms as you like, they do not update the LastPlatform value unless you enter the system menu first, and it only works for that one value change. For it to update again, you would again need to back into the system menu with a different platform selected. Big Box Last Platform Issue.mp4

In the latest beta, "beta-6", all STEAM games report as INSTALLED (install checkbox is checked), having their PLAY/INSTALL button display as PLAY even if they are not installed. I cannot manually change them either....or well you can, but then it instantly changes back to installed. I know this is normally automated in the background so that part of the process is not weird. But said processes determining the installed status/value seems bugged now. When I roll back to beta-5 the issue goes away, so, just confirming it is v13.28 beta-6 that introduced this issue.

Transitions: Only some are fixed Fixed: -from game wheel to game details -from game details to game wheel -from game wheel to platform wheel -from platform wheel to system menu -from category wheel to system menu Still broken: -from category wheel to platform wheel -from platform wheel to game wheel -from platform wheel to category wheel Video example for transitions: Big Box transition examples.mp4 VLC frame rate/playback: -I have enabled the experimental option. No crashes or hang ups or mission critical type bugs noticed so far -Frame rate/playback does not appear to have improved, it definitely has not improved in Big Box -I did not test this in LaunchBox previously since I don't use videos there, so I don't have a good history or experience to compare it to, but VLC frame rate/playback looks subpar compared to using WMP even in LaunchBox Video ex for VLC playback: Big Box VLC playback example.mp4 Video ex for WMP playback: Big Box WMP playback example.mp4 Issue with not remembering what wheel you were in (platform vs category in this instance) when entering and then leaving system menu: -I have PLATFORMS set as my default that Big Box boots into -If I change to view categories, and then enter system menu > X page, and then back out to what should be the category wheel, I instead am brought to the platform wheel -the trigger seems to be entering system menu > X page with "X page" being entering anything that has a new view/screen show up. So this would include going into options, or manage themes and the like. -just entering the system menu and backing out it will properly return to category wheel in that sequence of actions, so that is why I say it seems you need to go at least one more page deep in the system menu to trigger this issue Video ex for not remembering category vs platform wheel: Big Box Category Platform Issue.mp4 LaunchBox getting hung up on startup at "Loading Interface": -seems to be some improvement here! not happening as frequent, but it still happens -So, we cannot call this issue closed yet, but whatever was changed was a step in the right direction -Logs included for review Logs.zip Big Box elements animation behavior when returning to the game wheel from game details: -super strange bug here that is dependent on a specific sequence of inputs (or lack of them really) from the user -when entering a game wheel, if you then enter game details for the game entry that is initially selected, and then back out to the game wheel, some things act like they were going to start their animations but clearly don't do them. ie things that start off screen and are supposed to slide onto screen are still presumably hidden off screen or are stuck in a 100% transparent state -I discovered a way to prevent this issue from triggering. when you enter a game wheel, as long as the user selects a different game entry before entering game details for any game entry, animation behavior in Big Box is as expected! -so the issue revolves around the user NOT selecting another game entry before entering into game details of the initially selected game in the game wheel Video ex of this issue: Big Box Animation Issue II.mp4 What I am doing here: -1st sequence of inputs is showing me entering the game wheel and then selecting a different entry, then returning to the initially selected entry, going into that entries game details, and backing out the game wheel. Everything looks good and works as expected here. -2nd sequence of inputs is showing me entering the game wheel, and then going into the intially selected entry game details, when I back out to the game wheel this time, you notice the 3D box image is gone. This is the new issue introduced Game wheel index: -all letters and icons are blank on many included themes I tested. COLORFUL (the included version, not my custom version), DEFAULT, OLD DEFAULT, CRITICALZONEV2 - DEFAULT -a theme that worked ok with the game wheel index was COVERBOX -it is also OK in my customized version of COLORFUL, but I am using different code for the game wheel index. CTC also produces bad results with whatever code it spits out for the game wheel index by default anyway (that's a CTC issue) but whatever I am doing different (I rewrote this wheel index code myself months or maybe years ago when CTC started producing bad results) this is not impacted by this issue. I don't really know what I am doing there, I just kept trying stuff until I got the results I wanted, I am otherwise clueless to knowing the language to provide further insight on that Windows 10 i9-9900k Gigabyte Aorus Master Z390 MB 32GB DDR4 @ 3200MHz AMD RX 6900XT Seasonic Prime 850W PSU Unless otherwise specified, testing with customized version of COLORFUL using VLC media engine

Ahh ok, thanks for sharing. This would be occurring on a Windows 10 system with an i9-9900k. I'm under the impression what you're referring to was issues specifically related to the 13th gen family? I recall reading some widespread issues regarding voltage control on TechPowerUp when it was first rearing its head. If that was the issue you mean, I'm in the clear on that one. I appreciate your response and update! I know the FPS thing can be subjective to some. I never was sensitive to frame rate until I got a TV that could do 120Hz....now I notice things I never previously gave a crap about lol To clarify, the thumbnail flash, that is something I only noticed and provided a video example with FFMPEG, not VLC, only in Big Box. I know the other fella Heartless1Riku said that it was with VLC, but they also added that was in LaunchBox. I did not test that with LaunchBox since I only use videos in Big Box. So just making sure we are on the same page. In Big Box, VLC did not have this thumbnail flash issue for me. Looking at Heartless1Riku's video example, I would guess it's the same issue but seems there is a difference between which media engine is causing it between LaunchBox and Big Box. Maybe it happens with FFMPEG in LaunchBox too....something I also didn't test. So a quick summary = VLC in LAUNCHBOX has the thumbnail flash issue. FFMPEG in BIG BOX also has the thumbnail flash issue.

I 2nd this complaint, it's a step backwards for VLC. Transitions are not the same anymore. But the problem is not just with VLC, seems to be with the other media engines too. Transition points that no longer work as expected with all media engines, but VLC is the worse offender perhaps. This is what I noticed reviewing Colorful theme. -from platform wheel to game wheel -from game wheel to game details -from game details to game wheel -from game wheel to platform wheel -from platform wheel to system menu -from system menu to platform wheel -from categories wheel to platform wheel (sorry forgot to put this one in the videos) -from platform wheel to categories wheel (sorry forgot to put this one in the videos) -frame rate for VLC and FFMPEG playback looks poor. for ex I watch a video I know is 60FPS, it sure is not looking like 60FPS with either VLC or FFMPEG selected. you can see this in the videos I captured too. The same above issues can be said about FFMPEG, and WMP, but some small differences too so I list them below rather than make the same lists with just 1 or 2 changes..... Specific to FFMPEG -from game wheel to platform view seems to transition as expected -shows what looks like a single frame of what I would assume is an image for the currently selected game before video starts for game videos (game wheel and game details). Note this doesn't seem to occur for platform videos though. Specific to WMP -from game details to game wheel view seems to transition as expected -frame rate is EXCELLENT (it has actually always looked excellent with WMP) and makes it more noticeable how poor frame rate/playback is with the other two media engines right now It's like there is zero transition at all anymore. As if it's going from one view to the other in a span of 1 frame. Video examples of the above issues for all three media engines: -VLC Big Box Issue VLC.mp4 -FFMPEG Big Box Issue FFMPEG.mp4 -WMP Big Box Issue WMP.mp4 I'm still needing to do multiple attempts of opening LaunchBox to get it to actually load. I do not notice any improvements on this front. This should be priority #1 on the needs to be fixed immediately list. I'm quoting my previous post below, which has logs included there. This time around, I zipped the entire log folder to provide whatever ones you need for not only the Big Box transition issue, but also LaunchBox getting hung up during launch so often. Logs.zip The positives (confirming previous issues are resolved) -No more focus issues from hitting B on the controller when playing a game launched from Big Box -No more extra/unintended animations occurring when exiting games and returning to Big Box

Badges - Got it, it's a feature, not a bug. The theme is COLORFUL which has been modded, started with the CTC version you produced in v2.3 and I've been updating into subsequent versions of CTC since. All of the animations on the WheelGamesView have been the same for several years and only in the past when the dev team is making updates to the frontend has this issue occurred with animations getting triggered at wrong points when exiting games and returning to the WheelGamesView. Now in the past it was spread to other themes too including the default. I don't see the behavior this time on default theme so that is different from previous occurrence of the issue. My version of COLORFUL theme worked OK on 13.27, but now it doesn't in 13.28 betas so that alone made me bring the issue to your attention. I attached logs from the last borked attempt to open, and the very next attempt that did load successfully. I left it open for some time, and then closed the frontend and attached all four logs that were created. I notice every time it got hung up it created the same 120KB file each time sans of course different time stamps for each step. Otherwise it keeps hanging up on the same exact spot each time where it is adjusting game's play count and time and then appears to do something with the media engine....this media engine step never appears on the borked attempts when it gets hung up at "Loading Interface" Can see the next step is where the hang up problem is. The left hand side is a borked launched log, the right hand side is a successful launch. Files are attached! Note there are no crashes or event logs, I checked both application and system tabs for anything relevant to the frontend or when it was launched/closed and didn't see anything. The program doesn't crash, it is hung up indefinitely when it occurs. The only way I can close it is through force closing the process and then trying to open it again. MediaEngine 2026-07-13 09-34-44 AM.worker.logDebug 2026-07-13 09-34-39 AM.logMediaEngine Client 2026-07-13 09-34-44 AM.logDebug 2026-07-13 09-34-06 AM.log