Jump to content

CrYPTeX1337

PC Member
  • Posts

    63
  • Joined

  • Last visited

Posts posted by CrYPTeX1337

  1. The bug only occurs if you try to offer mods that you maxed out inside the dojo. If you level them up before joining, you can make the offer just fine. That's what I've worked out so far from my testing, because I ran into the same issue today. This is also the reason you can offer equipped mods just fine, because they were already leveled up before you joined the dojo. Anyways, this new bug is really annoying.

    • Like 1
  2. 32 minutes ago, Circle_of_Psi said:

    You'll get used to this, they can't NOT disappoint people at this rate

    The focus should always be to release polished content, even it that means delaying the original release date. People like you are the reason so many games during the last couple of years were hot garbage from the beginning, because you cry on forums/reddit about the devs taking too long with the release. I'll take quality over quantity any day.

    • Like 2
  3. While doing the Ambulas Assassination during today's Sortie I realized that the Condor Storm Dropships - those that are supposed to deliver the hacked Ambulas to the Corpus Ship - are way slower than usual. Usually when the two minute timer starts to count down they appear almost instantly and hover over the tile set for at least 40 seconds, which can be quite annoying if you don't disable their turrets. This time they were flying extremely slow and took the full two minutes to fly to the right spot and pick up the hacked Ambulas. Of course on their way back they were really slow as well, it felt like an eternity until the next wave of Security Teams could spawn.

    This 'new' flight speed is really annoying, because the Ambulas Assassination already takes at least 10 minutes which makes it one of the longest non-endless missions in the game. Now it takes even longer... that's not what I'd like to see to be honest lol.

  4. I just checked out the New Ash Leverian and found his Prex Card right behind his statue. After I checked my Codex to see whether or not the Card would appear in my Codex I saw that the image on Ash's Card is a little bit distorted. It seems like you accidentally used the full-sized image of his Prex Card for the Codex Entry as opposed to just using a little snippet of the image as is the case with other Prex Cards, which of course distorts the image since it's a little too big for the small box in the Codex.

  5. 1 hour ago, -BM-Attila.the.Hun said:

    So I was doing mission on space with clan mates, after finishing and extracting my clan mates got around 1200 scarlet credits (more or less) but after I went out of the relay I checked my inventory and found out that I didn't get any

    Same Problem here, it was an extremely laggy session (due to a S#&$ty host), we should have gotten 775 but i got only 90 or so...

    • Like 1
  6. Yes, yes and yes. The worst part is that most team members probably think I'm retarded because I'm not doing anything even if I explain it to them and can't do anything in reality 😄

    Due to this bug it can also occur that you're stuck forever in Operator and sometimes even walk through the air. This is getting out of hand.

  7. This is a huge problem for me currently during Eidolon Hunts. After I land from Archwing I can't use weapons (can't aim, can't shoot, can't switch weapons either) or use abilities, most of the time I can't even sprint as well. Only way of fixing it for me is dying and that only resolves it for 5-10 minutes if i'm lucky.

  8. I've got the same problem, as many others above i'm also playing solo (Invite Only) and used different Warframes. It can occur on almost every tile set - for me at least - and I lost probably already 30K Kuva today because of this. I've never had any issues like this up until today.

    Edit: it might have something to do with leaving the tile where the Siphon spawns to complete the main objective while the Siphon is already activated. I will test this further but leaving the Siphon's tile might glitch out the clouds/the Siphon itself.

    Edit 2: Nevermind, the Siphon can even glitch out if you're on the same tile.

    Edit 3: At this point I even had a "runaway" Kuva Cloud lol... just when I thought no more clouds were spawning and I have to restart the mission YET AGAIN I ran towards the extraction and what do you know... there's a Kuva Cloud floating towards the extraction (yes, that's correct! the cloud was floating away from the Siphon and had already travelled 200+ meters when I saw it) as well. Though this is the only time I was actually able to complete the Kuva Siphon Mission with a bugged Siphon, because usually hits on Kuva Clouds aren't registered at all if the mission bugs out.

  9. It appears that time spent in the orbiter or in the dojo (might be the case for other instances as well) gets added to the mission time if you start a mission, which causes an inflation of the 'time played' stat, which therefore accumulates mission time way too quickly. Maybe you can further look into this issue! 😄

  10. As I already described in my post under the 'UI' section 

    the data for my 'Failed Ciphers' Stat seems to be corrupted. I finally found the answer to what's causing the problem. I had the idea that - since I mainly play Railjack (and only as Engineer) for the last two weeks - it might have something to do with the usage of the Forge in the back of the RJ. So I went ahead and documented a complete ~1hr long farming run for MK3 Vidar Reactors. In the following I'll abbreviate a one-time use of the Forge (e.g. to check for current amount of resources in the storage) without any further interaction with 'F'. Furthermore: Crafting Munitions, Dome Charges, Flux Energy, Revolite --> 'C' and Refining --> 'R'.

     

    These were the results:

    F: 10x

    F+R: 4x

    F+C: 48x

    F+C+R: 3x

    which adds up to 65 separate uses of the Forge.

     

    My 'Ciphers Failed' before the mission: 1543

    My 'Ciphers Failed' after the mission: 1608

    As you might have guessed the difference is 65. Quick maffs (duh).

     

    To conclude: any kind of interaction with the Forge results in the 'Ciphers Failed' Stat increasing by one, which of course is not very nice if you're a perfectionist like me. I'd really like to see this getting fixed and my failed ciphers rerolled to a pre-Railjack state which is probably in the 300-ish range.

     

    Merry Christmas and happy holidays, may the Void bless y'all with precious Credits. 😉

  11. So I just checked my personal stats and stumbled upon something odd. I'm rather good at solving ciphers in a fast pace (average time ~5s) so it is kind of expected that I don't fail ciphers at all or just very, very rarely. Which definitely is the case. I mean I'll occasionally abort a cipher to kill a couple of Grineer Butchers slashing through my spine with their Dual Cleavers (those things really hurt) but other than that I don't fail ciphers as is the case with most of the players that... let's say play frequently. For the last couple of years my failed ciphers were sitting at 200-300 and at this point should probably be at 400 max with over 8500 ciphers successfully solved. But for some odd reason this time I checked my stats just out of interest the 'Ciphers Failed' Stat skyrocketed to an impressive amount of 1400+ failed attempts which I simply cannot explain. I don't really know what's going on, maybe you can help me shed some light into this issue.

     

    Best regards, CrYPTeX1337

     

     

    Edit: At first I thought that maybe the newly introduced Parazon Mod 'Auto Breach' had something to do with this but from testing in a Spy mission successful auto-hacks seem to count as 'Ciphers Solved' as they should.

     

    Update: When i posted this yesterday my total 'Ciphers Failed' count was 1423. Now it further increased to 1543. I haven't even hacked 120 consoles since yesterday, let alone failed a single one of them... this is getting crazy. Note that I've only been playing Railjack for the last two weeks, I suppose it might have something to do with using the Forge. I'm going to further investigate this issue.

     

    Update 2: I worked it out, moving the thread to the Railjack Bug Thread.

×
×
  • Create New...