Fursphere

Installed fresh copy in \launchboxtest\ Upon loading LB for the first time, I see a Windows platform has been created, and it appears all of my Steam and Epic games have been imported. Personally, I like to have Steam and Epic in their 'own' platform, and not together in Windows, but that's just me. Next it started auto-downloading metadata and images. So it appears to work as expected. Pretty cool!

Not sure if this is a bug, or intended - but its the first time I've noticed it. For Symlinked folders - Is the ROM Import Wizard supposed to record the path as selected, or interpret it as the real path? I selected: d:\roms\ms-dos and the rom import wizard changed it to ..\exodos\exo\exodos\ Which is fine, but it removes the flexibility to effectively use symlinks.

For what its worth, I updated all four of my cabinets to the latest beta. I've only used BigBox so far, but no issues found yet. Update process was smooth at least.

Just loaded it on both my stand up cabinets - upgrade was clean. I'll hit the driving cabinets later. I'll play with the new features later. thanks!

Fruitmachines work like Visual Pinball - you need a video overlay. There is a whole community that does that, but I can't remember the name.

ReFS first came out with Server 2012. So its been around awhile. I use it (at work) with Hyper-V / Azure Stack HCI clusters. Never had any problems with it 'losing' files. I doubt it has anything to do with the Launchbox problems mentioned here, but its possible. I'd check overly ambitious anti-virus / anti-malware software first. There is noise about Microsoft making it the default file system in Windows 11 at some point, but for now NTFS is still the standard. If it was my system, I'd switch back to NTFS for home / emulation use for now.

You can also set a special keyboard mapping to bring up "Game Details" so you don't have to use it all the time. (IPac SHIFTED key for example)

RetroArch Netplay is built into BigBox. Its one of the options when you go to start a game on the "Game Details" screen. Are you talking about RetroArch netplay here, or something else?

Closing launchbox completely. Process no longer running, not even in the system tray. Sorry for not being clear.

Ok, closed and restarted LB again - and now the playtime for Ms. Pac Man is showing 1 min 53 seconds or something. Went over to CAB B, pushed the sync button, clicked off the Arcade platform onto Atari or something, then back onto Arcade, and Ms Pac Man has updated to 1 min 53 seconds. So maybe the crash is related to a lock where it is updating the cloud and trying to write to the XML file at the same time? file lock / database lock type issue?

Got it to crash again. Workflow: Start launchbox. (CAB A in this case) Arcade platform, find a game with zero playtime recorded (Ms. Pac Man for me) Play game. Played for about a minute, and finished the game (killed off all lives) Back to launchbox - scroll over to see if Playtime field was now updated. This is where it went unresponsive / crashed. Closed it, re started launchbox. Back to arcade platform, Ms Pac Man, still showing 'zero' playtime. (but no crash on restart?) Logs are attached. Logs.7z

Updated both my cabinets to beta 3. Playtime is showing correctly on both cabinets (for Mr. Do!) and LB is not crashing. So far so good!

Ok, fair enough. It found the error on both of my cabinets. I installed a 'fresh' copy of LB on my desktop and updated it to the beta and did not see the error. So I was curious.

Looking at the logs, I see this coming up: 2023-04-11 07:56:15 AM FIRST CHANCE EXCEPTION: Could not load file or assembly 'd:\launchbox\Core\Unbroken.LaunchBox.Windows.XmlSerializers.dll'. The system cannot find the file specified. at System.Runtime.Loader.AssemblyLoadContext.LoadFromPath(IntPtr ptrNativeAssemblyLoadContext, String ilPath, String niPath, ObjectHandleOnStack retAssembly) I have confirmed that file does not exist - is this expected?

Updated both cabinets. The update took longer than an update normally takes, but seemed to complete successfully. Upon launching Launchbox, immediately noticed (on both cabinets) that cloud sync'ing had been re-enabled. I specifically disabled it previously with Beta 1, so this was interesting. Cab-A - Everything seems good so far. "Playtimes" column was visable in Launchbox, and times showed. Cab-B - "Playtimes" column is missing, and upon trying to right click on the title header bar to see if it was enabled or not, Launchbox went unresponsive / crashed. I let it sit for ~10 minutes before forcing close. I've attached the logs here. Cab-A-Logs.7z Cab-B-Logs.7z

@C-Beats Checked the cabinets this morning and debugging was already enabled. So here are all the logs from last night. Cab-A-Logs.7z Cab-B-Logs.7z

All from Launchbox Sure, I can do that later today.

Cloud Sync seems to be a bit buggy. Here is what I did. CabA - Enable Cloud Sync - Enter LB DB username/pwd CabA - showed syncing / syncing complete. CabA - No changes to playtime information in LB (Using Mr. Do to observe) CabB - Enable Cloud Sync - Enter LB DB username/pwd CabB - showed syncing / syncing complete. CabB - No changes. Verifed Mr Do had a different playtime than CabA. CabB - Click off "arcade platform" to "atari 2600" then back to "arcade". All playtimes are now zero'd out. CabA - Hit Sync - No changes. Cab A & B - Close LB, reload. Now both LB's are showing zeros for everything. CabA - Launch Mr Do. Play for 10 minutes or so. Close game CabA - LB still shows zeros. CabA - LB hit Sync - sync completes. All times comes back, and Mr. Do is updated accurately. !!! CabB - LB hit sync. No changes. All games still showing zeros. CabB - Launch Mortal Kombat. Get my butt kicked for a few minutes. Return to LB. All games still showing zeros for playtime. CabB - Shutdown LB. Restart LB. CabB - Check for playtimes on MrDo and MK - Observe "playtime" column is no longer displayed and then LB crashed. No error, just hung and Windows gave me the option to close it. CabB - restart LB - same issue. If I try and scroll to the right to see the 'playtime' column, it crashes. CabB - restarted PC, let it boot into BB, quit into LB, same pattern. Crashes when I try to view the playtime field. If I was to guess, I would guess the Sync feature corrupted the local DB (XML) EDIT; So if I reopen LB after it crashes. Click on any other platform, verify that "playtime" field displays, then click back to "arcade" it seems to stop it from crashing. However on CABA, all playtime numbers have returned to zero. I went ahead and disabled sync'ing for now on both cabinets. I edited the XML file and didn't see anything out of place or obviously "wrong" with the <playtime> field. Looked normal to me.

In place upgrade from 13.2 --> 13.3 went smoothly on both of my cabinets. Going to try the cloud sync in a bit.

You can have Archive Manager COPY the games you play frequently to your local cache location, so only the first run would potentially be slow.

Interesting. I didn't know about that. But this approach would require turning every 'Platform' into a 'Playlist' essentially. Not that I'm against that, it just seems a little counter-intuitive, and then having BigBox show/default to Playlists.

Sorry for bumping this old thread, but I found this comment funny, because that exactly what someone did with a bunch of junk Casino games. 1 vote total, 5 star rating. I promptly deleted those "games" from my list. And there should be a filter or something for BigBox. Like, don't show games that are 1 star or less. Having to make a playlist for every little thing gets old.

Sorry to bump a really old thread, but this seems to be one of the number one google search hits on the subject. Sinden Light gun - SNES - RetroArch - SNES9x Core. I'm using the latest version of RetroArch - 1.15 as of this post. Settings - Input - Controller 1 - Mouse Index = N/A #2 (This is what screws everything up - the mouse gets mapped to Port 1, killing the lightgun. This might be whats wrong with Mega Drive too - haven't tested yet) Settings - Input - Controller 2 - Mouse Index = 1 Then you need to setup buttons in Settings - Input - Controller 2 - for Gun Trigger, Gun Aux A, and Gun Aux B (on mine, Gun Aux B was the actual 'trigger' in Battle Clash...) Hope this helps someone in the future!

Update: Couple of reboots later, it magically just started working. Nevermind. Nothing to see here.