over 2 years ago - /u/CreatureTech-PHX - Direct link

Server Status @ status.playdauntless.com
We are working hard to quickly resolve live issues. For more help, contact support @ support.playdauntless.com
Please 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
  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 →
over 2 years ago - /u/CreatureTech-PHX - Direct link

Server Status @ status.playdauntless.com
We are working hard to quickly resolve live issues. For more help, contact support @ support.playdauntless.com
Please 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
  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 →
over 2 years ago - /u/ChandyPHX - Direct link

Originally posted by JHFA92

no need to specify, the movement has been bugged for two weeks now.
It didn't change with this patch either and/or mentioned as a thing, so i assume it's a bug.

The movement is no longer true directional, but the character always wants to turn instead of face directly in a direction.

The easiest way to notice this, is pressing WASD in quick succession. Before the character would turn around on the spot and now (and for the past two weeks) the character will move left and right and hesitate on the inputs.

I'm sorry to say it, but it makes the game feel sluggish. Hope I didn't insult any of you, if this was intended (I sure hope it isn't)

There was an issue with axe rotation that we have fixed for the next patch, but this sounds like general movement which I can definitely bring up internally.

over 2 years ago - /u/ChandyPHX - Direct link

Originally posted by Nalin8

In-Game Name: Nalin8
Type of Bug: Event
Expected behavior: I should gain credit for completing events on Frostmarch
Actual behavior: I get credit for snowball fight, but no credit for snow fort events.
Reproduction Rate/Steps: 10/10
Geographic location: US West

Looking into this. Thanks for the report!

over 2 years ago - /u/ChandyPHX - Direct link

Originally posted by Nalin8

In-Game Name: Nalin8
Type of Bug: Weapon
Expected behavior: I expect to be able to consistently use my chain blade's special move.

Actual behavior: Sometimes, after I use my Reaper's Dance special, it uses all my momentum, but my charge bar is still 100%. When this happens I will never gain any more momentum as my charge bar won't convert itself into a charge of momentum, breaking the Reaper's Dance special until I switch islands.

Reproduction Rate/Steps: This bug doesn't happen every time. I haven't been able to identify what causes it. I am currently using the following build:
https://www.dauntless-builder.com/b/yKfETJBhBCMcdnujcmtYT8RhqcbC4cr3u7CM8caMTJCyxtguwCaLInSgvU0
It could be an interaction with the Revenant cell. It could also be caused by not using your special for a fight or two.

Geographic location: US West

I believe this is something we are aware of and looking into already. Checking in with designers to make sure. Thanks for the extra info!

Edit: confirmed fixed for next patch.

over 2 years ago - /u/tinouti - Direct link

Originally posted by der_Mechaniker

We are at Week 13 and there’s only one more week to go for Season: Call to Arms.

How will these bugged challenges be handled as far as seasonal progression is concerned?

It doesnt seem like there will be time for you to implement fixes and pass Xbox Cert., and with that being the case it will be impossible for us to complete the season successfully.

What‘s the thinking here?

Bugged Sahvyt challenges should be fixed now, give it a go! 🙌

over 2 years ago - /u/tinouti - Direct link

Originally posted by PrplGrl3

(This is a very time-senstive bug that should be made top priority, as it has to do with a weekly challenge that is bugged, and should be fixed before 2 weeks, before the deadline for the weekly challenges for the next and final week - week 14 - finishes, as if it is not fixed before then, will affect being able to unlock the character title from doing all weekly challenges during the Call to Arms season!)
In-game name: PaarsKrygers
Type of bug: Weekly challenge
Expected behaviour: When you complete a weekly challenge, it should say you've completed it by showing up on the weekly challenges as blue, and for all objectives to be completed in it.
Actual behaviour: One of the weekly challenges this week, in week 13, is totally bugged!! It's the one called Anger Blades, where you have to slay an enraged Sahvyt. Even though I have done that, this weekly challenges still appears grey on the weekly challenge page, as if I never even did it! :/ Please help, I like completing weekly challenges within the week, and especially really don't want to have to miss out on unlocking the character title by the end of week 14 (for completing all weekly challenge during the Call to Arms season), just because a bug prevented me from completing a weekly challenge in one of the weeks that I did correctly :/
Reproduction rate: 10/10, because I have slayed not 1, but 3 Sahvyts now, all while they were enraged, with the same result, no progress towards the Anger Blades weekly challenge counting. This is incredibly irritating, and driving me insane! >:( Any fix on this irritating bug asap would be greatly appreciated!
System Specs: PC, Windows 10
Geographic location: Australia

Bugged Sahvyt challenges should be fixed now, give it a go! 🙌

over 2 years ago - /u/tinouti - Direct link

Originally posted by elcor_parkour

Bug Report

In-Game Name: elcor_parkour

Type of Bug: Behemoth/weekly challenge/bounties

Expected behavior: to get credit for killing sahvyt when enraged

Actual behavior: nothing, no credit on bounty nor weekly challenge

Screenshot/Clip: https://youtu.be/w-hlgwlhH4Q

Reproduction Rate/Steps: Are you able to reproduce this bug? How often does this bug occur? 10/10 times. doesn't work when enraged or both enraged and aethercharged. I did this about a dozen times

System Specs: Intel i5-9600k CPU @3.70 GHz, Nvidia GeForce GTX 1660ti

Geographic location: NA-E

Bugged Sahvyt challenges should be fixed now, give it a go! 🙌

over 2 years ago - /u/tinouti - Direct link

Originally posted by Danielmbg

In-Game Name: Danielmbg

Type of Bug: Behemoth/Bounties

Expected behavior: Killing Sahvyt on escalations should count towards Bounties and Daily Challenges that require killing behemoths.

Actual behavior: Killing Sahvyt on escalations does not count towards Bounties or Daily Challenges.

Reproduction Rate/Steps: 10/10 Every Sahvyt I killed on an escalation did not count towards my Bounties or Daily Challenges.

System Specs: Xbox One, Canada.

Bugged Sahvyt challenges should be fixed now, give it a go! 🙌

over 2 years ago - /u/tinouti - Direct link

Originally posted by Yoyobunbuns

Sahvyt for bright wood Doesn’t seem to count for a lot of things. I’ve wounded it so many times and get nothing

Bugged Sahvyt challenges should be fixed now, give it a go! 🙌

over 2 years ago - /u/tinouti - Direct link

Originally posted by Soahtree

In-Game Name: Soahtree

Type of Bug: Behemoth, Challenge Progress

Expected behavior: Expecting credit for defeating Sahvyt with chain blades, expecting credit for dodging physical attacks from Sahvyt, expecting credit for 3x wounds in 1 Sahvyt fight, expecting credit for breaking all parts before defeating Sahvyt

Actual behavior: Progress towards completion of the associated Challenges does not occur

Reproduction Rate/Steps: Able to reproduce bug 100% of the time, in solo, in party, and in escalation over several separate sessions.

System Specs: 17 ping, 26 Mbps download, 31 Mbps upload speed. Windows 10. Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz 4.00 GHz, NVIDIA GeForce GTX 1060 6GB. Additionally have tried this on Switch and have been able to reproduce the error across sessions, with solo/team/escalation.

Geographic location: Washington state, USA

Bugged Sahvyt challenges should be fixed now, give it a go! 🙌

over 2 years ago - /u/tinouti - Direct link

Originally posted by CranberryInevitable3

In-Game Name: TombstoneZombie

Type of Bug: Challenges

Expected behavior: To track current progress on Sahvyt challenges.

Actual behavior: Reads 0/10 sahvyts slain

Reproduction Rate/Steps: 10/10

System Specs: Console

Geographic location: U.S East

Bugged Sahvyt challenges should be fixed now, give it a go! 🙌

over 2 years ago - /u/tinouti - Direct link

Originally posted by der_Mechaniker

• In-Game Name: Nixon Redgrave & Avitol Myopic
• Type of Bug: Weekly Challenge
• Expected behavior: Week 8: Bladestorming count increasing with Sahvyt Chain Blade kills
• Actual behavior: No kill count increase
• Reproduction Rate/Steps: 100% reproducible. Equip chain blades, kill Sahvyt, observe count remains 0/10
• System Specs: Xbox Series X&S
• Geographic location: CA, USA.

Bugged Sahvyt challenges should be fixed now, give it a go! 🙌

over 2 years ago - /u/tinouti - Direct link

Originally posted by LawmanBarry

In game name: Thezedd73 Type of Big: performance? Expected behavior: complete challenges once complete Actual behavior: the opposite of that Reproduction: Every time

Challenges not counting as completed when they are complete

Bugged Sahvyt challenges should be fixed now, give it a go! 🙌

over 2 years ago - /u/tinouti - Direct link

Originally posted by MrGrakan

In-Game Name: SirGrakan

Type of Bug: Weeky challenges

Expected behavior: challenges related so sahvyt counting

Actual behavior: they are not counting

Reproduction Rate/Steps: Everytime

Geographic location: Portugal

The slay sahvyt with chainblades and the dodge sahvyt attacks aint counting, the dodging counted 1st day but ever since that stopped

Bugged Sahvyt challenges should be fixed now, give it a go! 🙌

over 2 years ago - /u/tinouti - Direct link

Originally posted by Kr0nshi

In-Game Name: Kr0nshi

Type of Bug: Behemoth

Expected Behavior: Weekly Challenges to count Sahvyt dodges and kills.

Actual Behavior: Weekly challenges do not tick up at all when dodging Sahvyt's attacks, or killing him with chainblades. Have not tested the break all parts challenge.

Reproduction Rate: 10/10

I think this may have something to do with Sahvyt counting as Neutral pre-patch. The game doesn't seem to recognize "Shock" Sahvyt as the Sahvyt in the challenges and still wants "Neutral" Sahvyt.

Bugged Sahvyt challenges should be fixed now, give it a go! 🙌

over 2 years ago - /u/subiwatson - Direct link

Originally posted by AresThreeFive

In-Game Name: AresThreeFive

Type of Bug: Audio Issue

Expected Behavior: The swarm of bees from Kharabak to stop emitting a sound after they are gone.

Actual Behavior: If you come into contact with the Kharabak bee swarm the sound that plays with them will never stop until you leave the hunt.

Reproduction Rate: 10/10 happens every time I come into contact with the bee swarm.

System: PC Windows 10

We have a fix for this issue going into 1.9.0! A very annoying one indeed. Makes me think of the Nicholas Cage meme, NOT THE BEEEEES!

over 2 years ago - /u/tinouti - Direct link

Originally posted by Infernal_Niek

Name: Infernal Niek

Type of Bug: Weekle Challenges

Expected Behavior: After completing all the other weekly challenges to get the the final challenge "Call to Arms"

Actual Behavior: Did not get the "Call to Arms" challenge even after getting all the other challenges.

System Specs: Nintendo Switch

We unfortunately won't be able to fix this bug in time, so we'll be granting the title manually in a later patch to everyone who completed all challenges.

over 2 years ago - /u/tinouti - Direct link

Originally posted by tostane

Quest Tribulations Vii Test your might says wear krolachi basics armor the list disappears after you accept the quest. I have no idea what the complete set is now how can i do the quest ?
i found a chest and helm named same and a banner and flair but those did not work for the quest i have killed that mob 10 times and cannot get it to complete.

That's an unfortunate UI behavior, sorry about this. You should be able to easily find the items though as they are the only ones without no resistance values. Hope this helps!

over 2 years ago - /u/tinouti - Direct link

Originally posted by furine666

I have the same issue. After completing all other weekly challenges this one did not complete.

We unfortunately won't be able to fix this bug in time, so we'll be granting the title manually in a later patch to everyone who completed all challenges.

over 2 years ago - /u/tinouti - Direct link

Originally posted by Impossible_Deal6404

Hi, I'm here to report a bug.

The challenge called "Call to Arms" that is in week one, in which you have to complete all the challenges of the season to win a title, but I did not receive the title.

The video shows the evidence.

In-Game Name: Maximarcio333

Type of Bug: Challenges/Rewards

Expected behavior: That I receive the title.

Actual behavior: I didn't receive the title.

Screenshot/Clip: https://youtu.be/k7t2VbGZsSk

Reproduction Rate/Steps: Every time I play, the challenge is not complete.

System Specs: Internet speed 400 mbps, Windows 10 Pro ,CPU: i5-6400 2.70GHZ , GPU: GeForce GTX 1060 GB.

Geographic location: I currently play in Chile, country of south america.

Session ID: Every time I play, the challenge is not complete.

We unfortunately couldn't fix this bug in time, so we'll be granting the title manually in a later patch to everyone who completed all challenges.