Jump to content

KosmicKerman

PC Member
  • Content Count

    179
  • Joined

  • Last visited

Community Reputation

105

About KosmicKerman

  • Rank
    Gold Novice

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. People were using snipers or arch wing and not getting credit. 200 meters isn’t that close in the open world.
  2. Another way to look at it is that you are sacrificing strength by refusing to run blind rage or transient fortitude in Rhino. In my opinion, Rhino’s kit is much better served by strength than by efficiency or duration. That said corrupted mods aren’t always the right choice when you are first starting out and don’t have mods to offset them like primed continuity or don’t have easy access to energy regeneration. Besides having mods with negatives can force you to make interesting choices.
  3. Not surprised to see this thread still going but isn’t it time to switch to the “Speedrunners are ruining Warframe” one? Or maybe “Mesa is ruining my enjoyment of the game.”
  4. DE - I think it's fine that you periodically rebalance rivens as updates to the game require it. I'm not okay with rivens being changed when there aren't any changes that warrant a rebalance. While the last riven rebalance was painful, I was okay with it as many rivens needed to be balanced or hadn't had their dispos changed in a while. Last time I had a rubico riven and a catchmoon riven that were hit hard. Like I said, I accepted it because I agreed a rebalance was in order. They have been nerfed again without any changes to the game that require it. I have no interest in burning resources to reroll rivens if their stats will be slowly reduced at each rebalance. Why bother burning Kuva if it ends up being better to use a damage mod rather than a riven in that slot.
  5. Most, if not all, are intentional. You would be better off providing a list of those enemies.
  6. To be fair, it makes perfect sense to post a “Coming soon” thread the day after posting a thread announcing the event and 8 days before the event. One can understand why this might cause confusion.
  7. Reset your controller bindings to default. I am not experiencing any of the problems you claim. I can slide. I can aim glide. And I can do blocking combos by using the left trigger. I’m also pretty sure I responded to you the last time you posted this. The problems you are having are not universal. Reset your controller to default and everything should work fine.
  8. My controller works fine. If the problem is with a steam controller maybe try the fix discussed here:
  9. Before melee 2.999, I had block bound to left trigger on my controller. After the update, I reset my controls to default and then rebound them. I am able to do the blocking combos by using left trigger. I don’t know if this is result of previously having left trigger bound to block or if that is the new default config. Regardless if you have not already done so, I highly recommend that you reset your controller to default. It seems like anytime DE makes substantive changes to controllers it breaks the bindings in funky ways and they need to be reset to default.
  10. This is understandable and most of the community gets this but: 1) Even with the phase 1 skip, the fight still takes a long time. One might even say too long since it can’t really be optimized 2) Due to the P2P nature of the game, the fight can take even longer due to canisters not hitting the orb during phase 1 due to latency or packet loss from the host. This is something which may not have been obvious when DE tested in house. 3) There are serious bugs in the fight and in Warframe in general which can cause players to lose progress/rewards. Making the fight take longer just exacerbates this issue. I’ve personally lost all rewards following a tridolon bounty due to buggy matchmaking. Supports response was that I could ask for one thing out of the rewards. These sort of bugs and responses color the community’s responses to these types of “bug fixes.”
  11. Yes, the problem which must not be named is very serious. Please fix. Halp.
  12. Yeah, weird stuff happens when DE changes the defaults for controllers. The only repeatable fix I've found is resetting to default configuration and then rebinding. Sometimes you have reset to default, quit, relog, and then rebind to get the changes to stick.
  13. Try restarting your computer. I had the same problem and a reboot fixed it.
×
×
  • Create New...