C-Beats

The following would be helpful bits of information to have before any one could help potentially identify why you may be experiencing issues: What is your processor? What is your video card? What does your storage situation look like? What type of drive is the image cache stored on? What operating system are you running? Are you up to date with OS updates? Are your video drivers up to date? How many systems/games are in your collection? Do you have these issues with the default theme? What version of Big Box are you running?

Would be curious if others are still having the problem. I know there was a new Windows Update last night and EmuMovies did a server update/restart. Curious if either fixed the issue for anyone else.

The newest beta does make this possible for all Themes/Views but you would need to update the theme xaml to do so, no theme by default does this because it simply wasn't available at the time. Adding the Endless property to the views FlowControl and setting the value to False will do what you want.

Thus far all the logs read the same, that the connection timed out. Not sure at this point the reason you all would suddenly be getting these errors. I have my suspicions that it's related to a Windows update affecting how the LaunchBox client is trying to communicate because the code that controls this process hasn't been changed in a long while. I'll continue to investigate to see if I can find a way to resolve the issue though.

@fraganator @neil9000 @Blitz Mary Do any you of you have custom settings in Windows Color Management advanced tab? Attached image of the screen I am referring to (should be able to just windows search for Color Management to get to it)

You can test and see though, I'll gladly take a surprise win lol

Yeah, it wouldn't surprise me if there was some net hub some where along the path that was causing the issues, and using a VPN would alleviate that because it forces use of a different path. I live in the Midwest though and I haven't ran into the issues being reported. It very well could be ISP related, or have to do with how the ISP is routing the traffic.

I would have my doubts that you would see any changes to that. To my knowledge that is happening because we animate each item individually. I have idea's on how to correct that but it requires changing quite a bit of the backend logic, and that has not occurred yet.

Would those having this issue please turn on debug logging. Try and scrape again and send me a copy of the log generated when it fails (just close LaunchBox, look for the most recent file in \\LaunchBox\Logs\ and PM me via forums). I will see if we can find a common issue in the logs that may help figure out why you are all suddenly having this problem. @zzscratch @Hifihedgehog @vahn65

Curious @xM0RKx if you are still having this issue or not. If you are could you turn on debug logging if not already and try the download again and send me the log when it fails.

@fawkesyeah I know you were seeing some weird behaviors with the WallView while you creating your theme. Would it be possible for you to grab this version and let me know if we got those taken care of?

@nicolasonline This beta has fixes to a lot of the issues you have report in various threads. Could you please update to this beta release and let me know if it resolves those issues and if there are any outstanding issues that aren't resolved in this release?

Shouldn't need admin privileges. Just make sure real time scanning is on in the controller configuration.

Reason I ask isn't so that we just NOT USE the feature (if possible) but was because I wasn't sure if you load the file through the UI instead of command line if RetroArch does some logic where it just reads the M3U file itself and passes the first file to the emulator instead of passing it the m3u file directly like it may do if done via command line.

Unsure then. Not sure I use that core. Are you launching that m3u through RetroArch UI or through LaunchBox?

The core doesn't support .m3u. It would be listed in it's docs (https://docs.libretro.com/library/genesis_plus_gx/) if it did.

We have been waiting for the next version of the RetroAchievements API to be built before tackling this feature. We were told it would have several features added that would make doing this sort of thing far more accurate. Once they release it we can revisit and see what we can do to facilitate the requests for better functionality.

Yeah that should be corrected already. Had to do with all the fun little maths we use to position items. We should be releasing a correction beta relatively soon so be on the look out. I'll do my best to remind you so you can verify the issue is resolved.

If a premium member you could create a theme to change how/where they appear in the GameDetailsView. Otherwise you can turn them on/off in the Options menu shown below:

If you open the XAML file for that view and look for the FlowControl control, you will see a Orthographic camera. You should see a Position property on that camera. Increase the middle number until the boxes appear where you want them to. Given the image will need an increase of at least 1 more than likely.

Hey Deam. Unfortunately that is a known issue introduced in 11.10. We have implemented a fix for it but wanted to wait to release a fix until we can nip several of the known bugs at once. Unfortunately the only options available to you at this point is to either put up with this bug and stay on 11.10 or revert your version to 11.9. There should be the setup for 11.9 in your LaunchBox\Updates folder. Just run the installer and point it to your LaunchBox folder (make sure it's the same folder and not LaunchBox\LaunchBox). The revert process won't undo your data and so is safe to do so.

You have to change how you are doing your box items. Instead of doing a Border with a Flow Image in it, you need to do a Grid with a FlowImage and a Border in it (both as a child of the grid). Similar to how @faeran does his wall view 1 in his POC theme.

Is there a theme you are seeing it with more? And also can you confirm whether the issue occurs in default theme or not.

Sorry, I mean the border control you have (<Border>) already around the box. Just add Height/Width to that control.