Siela
-
Posts
13 -
Joined
-
Last visited
Posts posted by Siela
-
-
I was having that issue with accounts not saving, thank you so much for the fix<3
-
Oh yeah, leaving my Drakgoon unmodded works fine, it's only if I add something to it like you. Harpak and Kulstar work fine for me though.
-
I can cause it to give me the error by just starting a random mission (I've been using Neruda, for the record) on mercury and immediately aborting as long as I'm using a modded Drakgoon, which is how I so quickly tested all sorts of variables like paintjob slots, loadout slots, and warframes. None of those affected anything, but I thought it would be good to check.
Point being, if anyone can replicate it with any specific items, you can rapidly test it by just aborting missions.
If you're getting the bug to occur regardless of what you use that's fine, but I can easily replicate it with specifically the Drakgoon and nothing else so far.
-
Normally I'd assume it is and did assume for the past couple days, but it being a server problem on their end doesn't explain why it happens reliably every single time I test it on the Drakgoon, but doesn't happen with other weapons :P
-
let me know when you find what is causing it for you so i can add it to the ticket and this post.
The Drakgoon with any mod under any loadout reliably causes it to happen, but I just got one with the Harpak and I can't replicate it. That's all I got.
-
So is it different for everyone what causes it then? What a strange bug.
I'd test it with Equinox but I have yet to get a Night Systems.
Edit: Now that you mentioned it happening with Equinox appearance config B I decided to test that with the Drakgoon since I use B config on it as well, but no, it errors on all 3 configs, as well as on any Arsenal loadout slot.
Edit2: Changing the "visible when holstered" option doesn't help.
-
I'm beginning to narrow down what might be causing this, at least on my end. Seems to be related to adding mods to my Drakgoon.
Alright, so it seems adding ANY mod to the Drakgoon causes it to not save my progress.
Every time, reliably, adding even an unranked Seeking Force causes it to not save my progress. Public and Solo mode both do it, and it doesn't matter if I use only my secondary throughout the mission. Using the Boar Prime fully modded is fine, it saves normally. Using a blank config on the Boar Prime and adding a mod is fine.
That explains why I was getting it so frequently like I mentioned in my first post, because I've been trying to level up the Drakgoon. For the longest time it was too low level to add any mods to it so I wasn't getting the error, but now that I can fit my primed Point Blank on it, when I'd go to level it up more I'd get the error every time. Then I'd forget to add the mods back on because the error removes them, and I wouldn't get the error.
-
I'll keep a tab open with this thread, would be appreciated if you'd put their response here whenever they get around to it :P
-
I'm getting this too on something like 70% of missions I do. Mod I didn't have yet got deleted because of it. I'd create a support ticket but I don't feel it's worth clogging their inbox with a "what do?" message.
-
Awww sweet, you guys fixed that weird melee holstering bug. Thanks for the fixes guys ^~^
-
With the Redeemer equipped and having swapped to it and having it as your active weapon, picking up an Excavation power cell and then dropping it off at either the scanner or an excavator completely bugs the Redeemer out.
It sets your equipped weapon to your secondary and all Redeemer quick-melee strikes mimic the animation of the last strike you performed. For example, if you pick up a power cell and then complete the basic E-E-E combo, the last attack you performed was the swing followed by the shotgun blast. If you then go and drop off your power cell, every time you press E you will perform that last swing and shotgun blast while skipping the rest of the combo. It also doesn't seem to properly deal damage, with the swing seeming to deal 100 impact that isn't timed with the animation and the shotgun blast dealing full damage, but nowhere near your crosshair, sometimes even behind you.
Swapping weapons fixed it, but only until I bugged it out again.
Also, I occasionally got the already bugged out melee swings to completely give up on reality and do this (Not sure how to reproduce this one, took me at least 15 mins of restarting the mission trying different things to get it to happen a second time), also, the voice is of the person I was playing with. For some reason my own voice didn't get recorded, but whatever:
Keep in mind I was pressing nothing other than WASD and my sprint key during the video, I wasn't pressing any attack keys. Kills while in this state dealt extremely rapid ticks of 100 impact damage, and for some reason counted towards the Pistol Kills challenge.
Screenshots from another player of what I looked like to him during the events of the video:
-
Map Holes & Environment Bugs: Screenshot Tickets
in Mission Specific
Posted
761754
Missing collision in asteroid base mobile defense room