(XBOX)ExoSin
-
Posts
29 -
Joined
-
Last visited
Posts posted by (XBOX)ExoSin
-
-
Let me start off by saying that nothing gets me as excited as a silky smooth user interface. I was looking more forward to a revamped UI than I was to getting Khora. Warframe has a reputation for being needlessly complex. That's where a lot of people have fun. There are menus upon menus of things to equip or interact with. There has been talk on the devstream where people tell stories of others who have tried warframe, and were intimidated by all the menus. Imagine if it was both the menus, and the method of navigation that where cumbersome. People have said they have gotten used to this new system and that's fine. You can get used to it, I can too. That does not mean it's in a good state. Warframe. more so than most games needs a fluid interaction system. As much care needs to be put into UI navigation as was put into controlling your warframe. If a new player has too many negative experiences in menus, however trivial they may be, they stand a lower chance of doing things like modding their weapons properly. Buying/building new guns, or leveling mods/ learning what they do. These annoyances will pile up so they escape the menus to missions, where they will slowly find themselves being outpaced by the game's content, where they will then claim that they "just don't get the game", and move on.
Let me take you on a guided tour to switch my Inaros from Config A to Config B.
-I step in the arsenal and press X to open it, then press Y to open my upgrade screen. All good so far, thank you for the shortcut implementation.
-I press RB to switch to Config B. Instead the bottom tray is switched from "All" to "Aura". Upon first entering this screen, two UI elements both show that we can interact with them by LB/RB at the same time. I feel whichever tray has the focus, the top window or the bottom one, should populate the LB/RB button commands on screen. Furthermore, the top tray should have focus when entering the upgrade screen to allow quick switching of configs.
-I notice that the bottom tray received my RB command instead of the top tray. So I press D-pad up to snap to a mod that is currently equipped in my top tray. The cursor is currently in the correct window. I press RB again. The bottom tray switches from "Aura" to "Augment. Entering the top tray using the d-pad snap instead of the left stick cursor does not bring focus to the top window. If instead of snapping to an element in the top tray, I would have used the left stick, the top tray would have been given focus and my RB command would have changed to config B.
-I now have to move my cursor off of the selected mod and on to a new mod in the top tray in order for the top tray to be given focus. This highlights the largest issue with the smart cursor system. It is not smart, it can not change focus from window to window. It also snaps to non-intuitive UI but more on that later.
The smart cursor is not smart enough to handle the quick navigation window at all. When pressing RB to open the Alerts, invasion, Sortie, and other miscellaneous stuff, the smart cursor does not even know it exists. This isn't simply a focus problem like the arsenal one, the D-pad cannot interact with this window. This is particularly annoying since you used to easily be able to snap to this element.
When in the void relic refinement screen, after selecting a relic you wish to refine and tapping D-pad right to snap over to the elements on the right side that allow you to refine relics, your smart cursor takes a field trip to the scroll bar. Why in the world would I need to snap to the scroll bar when I can scroll up and down with the right analogue? If given a mouse to navigate this window, I would not left click on the scroll bar and drag it to where I want it to go. I would use the mouse scroll wheel. I cannot fathom the state of depression I would need to be in to make me want to navigate a scrollbar using a cursor controlled by an analogue stick, but the smart cursor will interact with this; when I can't use the d-pad's quick navigation properties in the literal quick navigation window in the paragraph described above?
Opening the chat window and using the D-pad to snap to the names in chat will show me that I can press A while I have their name selected. Pressing A does nothing. D-pading over to the names does not grant focus to the small window that contains the names, so you are just press A in some other window where your cursor is. If I move my cursor over to the name of the play I wish to contact, and then press A, I am given an even smaller menu populated with things like talk and invite. D-pad snapping to talk and pressing A again does nothing. Because, of course, this new menu that has opened does not have focus.I now need to cursor over to the word talk, something that is as small as the cursor itself. Mere inches away from the three options I have to ban somebody from my alliance chat.
Mid mission it's a complete pain to check somebodies load out because you can't snap to the drop down menus for each individual player by using d-pad up like you used to. Furthermore, is you do put focus on the drop down menu, the new expanded option doesn't have focus. Grineer heads on the plains of eidolon from 100m have an easier hitbox than the leave squad option does in this menu. Futhermore, on occasion with the drop down menu opened, holding left-analogue to the right to look at another player's loadout will sometimes behave as if you pressed d-pad down and snap to a lower snap point on your loadout box. Why? Why would holding the analogue stick right make it snap down? The smart cursor isn't smart, it's drunk.
When you have a mod selected, there is a visible cursor in the way of the text. For many mods, as the card expands the cursor is displayed over the picture, or event he mod name. You presumably read the mod name before selecting it so you know what it is, this isn't a problem. But the more text on a mod, the higher the words on the mod creep up towards the top. Common sense of course, but when selecting things like rivens that may have an entire paragraph of unlock criteria, you're met with a situation where you need to capture a <top of cursor> target without <middle of cursor> while wearing a <bottom of cursor>ing dragon key. It tends to get in the way of the new set mods too that have a ton more text compared to most. Perhaps, when a mod is selected, instead of displaying a cursor in the middle of it, make the cursor invisible. The mod stays expanded, you can read what it does and enjoy the art team's work that they put into the picture on the mod. Snapping in a direction will simply expand that new mod, whereas moving the cursor via the left stick will make the cursor visible until it has anchored onto a new mod and expanded that.
There's also two invisible snap-to points in the operator menus. I presume this is because the screen used to have five options (the schools), but now it has three options (focus, equipment, appearance). The strange thing is that these snap-to points are not where the old options where, but in the middle of nowhere. I can snap to my operators collarbone which does absolutely nothing, but I can't snap to the quick navigation menu, Why God.
-
3
-
-
On 3/18/2018 at 2:10 PM, (XB1)Noa Kenobi said:
Well, fooey...
I've actually worked this issue out as well as I can.
So here's what those of you having this happen need to know.
First, next time you're on your Orbiter, stand in front of the Navigator (where you get the map) and then hit X so you enter it.
Notice on the chat window, all the way to the left-most side of that chat, you'll see by entering the Navigator, you created a Squad Chat.
Now if you hit B to exit the Navigator, and then go to the Start menu, if you look at the chat again, that Squad chat is gone.
When you enter the Navigator, you create a Host Session, you create a squad that others can then join.
So essentially, if you don't send invites (through XBOX Live or through in-game menu options) while you're actually engaged into the Navigator, then there is no Host Session for others to join.
So even if you use the XBOX Live controls to send an invite, you want to do it while you're in the Navigator in-game.
This won't fix it 100% of the time, cause there are other bugs, and there are network related issues as well... but it should at least help for most of the times.
Of course, if it persists even if you do it how I've described, then you and the other will both want to reset Warframe and/or your XBOX.
I wrote this months ago, and saw some recent messages on here, so I thought I'd share what 6 weeks of experimentation and research showed me.
These are two different issues. There is a bug where you aren't in a session and opening navigation will fix that bug. If you are not in a session, you cannot send an invite via warframe or from xbl, so if you are familiar with that issue, it's quick and easy to fix.
The problem in question is an extremely high rate of people who suddenly can't play together. There is one member in my alliance who can connect to every single person, and every one else is suddenly unable to play with each other. It always ends with a host not found error; we have to use him for any type of group activity because he's the only host who we can all connect to. These people have all been playing with each other with absolutely no problem for a very long time. They can play other games together on xbox, it's only warframe.
This issue began shortly after PoE released on console. I'd imagine some netcode fixes to try to stabilize people getting through the gate broke something somewhere else.
-
Have you gilded them? For Zaws and Amps you must level them to 30, gild them at Onkko or Hok, and then level them to 30 again. Mastery only begins to increment after gilding.
-
On 2/20/2018 at 4:45 AM, (Xbox One)R3d P01nt said:
I think there is also a bug where the countdown timer doesn't work properly when in operator form. I don't have video of it, but often I'll find that the disk will end prematurely according to the timer if I've spent any time in my operator while it was deployed. I don't think it's ending early though, I think the timer doesn't count down while in operator form. I'll try and test it later today.
I think this happens for any type of timer that is supposed to be visible in both forms. I noticed a 20+ second desync in various Smeeta buffs too, to the point where the doubler will run out on my frame but still exist on my operator. Sadly, the buff doesn't actually work on the operator when it's in this state. Only the buff duration from the warframe's point of view ever seems to matter.
-
Void containers drop random mods for all party members. Next time you see a gold mod, mark it. If it displays as "module" instead of the mod's name, it is a random mod and will be something different for your teammates. Being host has nothing to do with the rarity of what drops.
-
I would imagine the discrepancy you are experiencing is because of the speed at which you play the game as Ivara vs any other frame.
With prowl on, you will be moving slower and getting fewer kills/containers destroyed per minute than with most other frames/playstyles. In addition to that you are probably paying more attention to your energy bar because you are aware that it is draining, whereas with another frame you just play the missions normal without paying attention to your energy.
-
Good point, we were on different metrics, I was hung up on it when you said it was significantly lower for one than the other.
-
3 minutes ago, (PS4)lagrue said:
I was using the DE published one, I assume the automatically compiled one is more up to date.
-
If you are sprinting you usually cannot fire your alternate fire for some reason. Primary fire works fine, but not alt. I assume firing your primary makes you stop sprint for a moment which allows you to fire your alt, but then you resume sprinting because sprint is toggled on, which breaks your alt again.
-
I've found that killing the capture target before he is marked as the capture target causes his body to "die" instead of writhe on the ground to be absorbed. This also goes for assassinate targets- bounty won't progress if they are killed before marked as assassinate targets.
Also, are you playing in Solo or in groups? I've found that in groups the bounty stops progressing on the UI for some people, but others still see the progression. I.E. Defend the vault will read "insert datamass" But in actuality you may be a minute and a half into a functioning defense. I've found the misrepresentation only happens in squads but it can affect the host or the client.
-
50 minutes ago, (PS4)lagrue said:
Well on Shadow Stalker it is signifigantly lower at 37.94% - but this is countered by the fact every other weapon he drops has garbage 2.78% chance to drop.
I just double checked, Dread is listed as 75.88% for both. Strangely enough it also lists Hunhow as dropping Dread at the same rate.
-
The actual consumables to do this were removed awhile ago and your foundry was given the capability to do it. I don't know the controls for PS4 but:
Go to Foundry -> check lower right hand of screen for input to enter 'arcanes'
Tab over to the 'installed' section -> select syandana in question -> check lower right hand of screen for input to 'distill arcane'.
-
When casting Mesa's 1, 2, and 3, she will generally do a short animation with her hands. During this animation you can hold down the left trigger to aim down sights. When the animation concludes, Mesa will automatically go in to ADS mode (provided you are still holding the trigger). This is all good and fantastic but her fourth ability no longer does this. When deactivating Mesa's fourth, during the animation where she flips her regulators up the game will ignore a command to go into ADS mode. This leads to a situation where after animation full control is returned to you, you can be holding down the left trigger to be in ADS, but Mesa will not be aiming down sights. This may sound small but most gamers will agree it's very noticeable when you are inputting a command and the game is flat out ignoring it. There should never be an instance where you are holding down left trigger and in full control of your warframe but not acting as if you are holding it down.
This bug happens both with hold and toggle ADS, as both host and client, and is not unique to any skin.
Interestingly enough you can toggle sprint to be on during the very same animation. ADS seems to be the only command that gets dropped.
Edit: More playing has shown that this is only a bug with my primary weapon. Hold aim during the animation will allow you to aim if you have your secondary out, but not if you are using your primary.
-
The published loot table lists dread as a 75.88% drop chance, by far his most common drop.
-
I would much rather have these articula than the proposed bonus "old raid" sekhara that we are supposed to get.
-
2 hours ago, DeMonkey said:
Trials don't follow the flow of the game, PoE does.
Quite simply, the ''flow'' of the game is killing hordes of enemies. After the hordes are dead you might have the occasional sub objective like keeping something alive, but it's minor. Killing is truly the aim of the game.
There is only a single instance in all 3 raids where you are required to kill hordes of enemies, and that's for antiserum in JV. The rest of the time players either completely ignore enemies as they rush past them, or stand in one spot staring at all the enemies you've crowd controlled. You might shoot the occasional dude for a bomb, but there's no real reason to beyond that.
PoE is the only instance of "Free Roam". The uniqueness of that by definition makes it more against the flow than anything else.
How many kills do you get in a standard sabotage mission? I rarely bother killing anything. I think I get MORE kills in the sabatoge mission at the beginning of LoR than I do in any normal sab. Also, Every single room when on foot in JV requires killing to be done.
Looking at the kill counts for the top Speed runs of LoR, they have as many kills as a mid rank exterminate mission. I would assume by nature of going fast, they are doing less killing than the average group.
Captures, Sabs, exterminates, all are things blitzed through by the average player. Compare a void fissure capture to a void fissure mobile defense. Most groups I've ever been in will hands down ALWAYS choose the capture because stopping to defend the console several times slows down the flow of the mission. PoE is a bunch of moving to random points and killing just the same as MD. Players will almost always choose the laziest method. In most missions, this is bullet jumping passed dudes. In missions where that can't be done, they are often crowd controlled. PoE doesn't allow that, and I think that's why it burnt out the majority of people I've spoken to.
Let's take the hijack part of LoR and compare it to a sortie Hijack. In the sortie Hijack, I pick Inaros and stand on the core. In LoR, my team coordinates. You can argue that they too are just standing on buttons, co-op standing experience if you will. There's at least tension that you can be pulled off though. There's actual danger on NM LoR. I'd Also much rather do the third phase of LoR than a normal Vay Hek Assassinate any day.
-
Suffering from the same problem, can connect to them for party chat, and can play with them in other games. Host unreachable in warframe though. I've found that power cycling the console will fix the problem for about an hour about 50% of the time.
-
This is a problem with the mining laser, it lowers your sensitivity massively while mining, but sometimes it doesn't stop even after switching.
Replicate this bug by aiming down sights with the laser, looking at a surface close to you (the floor works). Fire the beam and while firing and aiming, switch weapons. Congrats, you now can't turn your camera.
Bonus points for convincing your friends for trying this bug. Also, just make sure you give the game a second between mining a node and switching weapons. Should stop this from happening.
-
Try removing either Primed Fury or your riven. I'm 90% sure this is because of your attack speed, which would explain why this issue seems unique to you. I don't have a riven so I can't test it myself. Hopefully that at least makes the zeni usable until it is patched.
-
Any Articula I equip with Spira Prime Crashes the game when you press "A" on them in decorating mode to change the settings.
I had 1 of 4 articula that would crash every single time. I eventually swapped Spira Prime with Sicarus Prime; no more crashes .I then equipped Spira prime to a different articula that had 0 problems before, and now that one crashes every time. Both the normal skin and Day of the Dead skin cause it to happen.
-
I've noticed this too, however it does not happen to me as the host, only as a client. The worse the ping, the further away the energy bubble is from where you land.
lith relics in high lvl bounties is it normal?
in General
Posted
It is supposed to be an Axi O3.
The specific bounty is the level 40-60 Rot B. In the drop table it lists the relic drop as being an Axi 03, however in game when this rotation comes up, the game displays a Lith v5 as the reward. Perhaps it's an xbox exclusive issue since the drop tables are gathered from the PC version.