devtrackers.gg
Your eyes shall be blessed with updated Volt Idle Animation GPU particles very soon!
Your eyes shall be blessed with updated Volt Idle Animation GPU particles very soon!
Our DB shows no Chat log of this conversation nor Kickbot suspending the supposed guilty. We also see that the account 'Padomay' is not Chat Banned.
Perhaps I'm misunderstanding, but we don't support Google Authenticator. Could you expand on how you set up 2fA using the Google Authenticator for your Warframe account?
You can do this glich with any warframe. All you need to do is go to your navigation, and in chat, press on a weapon link. Once it loads the weapon up, go back, your head will but stuck and about 2 seconds later it will disconnect along with any accessories, and glpyh
Everything reverts once you leave navigation.
Here is a gif showing you how.
EDIT: Found another glich. Pressing on a weapon link when you are about to join a game (1 second or so on the count down timer) makes your chat box disappear. The only way to get the chat box back is to restart warframe.
Thank you very much!
I just tried a bunch with Rhino Palatine and my accessories are fine. Is it all accessories for you?
How about you fix your retarded chat system? Get muted for linking an item just because the item is in all caps
Your code is f**king ultrashit.
You have been kicked from trade chat; next time lay off the capslock!
Bleep bloop. I am a robot.
When Barko?
If you're looking for Baro Ki'Teer you're going to have to learn to spell his name or find his :baro: emblem in your star chart.
I can't link my Zaw names without being kicked because they're all caps :(
You have been kicked from region chat; next time lay off the capslock!
Are you scoping this out? Please report back to DE with our desire for Kickbot circa 2016
Bleep bloop. I am a robot.
Bleep bloop. I am a robot.
This is why when random people ask me if I work for DE I reply with "deutschland."
Aside from the differences in stances already mentioned, is it meaningful to compare the range of Atterax with a Jat Kusar? They both have 'a lot' of range but in practice that range is expressed completely differently.
Hey Tenno! This issue will be fixed in the next Hotfix.
Grand Master eh?!! Thank you for the years of support - and the list! A lot of this does hit dev goals and discussions. 5 years and we still haven't solved the time to make every great idea happen though, but we're trying and now we have another cheat sheet :)
[deleted]
If your IGN matches your reddit name I see 34 runs yielding 8 Barrels, 7 Receivers, 5 Stocks, 8 Blueprints, a full set of the Puncture mods with some spares, and one of the AW mods. I'm not sure what you mean by "get nothing"?
Oh hey it's Glen being an ass again.
<3
We usually only log a few MB/hr and it clears it every time you boot the game.
I'm guessing your 18hrs AFK probably triggered some power state that made the graphics driver stop responding -- usually we generate a lot of swearing in the log when we can't talk to the hardware any more.
Zip it up and send it to support next time (or DM it to me on discord https://discord.gg/ZdJdgM7 [DE]Glen). If it isn't a device problem it's probably an easy fix.
But otherwise... do you really want us to be optimizing for the 18hrs AFK 'in some weird state' case? I can think of a dozen issues on my list that wo...
Read moreOk we figured it out and pushed a server-side fix ago.
The problem would only occur if there was a host election at the lobby (not to be confused with host migration mid-mission). For reasons we're still investigating we were never getting host election when we were trying to reproduce this issue and so many hours were wasted going off in other directions (I literally simulated thousands and thousands of missions to try to flush out the bug).
And yes, it would have caused problems for Infested Salvage, too.
IGN of who hosted, what date/time it was, and what you did just before that run would be helpful. I've personally put in close to 7 hours of ODS now trying to reproduce this with no luck.
Really could use the EE.log from the host when this happens.