about 2 months ago - /u/slayerdk-PHX - Direct link

We are working hard to quickly resolve live issues. For more help, contact support @ support.playdauntless.comPlease also keep an eye on the current tracked issues @ https://favro.com/organization/e5b8ad4a71148d7b5940992b/f86fee6bdc9be495922f7de2- Phoenix Labs development team.

Greeting Slayers!

Welcome to the Bugs Megathread where you can report bugs that you encountered while playing Dauntless. With every patch, comes with unforeseen bugs that can find their way onto our airships and into gameplay. To avoid flooding the subreddit with similar issues, we are collecting all bug reports in this megathread to consolidated incoming reports. This will be the place to post all bug reports until a new Bugs Megathread is made. This is to provide both the developers and the community a thread focused solely on bugs.

Prerequisites before reporting a bug

  1. Provide screenshots or a videos capturing the bug if possible. This would greatly help the devs validate the bug report. You can upload your screenshots/videos to Google drive and include the link in your comment below. Please make sure your sharing settings for that file/folder is set to "Anyone with the link", otherwise we won't be able to see it.
  2. Give as much information as you can. This helps the devs recreate bugs on their end and discover if the issue is localized to specific
  3. Knowing the session ID in which a particular bug occurred in would help as well.

How to Format your Bug

  • In-Game Name:
  • Type of Bug: Behemoth, Weapon, Gear, Performance, Cosmetic / Visual, etc.
  • Expected behavior: What were you expecting to have happen?
  • Actual behavior: What did you see happen?
  • Screenshot/Clip: Provide a video or screenshot of this bug happening.
  • Reproduction Rate/Steps: Are you able to reproduce this bug? How often does this bug occur? (1/10 : Occurs once every 10 tries, 5/10 : Occurs 5 times out of 10, 10/10 : Happens every single time)
  • System Specs: Internet speed Operating System, CPU, GPU, Internet speed, or Console.
  • Geographic location: Provided this so we can track which server you are connected too.
  • Session ID: (Optional). For bugs that occurred in a particular session/s.

Every comment might not be addressed, but rest assured that the devs go through every single post. Before commenting, please aim to upvote comments that are the same or similar to an issue you have experienced in-case someone else has already posted.

External link →
about 2 months ago - /u/slayerdk-PHX - Direct link

We are working hard to quickly resolve live issues. For more help, contact support @ support.playdauntless.comPlease also keep an eye on the current tracked issues @ https://favro.com/organization/e5b8ad4a71148d7b5940992b/f86fee6bdc9be495922f7de2- Phoenix Labs development team.

Greeting Slayers!

Welcome to the Bugs Megathread where you can report bugs that you encountered while playing Dauntless. With every patch, comes with unforeseen bugs that can find their way onto our airships and into gameplay. To avoid flooding the subreddit with similar issues, we are collecting all bug reports in this megathread to consolidated incoming reports. This will be the place to post all bug reports until a new Bugs Megathread is made. This is to provide both the developers and the community a thread focused solely on bugs.

Prerequisites before reporting a bug

  1. Provide screenshots or a videos capturing the bug if possible. This would greatly help the devs validate the bug report. You can upload your screenshots/videos to Google drive and include the link in your comment below. Please make sure your sharing settings for that file/folder is set to "Anyone with the link", otherwise we won't be able to see it.
  2. Give as much information as you can. This helps the devs recreate bugs on their end and discover if the issue is localized to specific
  3. Knowing the session ID in which a particular bug occurred in would help as well.

How to Format your Bug

  • In-Game Name:
  • Type of Bug: Behemoth, Weapon, Gear, Performance, Cosmetic / Visual, etc.
  • Expected behavior: What were you expecting to have happen?
  • Actual behavior: What did you see happen?
  • Screenshot/Clip: Provide a video or screenshot of this bug happening.
  • Reproduction Rate/Steps: Are you able to reproduce this bug? How often does this bug occur? (1/10 : Occurs once every 10 tries, 5/10 : Occurs 5 times out of 10, 10/10 : Happens every single time)
  • System Specs: Internet speed Operating System, CPU, GPU, Internet speed, or Console.
  • Geographic location: Provided this so we can track which server you are connected too.
  • Session ID: (Optional). For bugs that occurred in a particular session/s.

Every comment might not be addressed, but rest assured that the devs go through every single post. Before commenting, please aim to upvote comments that are the same or similar to an issue you have experienced in-case someone else has already posted.

External link →
about 2 months ago - /u/Cinco4706 - Direct link

Originally posted by -eXiGe-

Occasionally when using tempest, the dash will go twice as far as it normally would.

Hey there, can you please check out this article that will show you how to capture it if it happens again, and send it into the support team on the same page? We'd be happy to take a look!

https://support.playdauntless.com/hc/en-us/articles/4416116305563-How-to-capture-and-report-bugs

about 2 months ago - /u/Cinco4706 - Direct link

Originally posted by noocarehtretto

• In-Game Name: marill404

• Type of Bug: Performance I guess

• Expected behavior: the game not to crashed when going back to Ramsgate

• Actual behavior: if I'm in a hunt or escalation when go back to Ramsgate the game freeze or crashed. I have to restart the game. At least I can travel between islands. It's been like this since 1 or 2 weeks. This happened when I play on my Switch.

I already reported this in game but I haven't see this bug on Favro and I saw a few people who has the same problem as me. If possible, I would appreciate an update if t5y666y666

• Reproduction Rate/Steps: 10/10, going back to Ramsgate from a hunt or when the escalation is over.

• System Specs: Switch

• Geographic location: Canada (ET)

Much appreciated, we're looking into this one as it appears to be happening to several people, no ETA on a resolution yet.

about 1 month ago - /u/joshlhood - Direct link

Originally posted by ModsCanEatMyShorts

Type of Bug: Challanges

Expected behavior:
Week 12 challange; Poision Prevention.
Break 25 fire sacs from Sporestruck Charrogg while Aether-charged.
Even if the text for "fire sacs" is not applicable to Sporestruck Charrogg.
It made no sense at all when I read it. Was hoping for it to just be a tooltip error, since they are in essence the same behemoth.

Actual behavior:
Destroying fire sacs for Sporestuck Charrogg AND Firebrand Charrogg and for the heck of it, even baseline Charrogg does not count towards challenge completion.
Tested in private against all three, making very sure to only attack when aether-charged..
The obvious tooltip error... is an actual error.

Reproduction Rate/Steps:
It is... 100% reproducible. It is right now a broken, uncompletable challange.

Thanks for the report - we're not sure what happened here as we were tracking this as working fine (and the odd naming of the part was a known issue we couldn't address any time), but I've now removed it. Thanks for the report!