Jump to content

[DE]Glen

Warframe Staff
  • Posts

    1,055
  • Joined

  • Last visited

Posts posted by [DE]Glen

  1. If you want to help debug you might try disabling GPU particles for a while to see we can rule them out as a suspect:

    The only downside is you might hit some other unrelated crash and you won't be able to know from the WAR-number - but since this is our most common crash *by far* if it helps it should probably be obvious.

    Scratch that -- we found a bunch of reports with them disabled so that rules out GPU particles as a suspect

    • Like 3
  2. We've been able to narrow down the issue and can confirm this is a problem with a specific ISP.

    If you have a PC you can confirm that you have this problem by:

    • Opening a command prompt and typing “nslookup api.warframe.com” 
      • if it reports 23.40.172.184 as one of the addresses, your DNS server is returning stale information and is effected. 
    • Unfortunately it seems there is a pool of addresses returned and you may not see the bad one immediately (this is why the game can sometimes work but then will fail at random).
    • Tip: press the up arrow and then enter to re-run the same command a few times – in normal circumstances the addresses resolved might change every 20 seconds or so.

    As others have pointed out in this thread there is a workaround: you don’t have to use the DNS servers provided by your ISP. You can switch to a free DNS server locally on your PC, console or on your home router: 

    One issue we encountered with overriding your ISP’s DNS server, however, is that it appears this ISP specifies IPv6 DNS servers as well – we’re still investigating but in some cases changing the IPv4 DNS settings didn’t work until either IPv6 was disabled or the IPv6 settings were changed in tandem with the IPv4 settings.

    Sadly, this is not the first time we’ve had this problem: in February we saw the same issue with this ISP. For some reason their DNS servers are returning stale addresses and ignoring the 20-second expiry we specify and have been returning a value that changed almost a week ago.

    The last time our network partners were able to rearrange some equipment so that the stale address returned by the ISP’s DNS server still worked but unfortunately this is not possible this time. Our network partners are trying to reach out to this ISP to tell them about their misconfiguration but since we aren’t their customers this has not been effective.

    We’re currently waiting to hear back from our network partner about their efforts to contact this ISP however if you want to try to contact your ISP yourself the key things to tell them are:

    1. Their DNS servers are sometimes returning stale addresses for api.warframe.com (and probably others)
    2. Specifically it should not resolve to 23.40.172.184
    3. This is not a problem for millions of people on connecting through different ISPs.
    4. Other customers impacted by this have successfully switched DNS servers to work around this problem.

    Thank you to those who have attempted to help other Tenno to find solutions in the meantime, hopefully the issue will be fixed soon but for now this is a solution that we can use. 

    • Like 9
  3. 17 minutes ago, Horactius said:

    Thank you for the updates! I didn't expect decorations to affect RAM usage when buying things in open world at all. Thank you for optimizing this 😃

    Edit: I wanted to add that clicking and then buying things seems to be more effective in increasing the RAM usage than clicking on something, returning, and then clicking on something new over and over again but I'm not 100% sure.

    The code has been dramatically optimized for the next update however your 2741 placed decorations will still tax certain parts of the purchasing UI to some extent. The problem is we need to cross-reference decorations you've placed with the products being displayed to show how many you might already own and this is complicated to handle things like bundles. It's also a temporary memory expense: once it's cross-referenced the counts it can release the memory for background cleanup so that number should drop down over time (this is, unfortunately, frame-rate dependent, so on slower machines that might take a few seconds)

    • Like 10
  4. 18 hours ago, Horactius said:

    Hi, sorry for the late reply. Yes, I'm still experiencing this and have managed around it ever since I know about the out of memory problem. I have communicated this with [DE]Purzzle but couldn't find anything that could've caused this yet after comparing setting and spec. Right now, I suspect that this have something to do with my hardware.


    Wow! Okay, what are you buying specifically? I'd like to clone your account to the dev cluster and retrace your steps if I can.

    Found something: just going to trade tokens with Father and then cancelling the purchase over and over bloats a lot of memory (but it comes down after) -- we'll optimize this now.

    Edit 2: it's related to the number of placed decorations in your ship which is why not everyone sees this.

    • Like 5
  5. On 2022-12-29 at 3:33 AM, Horactius said:

    I'm not sure if this is the bug you guys are after but I have something that might be related to it.

    I notice that my game keep crashing whenever I was buying multiple items from the store from open world NPCs for a while now. It's been getting more consistent too after I tried figuring out what made my game crash and in my case, it would almost always be crashing after buying at least 3 items from the store right after another and that's that. I didn't think much more of it until I saw this thread yesterday. Then I started paying attention to my RAM when I'm on open world and trying to buy items.

    This is a very interesting observation! Is it still happening for you? I tried myself just now and bought a whole bunch of stuff from Yonta and couldn't move the needle. I wonder if there's some sort of local setting that aggravates this.

    • Like 3
×
×
  • Create New...