Jason Carr

From what I can tell, my guess is that this is just a freak Windows glitch or something. Are you able to get it to happen again?

Thanks for the report. I won't be fixing it for 10.11 (too close to the release), but we'll put it on our list.

Ugh, whoops. Sorry for that. I apparently missed a field when I went to unblock the account. Try resetting your password one more time and hopefully you'll be good to go.

It looks like you still need to go through the forgot password process. Try going here and reset your password: https://gamesdb.launchbox-app.com/account/password/reset

@cataclysm67 This kind of dramatic, passive-aggressive garbage is not welcome here. I nearly banned you, but decided not to this time. If it happens again, there will be a permanent ban.

Is that when you try to log in? Or just can't browse any pages?

It's hopefully been cleared up. Spoke with the person who was doing it and they've promised to shape up. Please let me know in this thread if it continues.

It should be enabled again. You may have to clear out your cookies though in order to get back in, and you'll have to reset your password before logging in.

Honestly, that might be a good idea; I have anxiety issues too and a break can sometimes do wonderful things. I'll go ahead and enable the account though.

That really shouldn't be necessary...

I do appreciate that, but I have to admit that the amount of negativity and hate is extensive and fairly alarming. I can re-enable the account if you're confident that you can respond to people respectfully, however.

I'm not sure why that's happening. Your settings file looks fine. I tested beta 9 myself and I don't have that issue. All I can figure is that maybe LaunchBox isn't recognizing the platform as a ROM-based platform, and thus not offering to delete the ROM? Four criteria have to be met in order for LaunchBox to prompt to delete the ROM: The "Allow Deleting ROM Files" setting needs to be checked (and it is in your settings file) The "Application Path" in the game needs to not be empty The game must have an emulator associated with it The ROM file must exist I'm assuming at least one of those criteria are not met. It's also possible that it's a file permissions issue and LaunchBox doesn't have access to the file, for one reason or another.

What version of LaunchBox are you using? Can you PM me your LaunchBox\Data\Settings.xml file?

Hi @LordEvyl, I received various complaints that you were being very disrespectful in your submissions and moderator comments, so I've at least temporarily banned your account. It really doesn't do anyone any good to constantly call people morons and idiots in all caps.

Are you being prompted to delete the game like this?

What platform? LaunchBox never removes games from your hard drive without prompting, and will only prompt to delete ROM files. It can't uninstall Windows games, for example.

He's put in an immense amount of work on the DB, which I'm not sure is a good thing or not. I'll probably be hearing from him I suspect.

Alright, removed his authentication tokens, so he's definitely locked out now.

Well I disabled his account, but he's apparently still logged in. Hopefully I've fixed it by resetting his password. Still the same guy lol.

Is that new, from today?

Thanks @Pixel. Beta 9 is out now with a hopeful fix for those who were unable to access Steam metadata. Steam's web servers require at least TLS version 1.2, and apparently some systems for whatever reason were choosing to use outdated versions of TLS by default. We're now forcing TLS 1.2 for the Steam API calls; hopefully that fixes the issue.

I don't have a second log file from beta 8, only one from beta 7. Did you send another one?

PM me the log file if you would. We need to see the error message.

Thanks much. I believe he reviewed it and made some changes; can you test it again?

Beta 8 is out now to fix the metadata issue where the wrong metadata was being used in the additional apps when games were combined on imports. Also, for those having issues with getting Steam metadata, we still have never been able to replicate that issue, but we'd like to know if you have the same problem with this beta.