C-Beats Posted September 23, 2024 Posted September 23, 2024 The newest beta release has additional logging to help us figure out what is going on. If experiencing this issue please update to that version, turn on debug logging, and try to import and get the error. Once you do close LB and send us the most recent log.
idolfun Posted September 23, 2024 Author Posted September 23, 2024 So tried the firewall exception. This worked for awhile and now its back. I will try with the new beta version with the additional logging today.
trueanimus Posted September 24, 2024 Posted September 24, 2024 ive been doing some testing but still cant figure it out... however, i did notice that if you load launchbox and let it sit for about 5 mins, you dont get the error on imports. it may be that the update broke the way it reads the XML files, or slowed them down? Anyway, if i load and the try to import i get the same error, but if i just let it chill for about 5 mins while i get a cup of coffee... it works.. lol.. just thought i would share.
trueanimus Posted September 25, 2024 Posted September 25, 2024 New PC, New HD, Clean install of windows 10 (running on I9, 32g ram and geforce rtx 3060) and same error..
morph9266 Posted September 26, 2024 Posted September 26, 2024 I too have this error on new imports since the latest version. My current work-around (if it helps anyone) is to un-tick all the the options for downloading images for both LB and EmuMovies during the import wizard which then seems to import the game(s) happily and then refresh the metadata for them ones after. Seems OK once the games have their IDs correctly found.
faeran Posted September 26, 2024 Posted September 26, 2024 This issue has been resolved internally and will be out when beta 2 drops. If you would like to help test the beta, here's the link: 1
Recommended Posts