Orav_94 Posted November 26, 2014 Share Posted November 26, 2014 I was playing T4S when suddenly the life support stopped dropping and enemies stopped spawning. Then at 5 minutes we didn't get any reward and extraction was not unlocked. Anyway, we aborted the mission and started again (luckily the key wasn't consumed), when after ~24 mins the bug happened again, and at 25 we didn't get a reward, so we went to extraction. Unfortunately, this time the key was consumed. I already opened a support ticket, but until it's answered I would like to know if anyone had the same problem, maybe with other survivals also. Thanks. Link to comment Share on other sites More sharing options...
[DE]Saske Posted November 26, 2014 Share Posted November 26, 2014 Never happened to me and i play a lot of survival for debugging, but i saw some similar forum threads about this bug. Link to comment Share on other sites More sharing options...
Orav_94 Posted November 26, 2014 Author Share Posted November 26, 2014 It started happening to me right after hot fix 15.3.3 was released, twice in a row. Before the hotfix it never happened to me. Link to comment Share on other sites More sharing options...
[DE]Whirrrrr Posted November 27, 2014 Share Posted November 27, 2014 I was playing T4S when suddenly the life support stopped dropping and enemies stopped spawning. Then at 5 minutes we didn't get any reward and extraction was not unlocked. Anyway, we aborted the mission and started again (luckily the key wasn't consumed), when after ~24 mins the bug happened again, and at 25 we didn't get a reward, so we went to extraction. Unfortunately, this time the key was consumed. I already opened a support ticket, but until it's answered I would like to know if anyone had the same problem, maybe with other survivals also. Thanks. Did you send a log file with the support ticket? Link to comment Share on other sites More sharing options...
Orav_94 Posted November 27, 2014 Author Share Posted November 27, 2014 nope, didnt know how to do that :( Link to comment Share on other sites More sharing options...
Chroia Posted November 27, 2014 Share Posted November 27, 2014 (edited) I've had this happen once. I should have the EE.log, but I neglected to label it, so not sure which of the 2 unlabeled it is. Can you give me a text string to check for? That ought to narrow it down. Edit: On retrospect, I should have some time-stamped screenies. If I can find them, I can compare. Will let you know. Edited November 27, 2014 by Chroia Link to comment Share on other sites More sharing options...
Doomclaaw Posted November 27, 2014 Share Posted November 27, 2014 (edited) This happened to me, but when the host left, the bug fixed itself, so it's definitely something on the host's end. Edit: each squad member left one by one to see which was causing the issue, when it got down to just me and the host, host left, host migration ensued, bug was gone and I finished the survival. Edited November 27, 2014 by Zorrandor Link to comment Share on other sites More sharing options...
Chroia Posted November 27, 2014 Share Posted November 27, 2014 (edited) Now that you mention it, we did have someone leave. Well, d/c actually. Fairly certain there was no host migration though. Edited November 27, 2014 by Chroia Link to comment Share on other sites More sharing options...
[DE]Whirrrrr Posted November 27, 2014 Share Posted November 27, 2014 (edited) nope, didnt know how to do that :( Here are some instructions in case it happens again :) https://forums.warframe.com/index.php?/topic/35420-mission-bugs-and-log-files/ The log file is wiped periodically, so to ensure the data from the last played mission is there, you'll need to quit just after the mission and grab a copy of the log file. I've had this happen once. I should have the EE.log, but I neglected to label it, so not sure which of the 2 unlabeled it is. Can you give me a text string to check for? That ought to narrow it down. Edit: On retrospect, I should have some time-stamped screenies. If I can find them, I can compare. Will let you know. Feel free to send us both! I'd prefer to look at both anyway to rule out any chance of missing something important. Edited November 27, 2014 by Whirrrrr Link to comment Share on other sites More sharing options...
Chroia Posted November 27, 2014 Share Posted November 27, 2014 (edited) Feel free to send us both! I'd prefer to look at both anyway to rule out any chance of missing something important. I did label it. Hadn't submitted because I hadn't moved it from the appdata folder, so I didn't see it, so lost track of it. Uploading to Support now, will update this post in a moment with the ticket ID. Edit: Done. Support ID is 258971, category is 'Account/General'. If there's any further info I can give, please let me know, I'll see if I can recall. Edited November 27, 2014 by Chroia Link to comment Share on other sites More sharing options...
[DE]Whirrrrr Posted November 27, 2014 Share Posted November 27, 2014 Got it, thanks Chroia! Link to comment Share on other sites More sharing options...
Chroia Posted November 27, 2014 Share Posted November 27, 2014 Got it, thanks Chroia! My pleasure. Please note, in case you haven't seen it, that the actual ticket contains some info, as well as a text string from shortly after the person dropped (so you don't need to comb the whole log). Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now