FatsharkJulia

FatsharkJulia



02 Jul

Comment

Hmmm, I see. Try logging out and back in, clearing your cache, etc.

Comment

You appear to already have access - see here.

Comment

Forum access will be open shortly before the second phase of the Winds of Magic Beta starts, so later today.


01 Jul

Comment

Sorry to hear this. Unfortunately we don’t have any solid solutions for the COULDNT_RESOLVE_HOST error at current as we’re still in the process narrowing down the causes.

The solutions listed here may help.

Comment

The initial crash is an issue on our end, although you appear to be the only person to have ever experienced it so you’ve been particularly unlucky here. I’ve raised it with development nonetheless.

As for the second crash, unfortunately it’s not entirely clear as to what could be causing this. It would be helpful if you could continue to send us crash reports.


29 Jun

Comment

Unfortunately the log is cropped at the end and lacking the crash data we need to see. Should this occur again, could you please send us the contents of the crash report window? What we really need to see is the long ‘GUID’ string. :slight_smile:

Comment

I suspect this is an issue on our end which has been patched in Internal Test, I appreciate it’s an inconvenience but it may simply be a case of waiting on Internal Test to be pushed live. :frowning:

Comment

I can certainly see a correlation with your crashes and Steam Authentication.

We need to be able to reproduce this on our end, so I’ve asked our Engine Developer as to how we should proceed.

Unfortunately we’re not able to recommend any solutions, as it’s something we need to look in to. Sincerest apologies for the inconvenience.

Comment

In this situation I would recommend that your buddy reaches out to Easy Anti-Cheat directly using the link here, and includes a copy of the problematic DLL. They will be best suited to assist in this case.

Comment

The RECV_ERROR is usually a result of using the Internet Protocol Version ‘IPv6’, which I appreciate isn’t the case for him.

Is he using a VPN, or anything else that could be interfering with his connection?

Comment

Sorry to hear this, I’ve raised your report with our Console Developers.

Comment

Oh, I’ve upped your permissions level so you should be able to PM me now.


28 Jun

Comment

My apologies @starkwaizer, the person I need to speak to is on vacation until Monday. I hope to have an update for you next week.


26 Jun

Comment

This isn’t a known issue no, we can see if we can manually mark the prologue as complete on your account - could you PM me your Xbox Gamertag please?

Edit: Actually, is the installation still in progress?


25 Jun

Comment

We haven’t made any changes that could suddenly result in an influx of crashes, so I suspect this is more of a localised issue. Have you restarted your PC since the crashes began?


21 Jun

Post

I quite liked John Wick: Chapter 3. I also realise whilst writing this, that I haven’t seen many movies this year…

What’s the best movie you’ve seen in 2019 so far?

Comment

This is a DNS lookup issue, but it’s very odd that this hasn’t resolved itself yet!

I’ll chat with our Network Engineers next week to see if there’s anyway to clear it manually.

Comment

This error does seem to be isolated to our Russian players unfortunately, but I’m surprised you’ve had no success using a VPN based in another country.

I’ll have to query this with our Network Engineer, but unfortunately due to the weekend there’ll be a delay until next week.

Please let us know if anything changes before then.

Comment

Sorry about this - I’ve raised your issue with development.

P.S. This is likely unrelated to what you’re experiencing, but I couldn’t help but notice your GPU drivers are outdated by at least 1.5 years. Worth keeping them up-to-date. :slight_smile:

Comment

Please copy and paste the crash report produced in here.