Jump to content

(PSN)Eneokun

PSN Member
  • Posts

    253
  • Joined

  • Last visited

Posts posted by (PSN)Eneokun

  1. Yeah, the rescure targets go instant rambo when they get a secondary in their hands... it's annoying. I still prefer to rush through the end, clearing the most enemies (when solo). When you are running with others, you ofc need to defend the target, unless you all run straight to the end at the same time.

  2. I can tell you how it happened, because it once occured to me as well. You were in a squad with some people, the mission was about to start and you notice its not the warframe you want to play, so you head to the arsenal. The mission starts in 3 seconds. You found the warframe, selected him within the last second the mission was about to start. You were unable to head back out to the mission screen, so your player information is not actualized. You play for few minutes, complete the mission, but you notice, the warframe is suddenly on max level. It is a glitch thats hard to simulate but I can confirm it with my Zephyr. She was lvl 27 and I did Lares for 10 waves or so. Even with boosters you couldn't make it to 30 there, in 10 waves. I noticed her suddenly being 30 at the mission completed screen, but back at the solar map I still had Nova selected (indicated in this player window on the lower left of the screen). The thing is that I'm not 100% sure, but I think that my Zephyr copied the level information (lvl 30) from my Nova in that moment. It's very strange, however. But I think that I did not receive any affinity from this instant up. I ofc did not check my affinity before and after since I didnt expect this to happen. Afraid of affinity loss I didnt test it with other warframes or weapons afterwards either. I thought I might be wrong, but another guy reporting this bug confirm my speculations on this.

  3. You know, there are 3 tabs for different mod builds in the modding window in the arsenal.

    This bug occured when I was creating a second mod build for Ash on tab "B".

     

     

    Here how it happened:

     

    I opened the modding window for my Warframe Ash, and switched to tab "B".

    I put in mostly the same mods as in tab "A", with the exception of abilities.

    Build A had 0 capacity left, Build B a capacity of 7.

    I wanted to put in the "Rush" mod, but since I only had 7 capacity remaining, I wasn't able to put in the maxed version of the mod, as I did on build "A". So I put in an unranked one, which I wanted to upgrade with fusion cores. (Note that I did put it into the slot before I did the next step).

    In the upgrade window, I picked the unranked "Rush" mod and tried to fuse the mod with fusion cores, but the following message appeared:

     

     

    "Fusion not possible: The installed mod would exceed the capacity of ASH (config A)"

     

    The thing is, I do have a maxed "Rush" version on build A and 0 capacity left.

    But the one I picked to upgrade was 1. an unranked version of the mod and 2. in build "B".

    The mods were both of the same kind, but they were different cards of different ranks.

     

    Now I wonder if it's the capacity of the builds or the mods that are conflicting here when upgrading the mod.

    Because actually this message is not supposed to show up when working with another mod build and a mod card that has a different rank.

     

     

    My solution for the moment: I made some free capacity on build A, saved, and then upgraded the unranked Rush mod. Then put back in the mods desired into build A, with 0 capacity left. When I did it like that, the message did not show up.

     

    Again minor but annoying bug.

  4. This game is TRASH,,  been stuck on lvl 4 for 2 weeks._ always fails to login, never saves progress after mission, WTF YOU STILL PLAY THIS TRASH YOUR JUST AS FKN DUMB AS THE MODS GIVING FALSE BS REPORTS.

     

    So you've basically only signed up to insult the staff? You are pathetic. But at least you got the point, that you don't need to play it, if it annoys you too much.

  5. Bugs are part of this business and some require more time to fix. But some people don't understand that. This is sad. Because instead of complaining they should provide helpful reports or just wait for things to get fixed. Easy as that, if it annoys you, go play something else. Complaining won't get you far, maybe not even noticed. I also had to learn this by myself...

  6. Yeah, even though the rage is well founded, the staff is already under heat and players that keep posting the same again are no help for this. Actually it's pointless to do it. Just stop wasting time and effort in farming and play on the low tiers, if you want to play at all, until it gets fixed.

  7. mhh... I noticed this happening to me once as well.

     

    I invited a buddy to a game and we did the mission. Afterwards I tried to invite him again - it failed.

     

    It could be a problem of ports, but this ordinary does not happen to me when I play with chosen players from my buddylist.

    Actually the bug mentioned happened only 1 time at all.

     

    What are your connection settings, ports and ping limit and did you change them? 

  8. C. Grineer space Ship. " big cannon room" , small fenced ramp, large ramp on other side with side shelf

    that holds a life support capsule, life support capsule on top, life support capsule lower end down by the windows, cannon barrels.

    The issue is the Grineer that are killed in this room do not fall, they are like frozen in position, but dead.

    This has been going on for quite a while now. Only happens in this room, consistently.

     

    This bug does not occur only there, it can happen in any mission. Confirmed.

×
×
  • Create New...