Jump to content


PSN Member
  • Content Count

  • Joined

  • Last visited

Community Reputation


About (PS4)Nek_Food

  • Rank

Recent Profile Visitors

793 profile views
  1. So there I was at the console scrapping components blueprints from armaments to have the needed space for new ones because of the 30 slots limitation DE has (because of the rivenlike rng stats they have). I selected an pulsar mk III zetki of the many I had to scrap it and was fine. The game after automatically selected my built and installed at frond cannons Vidar Cryophon MKIII I had with 55.7 damage yet it showed in the scrapping info frame the next pulsar mk III zetki I was about to scrap. I pressed scrap and it deleted my Cryophon. I have video capture from my PS4 but I don't have an YouTube or other video service to upload it, any suggestions? For a moment I was really pissed and confused. Then I checked the video and I understood what happened. I put an second Vidar with 55.2 damage to build but I am really annoyed with a) blueprints drop rates b) rivenlike rng stats for components c) invisible blueprints capacity (because of b) d) scrapping components blueprints one by one instead of multiple selected e) finally scrapping the wrong built weapon while the info windows was showing the wrong information. Yeap because of all those bugs the game has. f) the game is lagging and the menus have become extremely slaggish. So everyone beware when you scrapping components blueprints.
  2. Yeap it happened to me as well on PS4 and in multiple missions. I just wanted to add that in one mission when it (the Shedu) stuck, I switched to my secondary - a kuva one (multi forma-ed for the MR not sure which one brakk or twin stubbas perhaps not sure which one, certainly not kraken as I don't have it yet). The thing I want to add is that when the Shedu stuck and was not shooting, my secondary had for quite some time infinite ammo and yes, without any need to reload. 🙂 But after a while when I realized what was happening and as I was trying to figure out if it was really a thing (shooting like madman, trying to reload a fully stuck weapon, switching weapons and all that stuff that make us happy), it unstuck by its own (don't know what caused it) and turned into its usual behavior with magazine and all ammo depleting as normal. Yet the Shedu continued to not firing and been stuck. I'm pretty sure I was solo in a Kuva Lich mission - despite the fact that I had the public option on (still no-one joined that run). 100% with my Smeeta kavat, Inaros and pretty sure Shedu (with Catalyst on) had the "standard" damage and mutlishot mods on (I think I can still check the build if needed because after I maxed it - rank 30 - I never used it again). Kuva Brakk or Kuva Twin Stubbas as secondary and Paracesis as my melee. Don't know if any of the above helps...
  • Create New...