C-Beats

One thing of note when using LEDBlinky with LaunchBox in relation to this report is that if you have multiple items selected the GameSelect event doesn't happen, if you hit play we just play the first item selected in the selection. That COULD result in a GamePlay event firing without a GameSelect event happening first.

So is the issue always happening or only sometimes? Saw in the log file that you ARE sending GameSelect on two games (one of which was contra) so want to make sure I'm understanding what is going on.

Could I get the following information for the users having this problem ( @Headrush69 @Golfboy01 ). Are you having this issue when launching via LaunchBox or Big Box? If Big Box, what GamesView are you using?

We have a fix in for this coming in the next version. In short it is caused by having altered Color Management settings in Windows. If you go to Control Panel and open Color Management. Then look in the advanced tab, ONE of those values PROBABLY isn't "System default" and so it causes issue when loading the icons for the context menu.

I am able to confirm this is issue and will get a fix in place to correct.

Ticket is always appreciated, but I saw the post and will take a look.

Just drag the executable from File Explorer to LaunchBox and run the importer

Wall View at this time doesn't have the index (the function you are referring to). All the other views have a single navigation axis (you go up/down or left/right, but not both). Wall View has two, because of this we've been a bit torn on how best to implement the index in a way that's intuitive without getting in the way of your normal navigation.

Typically errors like this are caused because of network traffic degradation. Things like packet loss. All of our media is hosted on the same server and so if you can download SOME images but not all it may be that your connection to the server isn't stable. After a download fails, can you run the tool again immediately after and grab the image or no? If not what game are you having the most problems with.

At this point in time I do not believe LaunchBox will be able to detect EA Play games. The new EA Play system uses whole new API calls than the old Origin system so we have to start over and see if we can get access to those calls to build a importer for it.

Glad to hear. I would make sure to turn off the update checks in the options menu inside of LaunchBox. Unfortunately because of the OS you are using you cannot upgrade to a newer version than that. Turning it off will stop if from notifying you that you aren't on the latest or automatically download a newer version.

So I don't have GREAT news for you but I do have a way to at least make your set up work for you. The BAD news is because of how WPF works there just isn't a great way to let the theme's know with a relative path WHERE their resources are. That is why we create the symlinks on startup, to get around that limitation. Unfortunately that work around doesn't function with exFat partitions. the GOOD news is I have a work around that SHOULD. You will need to do the follow: 1. Make sure LaunchBox is CLOSED 2. Copy the LBThemes folder to \\LaunchBox\Core 3. Mark the \\LaunchBox\Core\LBThemes\ folder as readonly (when Windows asked if you want to push it down to all the files say yes). Let me know if that resolves the errors you are seeing. It is important to note that if you do this, moving forward if you download a LB Theme you will need to play it in BOTH LBTheme folders, not just one.

Dangerous statement to be making, I can be PRETTY needy.... Appreciate the willingness though.

Ah wait... I see now you are having issues with LaunchBox theming, not Big Box. Though I am curious, do you have the same issues in Big Box themes?

@graphix2004 Would it be possible for you to do the following on the exFat drive with any theme: 1. Launch LaunchBox and ensure Debug logging is on (Options/Debugging) 2. Open Big Box 3. While Big Box is open, open file explorer, go to \\LaunchBox\Core\ and tell me if you see a "Themes" folder 4. Close Big Box 5. Look in the \\LaunchBox\Logs folder and send me the most recent log file generated Have a good idea what is going on but would like the log files to confirm I'm on the right path.

There is a known issue with NavigationRows not setting the positions correctly for items resulting in the "hopping" behavior. We have code in place already that corrects this behavior in development. I'll make sure to reach out when that beta is released so you can test as I know you've personally found several of those issues at that point. Would be nice for you to be able to confirm we did indeed get the issues corrected.

Awesome, thanks for that. Look forward to hearing what you are able to shake out. Thanks for your willingness to help with it.

I'm fairly certain that is because it takes longer for the BeginAnimation calls to process so by the time the last one is told to process, the first one has already moved a bit. I have plans on how I could potentially battle that but it will take a bit to get it all implemented. If you reduce the number of items in the wall does it improve the issue for you? If so it would help prove that is what is going on.

You mean while animating, or you see this even after the items have stopped?

You could also set a style trigger to hide the item (Visibility:Hidden or Opacity:0) if the FlowContext.IsItemSelected property is false.

No problems. Though I will say that if you are trying to download media for all 12k games at the same time, the process that actually saves the media and moves it in the correct spots (runs at the very end) can and will take quite a bit of time to complete and have seen many people get errors or a "Not responding..." popup because of it, so plan accordingly.

Basically this happens because Epic should be redirecting you to a specific page and we are listening for that page to be hit, sounds like the redirect is taking you some where else. I would upgrade to 11.10, we have just changed the redirect logic in this upgrade to be a bit easier for users and it may also correct the issue you are seeing. Let me know if you still have the issue after that and we'll see what we can do to resolve it.

This error doesn't necessarily mean that your computer is out of RAM. Just that your OS refuses to give us the RAM we need to continue (for a whole host of reasons). I would try to download media for a smaller amount of items and see if that resolves. As stated in my previous comment, I have my suspicions that the update has anything to do with it.

We didn't alter any code regarding downloading metadata or media in the latest version update so I have my doubts the update is the cause of these issues. Typically those errors are caused because the communication between your computer and the servers didn't complete as expected. This can be caused by bad routing, server traffic, firewalls, net monitor/AV software, etc. EmuMovies is correct in that metadata comes from us, media from them (and only the media for items you check in the EmuMovies section of the importer or download media tool). If you are having issues with accessing both sites then it is more likely a network issue than LaunchBox.