ShaperOfForm
-
Posts
29 -
Joined
-
Last visited
Posts posted by ShaperOfForm
-
-
29 minutes ago, Jarriaga said:
So now you're moving the goalpost from "You can't mark cryopods" (Implying she could not do so before) to "What has changed is what you can mark"?
How does that address the fact that the previous function, now deemed "a bug", did exactly what it did it said but it's now suddenly a bug? Again, since the point is flying over your head, circling around the planet, and flying over your head 50 times more, I don't care about the actual ability being changed. If DE had a change of heart on what the ability is allowed to do then fine. My problem is them calling it a bug despite having direct in-game evidence from in-game text to in-game functions contradicting that label, which either shows a blatant lie on their end, or a terrible lack of communications with debuggers that don't actually play the game yet assigned to change it.
I certainly am not moving the goal posts and had no intention of implying she could not mark cryopods before.
It is possible for something to be a bug and still fall within the parameters of the tip description. Example is oplinks. DE stated they were not intended to be healed.
The tip before the fix was true. You mark an oplink and it would be healed. They removed the ability to heal oplinks and yet the tip is still true. You cannot mark oplinks therefore they cannot be healed. Any target you can mark can be healed.
Your assumption is that the fix put into place was not a fix. It was either a lie or the debuggers made a mistake.
The evidence being used against DE is the tip, but the tip is still true as it is written. If a Defense objective is marked it will be healed. That is not a lie. .
Did the debuggers make a mistake? I guess we can't definitively answer that, but the current evidence suggests this was not a mistake.
The evidence:
They fixed the oplink issue and while fixing that issue made further adjustments.
The adjustments they made are in line with other warframe heal abilities.
So no I haven't missed the point. A change was made and your response was to assume DE are liars, incompetent, or both.
DE absolutely make mistakes. We might find out this was one. What is the point of assuming the worst? If that's you feelings, why are you supporting a company you revile?
Why not choose being objective and rational instead of assuming people are just trying to screw you over..
-
1 minute ago, Jarriaga said:
So that's a "tips and tricks entry" (Implying wiki) rather than in-game text in her dedicated tips section?
See, that's the problem of arguing from a "common sense" high horse: You need to be factually correct in order to hold that position.
You do realize that tip is still true after the fix? If something is marked it heals.
The change is what can be marked. And what can be marked is inline with other warframe healing abilities.
What is not factual about any of that?
-
1 minute ago, Sovyul said:
i don't even play the game anymore, i'm just watching DE burn for their sins
Boy are they suffering. Thanks for hanging out in a forum for a game you don't play.
-
1
-
-
1 minute ago, nslay said:
Why say what was already said on page 1 of this thread. That poster tested it and claims it doesn't work.
Its cool mate. You don't have to believe me or anyone else. Just try it for yourself, but make sure you do it properly.
The target has to be marked with the heal icon.
-
4 minutes ago, Jarriaga said:
The tooltip says defense targets. It doesn't separate moving targets from stationary targets, and true to the wording that didn't discriminate, it worked on all.
If you need to add additional words in order to justify a "fix" that contradicts wording that did exactly what it said it did, you are grasping at straws.
In other words:
- "Works on yellow paint".
- "Yeah, but it was never meant to work on yellow shade 23".
The tooltip literally says "Venari's Heal posture can heal Defense objectives when marked!"
That is still what the ability does. If the target is marked they are healed. You can't mark cryopods. No warframe could heal cryopods.
They are being consistent.
Why are people so upset about not being able to heal cryopods. They self heal. There is no reason to cast heal on a cryopod.
Moving defense targets don't self heal. Those are the things you would want to heal. And guess what? You can!
-
16 minutes ago, SneakyErvin said:
But the change is a fix, since stationary targets have never been intended to be able to be healed with frame abilities. There are other ways intended for them to have their life prolonged, like DR buffs or shielding them with domes/catas. They've fixed several frames that have not interacted as intended with static defense objects over time. Those frames still work on non-static objectives.
A valiant effort mate. You'll be accused of being a white knight for just being rational and logical. This person you are trying to reason with is delusional and a strong sense of entitlement. They want to throw a tantrum and make sure everyone knows they are upset when they leave. Not worth the effort.
-
1
-
-
4 minutes ago, nslay said:
Nslay, I have no idea what you are trying to say. You didn't bother typing anything.
I am assuming you are pointing to me saying it works and others saying it doesn't.
I personally tested it and confirmed it works. Anyone that says it doesn't, must not know what they are doing.
Being marked means having the heal icon above the NPC. Point at an NPC and press 3 when using Khora and the heal stance is active.
-
I can tell some people here decided to react without all the facts or reading comprehension. Just grab the pitchforks and assume the worst.
The tool tip says marked defense targets are healed. So if you can press 3 and it gets the heal icon above its head- it will be healed.
What they fixed was non-moving targets cannot be healed. Meaning cryopods. Which self heal anyways and no other warframe ability heals them.
Go into a defense arbitration and you can heal the defense target all you want. Otherwise their health won't regenerate.
The heal now works as intended. The tool tip is still 100% true. Marked targets are healed.
Note: I just finished testing this to confirm. I am not making any assumptions.
Someone close this thread.
-
33 minutes ago, GoodEffort said:
Cannot melee after quick attack.
Please help!
Steam controller with in-home streaming.
The actions I took on a post above resolved this issue for me.
-
For those using a Steam Controller this is what has worked for me:
1.Changing the Steam Per-Game Input Setting to "Forced Off" seems to have restored my custom profile
2. In the Steam Controller Configuration on "Game" mode I used the legacy key feature to map the keyboard "E' instead of using the quick melee action
3. In "Melee Mode" I mapped legacy keys for Left mouse and Right Mouse on the triggers to simulate the shoot and aim actions, and then the legacy keyboard "E' for melee
4. I removed any mapping for channeling as I don't really use it. However, if I do map it, I will use the keyboard/mouse legacy button instead of the predefined actions on melee mode
-
PC Steam Controller.
Using the Steam Big Picture Button Configuration tool.
My custom profile will not work at all.
Update: changing the Steam Per-Game Input Setting to "Forced Off" seems to have restored my custom profile.
Will test further
-
Issue resolved with update. However, my steam controller bindings are being totally ignored.
-
I also cannot login with a Steam Controller.
You cannot get the "a" press to register with any device under any circumstances.
Please help.
-
1600x. Crashing constantly when hosting. Tried optimizing.
-
I have Ryzen 1600x. Optimized. Still crashing. Seems to be when I am the host of a match and someone joins.
Action Sets on Steam Deck are broken
in UI
Posted
I use a Steam Controller on my standard PC and am quite pedantic about the controls. Default controls are just terrible. Who doesn't put jump, crouch and slide on the paddles?
I have been experimenting with configuring my Steam Deck to mirror my Steam Controller.
I have been able to get my desired results on the Steam Deck with the following method:
Discard the games default configuration and action layers.
Set up a generic controller and build your own action layers. You need two.
The default action layer is mapped to the games mouse and keyboard keys as you like to play.
The second action layer is for menus. That action layer is mapped to the controller keys.
In both action layers, you map the select and start buttons to trigger the other action layer.
This way when you bring up the options menu, it will default to the menu action layer.
The select button is sacrificed to only trigger between action layers. There are scenarios where you will need to manually trigger the menu action layer when you have to press X to interact with something like the foundry.
I tested this method across regular missions, railjack, and open world. It seems to work just fine.
In the default action layer, you will need to configure the right track pad as a mouse to get responsive turning in a railjack.
Using the left track pad as a radial menu is great for the lesser used keyboard buttons like L, T, ESC, G, M.