[1.0] Final Descent achievement

[ranger_lennier]

I completed the Final Descent level, but its Steam achievement didn't unlock. I'm not sure if it matters, but I had previously completed the level in some of the betas before achievements were added.

[matt]

Hmmmmmmmmmm........... That's really strange. As soon as the ending finishes, we award you the achievement unless Steam already had the achievement recorded for you. Can you check your Steam profile to see if you have the achievement there? Maybe the pop up didn't work.

[ranger_lennier]

No, it's still not showing up.

http://steamcommunity.com/id/lennier1/s ... ievements/

I finished the stage, watched the ending, then hit A to skip the ending credits.

[matt]

Hmm.... I have no idea. There really isn't a lot of code on our end where that could go wrong. Where you able to get all the other achievements?

I hate to ask, but have you tried replaying the level? Maybe there was a network connectivity issue or something when you were playing. It triggers as soon as it switches from the ending scene to the credits, so the pop up appears over the beginning of the credits.

Is anyone else having a problem with that?

I'm so sorry for the trouble!

[ranger_lennier]

I played through Final Descent again in the 1.1 build, going straight to it from the Nightmare Select menu. I completed it and even let all the credits play this time. There was still no pop-up, and my Steam profile doesn't show it either.

I've got all of the other achievements. I unlocked Destroyed Dreams on August 19, using one of the alpha or beta builds (whatever was current at that time). I unlocked Wayward Dreamer and Veins after the game was released.

Final Descent was available to me in Nightmare Select immediately after the release, because I'd already opened it up in an earlier build, before you added achievements. The first time I finished it after the official release, I had used Nightmare Select to start at Insanity. I don't think I ever completed Final Descent between when you added achievements to the alpha/beta builds and when you released version 1.0.

I've never really worried too much about achievements. It's strange that this isn't working for me, though.

[matt]

That is really strange. I am completely stumped. I have no idea why that wouldn't work for you. Maybe there was some problem because you maybe got the achievement before the game was public, so it doesn't show up on the public website? Although that doesn't make too much sense because I have the achievement.

Unfortunately, I have my hands full, so if you aren't too concerned about it, then I'm not going to worry about it. I hope you don't mind!

[ranger_lennier]

Yeah, if I'm the only one it's happening to, I'm not going to worry about it too much.

[RightClickSaveAs]

If you really want the achievements, you can try out Steam Achievement Manager: http://gib.me/sam/

Use at your own risk etc, don't have it running while you play on any VAC secured game servers or you could get banned, but this is supposed to let you grab the achievements from any game you want.

[matt]

Some people on the Steam forum are reporting problems with the achievements as well. I've contacted Valve to see what the issue might be. It seems like our code is pretty solid (and it's very similar to what I did on Retro/Grade), but achievements are hard to test for since as near as I can figure, you can only get them assigned to your game once.

[matt]

The bad news is that I haven't heard back from Valve. The good news is that we tried to implement a work around. We now save whether you've been awarded the achievements or not. If you are supposed to get the achievements, and you haven't gotten them, we will keep trying to award them for you. Unfortunately, since we didn't save this data previously, it means you'll have to playthrough the levels that award the achievements again to get them. I'm really sorry for the trouble!

I think with this change, you should eventually get the achievement that you are supposed to, but replaying levels you've already beaten is not ideal, but we couldn't think of another solution.

Sorry!