[Question for Focus Tree Completionists]

Hey all - to those who have completed all five of the Focus School trees, totally finished with focus - do you still see the yellow focus orb in missions and do/can you still gain focus?

It may be silly, but I ask because I know that when you've reached your daily focus limit, the yellow focus orb no longer appears in missions, and I want to keep seeing mine and gaining focus points even after I complete all the trees. Why? Well, I simply enjoy the game mechanic and like challenging myself during those bonus period, and secondly because we'll never know if DE plans to expand the trees at some point, right, so having banked focus seems reasonable.

Thanks!

[Hotfix during Arbitration Can Cancel Mission and all Rewards]

This has now happened to me twice and is ... ugh ... really unfair and annoying.

If you're playing an Arbitration, and during that Arbitration there is a Hotfix deployment, and during/after the Hotfix deployment the host leaves or crashes, instead of the group reforming with the remaining players, it simply returns you to your orbiter without any rewards at all. You don't even get to keep the round rewards you'd get as if you'd died. You get nothing, nada, not even the end-of-mission recap screen, you just get the host migration screen and then appear in your orbiter with nothing. A complete waste of the time you've spent in the Arbitration.

I'm sure this is because, after a Hotfix, you can't start a new mission until you patch, but the host leaving an Arbitration and thus causing a group reform should not count as beginning a new mission.

First time, I thought it might be a one-time glitch, but it just happened to me again during today's Hotfix, so it's now repeatable.

Yes, one can hopefully avoid it in the future by leaving an Arb as soon as possible after the Hotfix is announced/deployed, but that doesn't return the now 70+ minutes and rewards I've lost due to the bug.

 

[I want to report players for "afk" playing]

Wow. Lots of hate on the OP. My guess is that he has valid frustrations but picked bad examples with which to express those frustrations.

What I will say is that, regardless of the poster's situation, I have personally witnessed people that are quite literally AFK (like, standing at the start of the mission and not ever moving, even to run to the exit when we're trying to extract). It also bothers me to no end when people join PoE / OV bounties and go off and fish/mine or whatever, hoping to have me and others do the quest while they simultaneously farm resources. The latter, if you weren't aware, DE has tried to fix, to an extent, at least with OV. You need to be at the place where the thing is happening or you don't get quest rewards or pickups like Toroids. It's not a perfect system, though, and doesn't work very well at all in PoE, and even in OV, you can ignore the quest and fish/mine as long as you're close enough to the action.

I do agree with what everyone has said, though, about being careful not to report users that simply are bad or look like they're afk but aren't. Maybe there was an emergency and someone had to get up for a minute - it happens to even the most dedicated player - though I wish people would at least SAY something when that happens. There's also a line between stopping between stages of a bounty to grab a single mining vein that is right in your face versus going to mine for entire bounty stage, and sometimes that line is hard to find.

What I will say, though, is at the end of the day there will always be people who try to abuse others and the system in general to get what they want without putting in the work, and when it's a conscious decision they've made, like literally fishing during every stage of a 4 or 5-part bounty, those are the people I'd really like to just uninstall the game, but since that isn't going to happen, it would be nice to have a method of reporting them ... it's just that, as everyone's said, people's ideas of AFK and abuse will differ and it's unlikely that DE will ever be able to sort out the actual offenders from the borderline or misunderstood cases. It sucks, but there it is. My best advice would be to leave those groups and get on with enjoying yourself. Dwelling too much on the negative will only make your experience worse.

[New Hotfix (12-19-18) Crashes on Start]

That seems to have fixed it, thanks.

Guess I should've remember to update my Discord after patching Warframe 🙂

[New Hotfix (12-19-18) Crashes on Start]

Just downloaded the new hotfix, around 8 PM EST / 5 PM PST on 12-19-2018, and the client now crashes as soon as I start it. I don't even get to the login screen. Never had crashing issues before in hundreds, maybe thousands, of hours. Pretty sure it's not me as it started happening literally on the next boot of the client after the hotfix.

[dual wield-glave/gun]

I have had this issue with the standard Glaive weapon as well. It basically makes it impossible to melee unless you manually switch over to just the melee-only function. When dual-wielding, quick attack becomes impossible. But this is why I don't use glaive weapons 🙂

[Oculysts / Sentients Not Spawning on Lua]

Hi,

I've just run 11 missions on Lua (with a friend, so this issue isn't just 'mine'), and despite getting the standard notification, the Oculysts only spawned in one of those missions. Space Mom gives the normal dialogue saying that the Oculysts have arrived, and you should avoid being scanned, etc. but the Oculysts are no where to be found. We tried waiting, going forward slowly, sprinting quickly through the map, but the Oculysts are simply not there.

Unlike other bugs that might be minor annoyances or inconveniences, I don't see a workaround for this issue. Reloading the stage doesn't seem to fix it. Without Oculysts, you can't spawn Sentients, and since this is the only place outside of a quest you can encounter Sentients, it's kind of a big deal / bug. Hopefully this can get some attention? Because it seems like, until then, Sentients have essentially been removed from the game.

-Sneaky

[Sauntering Mesa and the Frowny-Faced, One-Armed Man]

Also, if all my wildest dreams are to come true, it might be nice if auto-run were to persist across Sanctuary Onslaught rounds. As it stands now (for any/every character), auto-run needs to be toggled at the start of each and every Sanctuary Onslaught round.

[Astral Autopsy Completely Broken]

Been a couple weeks - was wondering if, perhaps, we might get a comment from the powers that be?

Again, we understand stuff takes time to fix, it would just be nice to verify that this is a known issue and on the list to get addressed in the future.

[Sauntering Mesa and the Frowny-Faced, One-Armed Man]

At the beginning of the mission, the man uses his good arm to press the "+" key on the keyboard's numpad to enable auto-run for the rest of the mission, then moves his hand back to the mouse and rushes off to (save the hostage | kill some dudes | capture dat bad guy | other mission objective).

Enabling auto-run via the "+" key is second nature for him at this point, as he does this at the beginning of every mission. Using auto-run frees him from having to hold the Shift key, but this time, even though the keypress is second-nature to him, he smiles, reminding himself that Warframe's deep customizability and support for macros allows him to run 98% of the game's input through his mouse and thus play almost entirely one-handed. Which is good, because his left hand is almost entirely lame at this point, and Warframe continues to be one of the few shooters that he is still able to play.

And then ...  it happens ... and it's great!! ... but then ... oh noes!! Major Frowny Face!!!

He's done it. He has used Mesa's ultimate (skill #4, Peacemaker), and watched as the hordes of pwnt Grineer evaporate into dusty, bloody, sprite-ey nothingness. But as Mesa puts her Regulators away, and saunters off at walking speed, bitter agony and a major frowny face floods over him - Mesa, it seems, always forgets how to auto-run after using Peacemaker. He's also reminded that all warframes forget how to autorun upon death, but he considers not mentioning that one, as he's pretty sure complaining about it will draw the ire of the "git gud, dont dye" trolls.

 

So, there ya go. The toggle auto-run is disabled when Mesa uses Peacemaker, and there are actually quite a few other frames with other skills that behave the same way: use skill, autorun is turned off. The mostly one-armed man (me), would be eternally grateful if the autorun toggle could survive through skill use. Surviving through death would also be a welcomed change / fix, but I understand that that might be a fundamentally different situation / discussion.

And before people ask - yes, for me it *is* a big deal to have to re-press that "one" key. There aren't enough keys on my mouse to have autorun bound there, so I need to stop everything, remove my hand from the mouse, move it to the keyboard, find the key, press it, move it back, etc. to get autorun turned back on, and this happens every single time I use Peacemaker and some other skills. Mesa just so happens to be a favorite, hence the example.

Thanks.

 

 

P.S. - Wasn't sure if this should go in Bugs or General, so feel free to move it if need be.

 

[Flappy Zephyr Un-Saves Arsenal Customizations]

Ok. If you go into your Arsenal, change the appearance of a frame, switch to Zephyr (without leaving the arsenal), play Flappy Zephyr (either on purpose or accident - don't worry, we won't tell anyone about your addiction), then exit Flappy Zephyr, the appearance changes to the first frame will be gone. It may affect other things you can do in the Arsenal, and in fact, it probably does, but I spent enough time figuring out this series of events that ya'll can take it from here 🙂

Basically, I believe that your appearance changes are normally saved when you exit the Arsenal, but by entering Flappy Zephyr, it's taking you out of the Arsenal without saving. This is backed up by the fact that, upon exiting Flappy Zephyr, you're returned to the Navigation Console and not the Arsenal.

Anyhow, small problem, but figured you'd wanna know.

[Baro Weapon Skins are Wrong]

Baro's new weapon skins, the Twin Grakatas Towsun Skin and Sonicor Elixis Skin, when you hover over them in Baro's inventory, both incorrectly state that they are a skin for a weapon that I do not own. But ... I own both of them.

[Astral Autopsy Completely Broken]

On 2018-06-01 at 4:55 AM, NinjaZeku said:

Just checking, are you trying to "autopsy" enemies whose Codex entries are already filled?

Because that, I think, should then cause you to not scan them / expend Scanner charges, similar to Helios.

(Or maybe I'm completely wrong about that. Nah, unpossible.)

Sadly, no. I've only scanned a few Archwing enemy types by hand (using the codex scanner) for testing purposes, so the Archwing portion of my codex is almost entirely empty. I've killed, with Astral Autopsy equipped, dozens of enemy types - most among them enemies that have no codex entry whatsoever. I was really hoping to use Astral Autopsy to fill out my codex, and not have to scan Archwing enemies by hand. Hmm .... it's almost like that's the reason this item was created ... Nah, that's crazy talk!

What I was really hoping for, though, was an acknowledgement from the powers that be that they know this (as well as Heliocor, etc.) is broken. I understand that it may take time to fix, and I think we're all ok with that, it would just be helpful to know that it's on the list. Otherwise, it just feels like we're talking to ourselves, raging nonsensically against something we have no control over 🙂

[Other things you *can't* name your Zaw]

So, I noticed in the most recent patch notes that you fixed not being able to name your Amp '111', and not too long ago you fixed not being able to name your 'Balla'-based Zaw, 'Balla'. That's great, but there are other issues with naming Zaws and Amps. Maybe we can all get together and make a list of these un-Zaw and anti-Amp name failures?

I generally just try to name my Zaws in a very boring, unoriginal manner using the formula {Strike} {Grip}, and sadly, from personal experience I can tell you that some really basic, 'this should work' names won't work. Why don't they work? I'm not sure, but each time the game glibly reports to me that Zaw names can't contain profanity. The ones I've tried and failed to create are -

Ooltha Shtung
Rabvee Shtung
Kripath Shtung

So ... obviously you can't use the word 'Shtung', and hopefully I won't get banned from these forums for using it, because I know how bad of a word that is. If I scar anyone for life, apologies in advance. But you started, what with using that word to name one of your Zaw grips 🙂

Anyone else? I'm sure it'll be easier for DE to make one big 'fix' than doing this all piecemeal.

That said, if you'd like to do some piecemeal work and, after you've got this sorted out, rename all of my now-named 'Stung' Zaws to the proper 'Shtung' spelling, please feel free.

 

[Astral Autopsy Completely Broken]

I'm nearly MR23 and been playing for a bit. I know how the game works. Astral Autopsy is not working ... for me at least.

Supposedly, you buy this mod from Simaris, slap it on an Arch-Wing melee weapon, and if you kill a critter with your melee weapon and have a scanner equipped with available charges, it will scan the critter you just offed. Sadly, it simply doesn't do anything, and not only did it take a lot of Simaris rep to buy one (and he has similarly-priced mods that sell for 50p, so, you know the opportunity cost was high), but I also did a lot of Arch-Wing missions specifically to get some scanning done ... and didn't. So, big sad face here.

Here are the various variations and variables I've verified aren't ... vorking? 🙂

- Yes, I have Codex Scanner charges available and equipped, checked and verified in-mission. Regarding this, I've tried:

• Having both Codex Scanner and Synthesis Scanner equipped at the same time.
• Having both Codex Scanner and Synthesis Scanner equipped individually.
• Changing the equipment slot my Codex Scanner was equipped in.
• Using a Codex Scanner charge in-mission to scan something manually, then switching back to melee to try Astral Autopsy. After the mission, I verified in my codex that the manual scan worked and was logged correctly, while all Astral Autopsy kills did nothing (60+ on that mission).
• Killing critters with melee hits with Codex Scanner as the currently equipped weapon / equipment item (so that it says "Codex Scanner" in the bottom right of the screen where it lists your active weapon). Killing something in this state does *not* decrement the scanner charge count which is also shown in the same area, giving more credence to the "it's broken" claim.

- Yes, I'm sure I'm killing things with an Arch-Wing melee weapon and getting the killing blow. Regarding this, I've tried:

• Two Arch-Wings (Itzal and Amesha) and three Arch-Wing Melee Weapons (Centaur, Veritux, and Rathbone). Astral Autopsy was installed on all weapons. One (Veritux) had no Catalyst, Formas, or Lens installed. Centaur had all three. Rathbone had a Catalyst only.
• Roughly a dozen missions using only melee, though I didn't check my codex and find out it wasn't working until I was already 6-7 missions deep ... 😭. Tests afterward were performed on three alerts of varying levels and the level 3-8 Exterminate mission - Montes, Venus.
• Missions on Montes, Venus were performed solo, and only using Melee, so I'm absolutely positive I was getting the "killing blow" which should trigger the scan. That said, one of the higher-level alerts had 4 or 5 of the high-HP Ogma enemies that took ~3 swings, so enemies that required more than one melee hit also did not get scanned on kill.

 

I'm not super-keen to do a bunch more testing, but I'm open to suggestions. Really, though, it'd be great if ya'll just acknowledged that you've heard me and know it's broken and will try to get it fixed in a future update. I won't turn down any freebees, though, for the massive pain and suffering this caused me. If some Simaris rep or plat or a shiny something-or-other showed up in my account, I promise I didn't see it.

-Sneaky