Jump to content

3mptylord

PC Member
  • Posts

    271
  • Joined

  • Last visited

Reputation

416

1 Follower

Recent Profile Visitors

875 profile views
  1. Again, the Personal Modifier doesn't say that it disables Transference - it says that it disables Operator Mode. Perhaps if the wording was "Disables Transference" I would agree that disabling Necramechs is implied but--again--that's not what the description says. Again, "the description not accurately describing the effect" is what I am reporting.
  2. The effect doesn't say it disables transference - it says it disables Operator Mode. You can unlock Necramechs before you unlock Operator Mode - so they are not dependant on each other in other places in the game. This is why the report is that the effect is undocumented. I am making the report because there's no reason for a player to expect this undocumented behaviour, even if we assume the undocumented behaviour is intentional.
  3. This is the second week of Transference Distortion and the issue is still present - so I've overcome my Bystander Apathy that someone else must have reported the issue and decided to do it myself. Issue: Transference Distortion states that it prevents the use of Operator Mode. This has the undocumented effect of also disabling the ability to pilot a Necramech. Attempting to pilot the Necramech incurs an error saying "Ability use prevented". Expectation: Per the description, I have only opted to forgo my Operator Mode. I expect to still be able to use Transference directly on my Necramech. I have this expectation because it is possible to complete the Heart of Deimos before the Second Dream. My partner unlocked his Necramech and was using it before he unlocked his Operator (see below the diary I kept of my partner when he first started playing in 2023). The game already mechanically supports controlling your Necramech without "Transference into Operator and Drifter" and this mechanic is seemingly lore-friendly. As a player, I cannot know whether or not the issue is with the description of the Personal Modifier or the gameplay. The pessimist-in-me suspects that this is intended and that the solution would be to update the description of the Personal Modifier, but I personally think that disabling Necramechs should be its own debuff (either Personal or Mission-specific) or tied to the Gear Embargo modifier. P.S. Shouldn't the description say either (a) Operator or (b) Dreamer or Drifter? Surely the current wording is the equivalent of saying "Do you like Fruit or Oranges?".
  4. With Styanax's Nipple Tassels using Attachment Colours instead of Warframe Colours (contrary to the examples listed above), jealousy inclined me to bump this post.
  5. This was previously reported in the Echoes of Duviri subforum, which is no longer available. The UI depicts them as small corridor sized rooms, but as you can see from the following screenshot: I am unable to place a second portal (the left room) adjacent to the first (the right room I've already constructed). In the DevStream and Patch Notes you really sold the fact these rooms use portals to transfer you to the landscape - but so far as I can tell from the minimap and the space the rooms occupy, the portal is purely aesthetic and you need to budget space for the islands. Could you please update the Dojo UI to accurately depict the amount of space that these rooms require and/or actually make the "inside of the portal" intangible for the purposes of placing other rooms? I'll admit that I'd really hyped myself that I was going to be able to put these portal rooms in the deadzones of my floorplan - but with these rooms being on-par with the Earth Chamber in size and only having one entrance, I don't actually know where I'm going to fit them without creating loads more deadzones. Here's another screenshot provided by another Tenno in the previous thread:
  6. Previously posted as feedback. Reproduction steps: Go to Settings Set "Hide UI in Screenshots" to true. Set "Show FPS" to true. Close Settings. Press F6 (or whatever you have the client-screenshot button bound to). Check your Screenshots Folder. Result: Expectation: The FPS panel should not be visible within the screenshot. I should not have to disable the FPS within the settings to take screenshots.
  7. I could have sworn they said/showed Necraloid now being in the Sanctum. Maybe we've all missed the secret.
  8. It seems to get disabled automatically when you have the Captura Settings open (I have the UI hidden in screenshots) - is there a way to enable this setting globally? I have tried toggling the Bloom and Glare settings, but they have no effect. EDIT: Sorry, to clarify, I mean in Captura. Deimos is much more visible in "real life": P.S. Is Captura using the new lighting system?
  9. A mod can move this to the bug report category if they consider this a bug report rather than a feature request. This isn't a new issue this patch.
  10. "Remember me" requires Cookies. If you have declined Cookies or your browser clears them when closed - that is why you keep logging out. Some AdBlockers also clean-up cookies - so just checking your browser's settings might not be sufficient to prevent them from being deleted.
  11. For example, here are some screenshots with the "Hide UI" option enabled:
  12. This bug was encountered on the Armatus tileset. We encountered the bug in two missions in a row. We have not explicitly tested versus other status-capped targets. My team mate is running +4 Max Corrosive Stacks. I am not. When my team mate engaged the Necromech Demolitionist, it would reach 8 stacks of Corrosive (the usual cap of 4, plus 4 from her Archon Shards). When I engaged a Necromech and she turned up after, the Necromech wouldn't exceed 4 stacks of Corrosive. We explicitly tested whether the order that we engaged the Necromech made a difference. She had remarked about 8 stacks of Corrosive being one of the few ways we'd found to strip Necromech armor in the various experimental squads we'd run, and immediately noticed when the enemy was stuck at 4. We did not explicitly test if the debilitating factor was the Warframe who applied the 1st stack or the 4th stack. We did not explicitly test if the debilitating factor was the host versus the client. I am like 75% confident that she (with the Corrosive Shards) was hosting, although it could have been our third premade. Either way, I was a client.
  13. The archwing blink. Double tap Shift or use your Roll hotkey if you've bound one.
×
×
  • Create New...