Numerounius Posted June 1, 2021 Share Posted June 1, 2021 ^^^ This is really weird and hope someone could come in and help elaborate exactly as to what is happening since this does not seem normal. Right now in my orbiter I have just under 1/2 of a murmur completed and when I go in a mission and mercy a thrall it shows up my progress at just under 2/3rds for some reason and when I have completed the circle in the mission it shows me what requiem that is back in my orbiter. Link to comment Share on other sites More sharing options...
realbartz Posted June 11, 2021 Share Posted June 11, 2021 Latching on since same thing is happening to me. I am sure that my client side murmur count is the correct one and that somehow warframe is adding to it. Persisted over 2 different liches so far, both solo and in group. Agreeing with original post that when the circle is complete in mission, regardless of out of mission progress, I am revealed the new mod. These 2 are taken right after the same stab. https://ibb.co/tLKtQGXhttps://ibb.co/vHc7CwY Second lich example solo mode. https://ibb.co/SyP3qjN Link to comment Share on other sites More sharing options...
NeedPants89 Posted June 17, 2021 Share Posted June 17, 2021 Did 2 liches this week and I noticed the very same thing. In my orbiter, the progress towards the first requiem mod shows to be about 50%. Then in the missions, you kill a thrall it and appears to be closer to 80%. Then when in mission the murmur farm shows that the first mod is revealed, it will actually reveal in the orbiter as well. The same thing repeats for the second and third requiem mod. In the orbiter the progress is always less than it is in mission, yet the progress shown in mission appears to be the leading factor. Link to comment Share on other sites More sharing options...
Alakafox Posted June 18, 2021 Share Posted June 18, 2021 Bump. Noticed mine was doing this the other day too Link to comment Share on other sites More sharing options...
CMDRKuixote Posted June 22, 2021 Share Posted June 22, 2021 Suffering from this same bug today: Tuesday, June 22nd. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.