Jason Carr

Sweet. Thanks kmoney.

@Sithel I googled "Rec Room Masters tempered glass" and ended up here lol. Your cabinet looks awesome. The only real problem I have with my cabinet from Rec Room Masters is the plexi-glass screen; it scratches so easily and even right out of the box it wasn't very clear. Where did you order your tempered glass from?

@mthompson239 Feel free to create a ticket in BitBucket, yes. Does the controller work in MAME if you disable gamepad/joystick input in LaunchBox? I don't believe I've heard about this particular issue before with this particular device, but I do know that there are a number of glitchy drivers out there for controllers that can cause issues. If you can, check to make sure there isn't a driver update available for the stick. Also, I know that a lot of arcade controllers simulate keyboard presses instead of acting as actual gamepads/joysticks, so that could be part of it somehow.

No worries; ETA's gonna hook me up when I start that project.

Sigh. Okay, I'll add that to the list.

I've honestly yet to use Cemu. Is it really another one of those emulators that can't use the game's title in the ROM name?

@Xpendable What theme are you running? Any plugins? @Rod I'll look into that. Perhaps that functionality got messed with when we switched to using the Chromium engine.

Ah, wow. I believe I have heard of that but not for a while. Try playing with the controller settings in LaunchBox.

I haven't seen that behavior guys but rest assured that it will be fixed with LaunchBox.Next, which should be feature complete very soon. So at this point I'm just gonna say let's hold out until .Next is complete.

Hi Darkholme, this is the dialog you're looking for in LaunchBox: You can drag the image into the box on the right, then click the area where the above image says Clear Logo on top of it, and select Clear Logo. It's also possible that you just need to refresh your image cache in Big Box under Options > Image Cache.

@jbl77 This was actually just added recently (wheel slanting). Check out the "Unified & Ultrawide" theme:

Every single feature that is currently in LaunchBox will be in LaunchBox.Next. Good points on Ctrl-F and middle mouse scroll. Hopefully we can tackle those after we get the standard features in.

Come to think of it, if regular LaunchBox is working but not LaunchBox.Next or Big Box, then it must be something specific to LaunchBox.Next and Big Box. It could be related to game controllers, DirectX, even a driver issue with .NET WPF. Check to make sure your drivers are all up to date, including video drivers. We've heard about weird conflicts with some poorly-written keyboard software from Corsair as well, and nVidia's recording software.

We're still not certain if you have the same issue, but it probably wouldn't hurt. Then again if the button isn't showing up I'm guessing that's not the issue, but that's just a guess.

Yeah, I use Dropbox for the redundancy, backups, snapshots, etc., but it's generally not the cheapest solution.

That's the beauty of the forums; it will forever be documented here. I'll also note it so that I should be able to recognize it for next time. That said, in all honesty we don't recommend running the EXE from a NAS or network storage at all anyways due to potential performance issues. We find that ROMs do perfectly fine over network storage, but media and the application itself are much better stored locally.

@ForsakenZaroc Can you check to see if you have the "unblock" option listed above on the "LaunchBox\CefSharp\x64\CefSharp.Core.dll" file?

Did you run the update/setup on that particular machine, or did the files just get copied or sync to it?

Good to hear.

@anickname Ah, well that hopefully gets us a lot closer. I haven't seen this anywhere else yet, but that is most likely a security issue where Windows is refusing to load the DLL over a network path. The first thing I would try is "unblocking" the DLL using the method described here: https://stackoverflow.com/questions/21753979/visual-studio-could-not-load-file-or-assembly-operation-is-not-supported-erro @ForsakenZaroc What version were you using before upgrading? I assume Big Box worked previously? Are you running it over a network path?

I see, thanks. So there's some kind of specific issue with running it over a network drive on that older version of Windows 10. Are you able to update? That's a pretty specific use case that I probably won't be able to dive into.

Assuming you have no issues updating, I would first try updating that machine. I'm guessing it would resolve the issues, though I can't say for certain. All I can figure is it's one of these three possibilities: The .NET framework or a related library is somehow corrupted There's a missing our out of date library of some sort There's some kind of odd configuration issue causing the problem You could also try reinstalling the latest version of the .NET framework to see if that helps.

Sadly those dumps aren't very helpful for .NET applications. Thanks for sending it though. Just to clarify, the same collection and data works fine on another machine?

Okay, sure. Is the machine on an enterprise domain with security restrictions?

Hi @anickname, I'm sorry to hear about the trouble. The only thing I can figure is that maybe 1607 has issues with the latest version of the .NET framework. We're on the very latest version of the framework in order to take advantage of the latest performance improvements. I know there have been some issues in the past for people who haven't kept up to date. It also looks like Microsoft has ended support for version 1607, so that could explain the issues with the framework.