C-Beats

Ironically went to test the work around and "failed" their new captcha challenge....

We have code that clears cookie's related to Origin for this purpose. Epic at the time of integration didn't save cookies in any meaningful way that this was a problem when we first implemented it. I would assume some of the code on their servers have changed a bit and is causing the issues. I will look into adding an option to force login during import, or add something in options like we do with Origin. I'll see if I can get a work around figured out for you in the meantime.

That captcha was pretty troublesome when testing the implement as well. Unfortunately that is all coming from Epic and we have no way of bypassing it. I recently had to change my password and login the actual Epic Game Library app again and had the same annoying things in their own app.

Text is always done pretty immediate. FlowImages follow the following process "flow": Check if image cached, if not build cache item, load cache. If it has to build the cache item the load process can take a second to complete. If you entering a platform that doesn't have ANY cache items it can take a bit for the cache process to cache everything and load it. The other views did NOT have the same dispose logic in them as WallView which could have affected memory usage. That has been corrected for the next release.

Nice catch. Was able to replicate and will get it taken care of.

Thanks for this. I was able to replicate and will get a fix put in for it.

Currently no. In the next release we have a new CoverFlow Theme Devs can use that would make it possible to do it, but there is no option you can set inside of BigBox to make the view behave that way.

Did you get a hard crash with error report? If so is there anyway you could try to replicate and post the error you are seeing? Also what theme / view were you using when you had the issue?

It won't get reset on start up, but any update WILL overwrite that file. Neil is correct that using a standalone in a separate folder as the emulator for your videos would work best.

FlowVideo has a "StretchVideo" property that should make it fill the space it covers

Awesome information, thanks for that @JoeViking245

Both the ROM set and the MAME version need to be a newer version. The command we use to identify the ROMs in the import process has been in MAME since 2008 as far as I can tell, so something newer than that.

Rows is the number of rows to display in the FlowControl. If you have a CoverFactory set it will override anything you set in Rows though.

This process wasn't changed in the beta. I DID notice the labels were not updated in the wizard but I am getting the files copied there.

Disregard. I see what you mean. I'll look into why that is happening.

@wallmachine Could you send me your XAML file so I can see exactly what is going on. I have made some changes to code since last beta release that helps with extra rows not showing up, but feel this may be caused by something else. At the moment SelectedScale is ONLY for the selected item, you can't scale up TO the selected item the way you are referring to

Do you have any plugins installed that may be causing this? The error reads like LaunchBox is failing to load a dependency. If you don't have any plugins installed I would rerun the installation and see if that corrects.

Bit concerned that your folders are turning read-only on automatically as this CAN (as you've pointed out) cause issue's within LaunchBox. For those processes to work LaunchBox needs to be able to write to your Data and Metadata folders (and the files within them) and if it is waiting on a file lock it could cause that issue (though in most cases it should just error). Is LaunchBox installed in a system location on your computer? Can you complete ANY downloads? For example can you go to Help and select "Force Update Games Database" and download that successfully?

Not really sure I follow what you are trying to do. In the example image are you scrolling up/down or left/right? Not sure I'm following what you mean when you say it's cantering.

Look in the Grid.RenderTransform towards the bottom of your picture. You changed the name of a path, but wasn't sure if you replaced it everywhere. All names appear in the same file to my knowledge.

Would confirm you have a "Prop_ReleaseDate1_X" and a "Prop_ReleaseDate1_Y" and make sure their Text path is being set. Looks like XAML can't find it and is defaulting to 0.

Yeah, unfortunately that is because of the perspective camera. I have went ahead and built in a SelectedScale property to the FlowControl that you can utilize in the next beta release.

One thing I failed to mention with the Z position tricks is that you must be using a perspective camera. Orthographic camera's can't tell the difference in Z position when looking at the Z axis.

No problem. If I remember I'll hit ya up after the full release and you can let me know if you are still having the problem or if it has gotten better or worse.

Yeah, this beta has a lot of big changes and the current release does have some known bugs in. Why I said I would wait until next release, or even wait for the full version to come out where we should have everything ironed out. I just have a feeling some of the changes we made to make some of the new stuff function may affect anything some of the stuff that could be causing what you are seeing and would be nice to find out for sure before making too many more changes.