Jump to content


PC Member
  • Content Count

  • Joined

  • Last visited

Posts posted by Zezmeril

  1. While mucking around with subsumed abilities, I ran into a peculiar bug concerning modding. The coarse of events that led to this are as follows. Had Pull put onto Config A to test the ability with the augment Greedy Pull placed in the build. Decided to swap the setup over to Config B. Without removing Greedy Pull, I want into the Helminth room, removed Pull from Config A and placed it onto Config B. Went to swap back to Config A and got 2 prompts saying "Aura mod can only be placed in Aura Slot."  This image is what became of the build after clearing the prompts.w4rN8BL.jpg

  2. Yah, I watched the whole thing as well. Just logged in today to see if it finally went through, but it seems to have not worked at all. Had a similar issue with the Dax Bust for the sacrifice campaign, but I eventually got that after watching a lesser known partner's stream


  3. While running a mission on Hydron, a team mate had the G3 attack them. After being downed, one of the G3 started to capture them. Once the team had disrupted the capture process, they were able to be picked back up. Inserted below is the result.



  4. 939b579e403f409160a0b4ebf7f10efc.gif

    As shown in the .gif, whenever I place a mod into the left most mod slot on the bottom row, it starts ignoring all other mods slotted into it, including stance once I'm in a mission. The issue persists when switching to config B and C as well At the same time, I can not remove the equiped sugatra from it without switching to a different appearance configuration. The parts used to make it are Mewan, Kroostra, and Vargeet II Ruhang. So far, this has been the only zaw to do this for me.

    EDIT: Forgot to mention that this is on PC, though that probably isn't necessary.

  5. This issue seems to be caused by an enemy that can nullify your abilities deactivates the wall. I did a little testing and found that it happens whenever a nullifier touches them, and whenever scramba and comba mobs with the appropriate helmets get within range.

  6. Starting early this morning, I've been unable to get the launch to get past the "Check for Updates" stage. Every time I try to launch it, it will go for a few seconds, then promptly crash to the update failed page with windows popping up a "Warframe has stopped working" window. The only information I can get on the issue is the crash report I got form Windows crash notification, posted bellow. I have tried switching 64bit mode on and off as well as trying to verify and optimize  game cache. Whenever I would try to verify or optimize the game cash, it should throw up another error, identical to the initial crash.


    Problem signature:
      Problem Event Name:    BEX64
      Application Name:    Warframe.x64.exe
      Application Version:    2016.3.16.19
      Application Timestamp:    56e9ee67
      Fault Module Name:    StackHash_0584
      Fault Module Version:
      Fault Module Timestamp:    00000000
      Exception Offset:    000007fefc3e3d20
      Exception Code:    c0000005
      Exception Data:    0000000000000008
      OS Version:    6.1.7601.
      Locale ID:    1033
      Additional Information 1:    0584
      Additional Information 2:    05844721ba6f46935da4f741075b96d8
      Additional Information 3:    cfd7
      Additional Information 4:    cfd727e056ffff4bf82e32abe5e4efc5


    Just as an update, I am not constantly getting an application error saying it was unable to start correctly (0xc0000005)

  • Create New...