SChin

Hey everyone, Thank you for letting us know about this Bio! I have put in a bug report with all the information you provided and sent it to the QA and Area Design teams for a fix. If you happen to discover more about this, please continue to post it here as I will be linking this thread to the bug report to be used as a reference. Thanks again and sorry for the inconvenience with this bug, Bio.

Hey everyone! Thank you for letting us know about this Aaron! I've put a bug report together with all the information you provided and sent it to the QA and Area Design teams to investigate. It seems like the quest might be having issues when done out of the general intended order, but this should be fixable. If you notice anything else about this, please continue to post it here as I will be linking this thread to the bug report to be used as a reference. Thanks again and sorry for the inconvenience Aaron.

Hey everyone, I just got an email forwarded to me asking for an update on this. This issue was supposed to have been fixed so I just checked it out again due to the email. For me it looks like the change fixed a large portion of the issue, but I am seeing a couple of smaller sections where the layering is still an issue. I reassigned it to the Programming team for a fix so that they can get this completely fixed up. The bigger question to me is if this issue is still as bad for you as it once was for me, because after the patch it has been improved about 98% in my case(it was barely usable for me before). Thanks, and sorry for the bug still being present.

Hello Jww, Thank you for letting us know about this! I'll put a bug report together for this and see if the QA or Programming teams can get a reproduction case so they can fix it. If you happen to discover anything else about this, please continue to post it here as I will be linking this thread to the bug report to be used as a reference. Thanks again for the help Jww!

Hello Belfaldurnik, Thank you for letting us know about the issue in the Drowned Barrows. I'll put a bug report together with this information for the QA and Area Design teams to investigate. If you happen to discover anything else about this issue, please continue to post it here as I will be linking this thread in the bug report to be used as a reference. Thanks again for all the help!

Hey everyone, Unity got back to us about this issue yesterday and gave the Programming team some ideas for fixing these transition crashes. The programmers submitted their fix and it is currently undergoing testing to make sure it doesn't break anything else. Assuming the fix passes, it will likely be added to the next major patch. Keep an eye on the forums for the latest patch notes to see when the fix is implemented. It is likely to make it into the Beta Patch branch first if you want to play on that branch when the fix is in. Thank you for your patience with this long standing bug.

Hey Bartopolis, That detection circle definitely seems to be in the wrong location compared to the near by NPC. I'll put a bug report together for this and have the Area Design team investigate the issue here. Thanks again for all the help!

Hello again Rolandur, Thank you for letting me know about this! Do you happen to have a save file where this is occurring that the team could use for their investigation into the issue? If needed, you can find instructions on where to find your save files here. Thanks for all the help reporting these issues Rolandur!

Hey everyone, Sorry about this Daily Wage bug. We think we have found the cause of the issue and are looking to fix this as soon as possible. We could still use save files for our investigation if you happen to have a save where this occurred. If needed, you can find instructions on where the save files are located here. I'm not sure if you've heard about the work around for this, but everyone has been saying if you reload the save file, the issue doesn't recur and you keep your money. Thanks for the help and sorry for the inconvenience this is causing.

Hello Bartopolis! Thanks for another great bug report! Fortunately we've had this one bugged and a fix is already in the works. It is currently being Fix Verified by QA to make sure the fix is indeed working and that it doesn't break something else. Once that is taken care of, it should be ready for implementation into a future patch. Keep an eye on the forum patch notes to see when this fix is implemented into the game or when it becomes available on the Beta Patch branch if you want to get through this quest sooner. Thanks again for the help, and sorry for the inconvenience this bug is causing.

Hello Dave, I'm sorry you are running into a persistent freeze during your playthrough. Would you be able to reproduce this issue and then send us a copy of your output_log.txt file as well as the save just before running into this? This should help explain what is going on in the back end as well as provide an opportunity for the Programmers to reproduce the issue and see what is happening in the coding. If needed, you can find instructions on how to obtain these files here. If the forums say the files are too large, or if you prefer, you can send them to me at support@obsidian.net along with your forum user name and a link to this thread as a reference. Thank you and sorry for the inconvenience this is causing.

Hello Karf, I apologize for not getting back to you on the Steam forums yet. This weekend has had a major influx of forum posts and help tickets and I'm just finally catching up. This issue definitely looks like a bug and I can't quite tell if it is only visual or actually going to affect gameplay. Regardless of which situation it is, I would like to get this fixed as soon as possible. Would you be able to provide a copy of your save file where this is occurring so the team can investigate it in case they can't reproduce the issue in-house? If needed, you can find instructions on where to find the save files here. If the forum doesn't allow you to link the save file, or if you prefer, feel free to send it to me at support@obsidian.net along with your forum user name and a link to this thread as a reference. Thank you, and sorry for the inconvenience this is causing.

Hey Rolandur! Thank you for reporting this issue to us! Fortunately(or unfortunately) this has been an understandably common issue among players and we already have a fix in progress. The fix is currently undergoing testing to make sure that it works and that it doesn't break anything else. Keep an eye out for future patch notes to see when the fix goes live or when it becomes available on the Beta Patch branch if you want to test it out early. Thanks again for the help Rolandur, and sorry for the inconvenience this bug has been causing.

Hey everyone, I'm not sure whats going on with that, but I'll definitely bug this and have the Systems Design team take a look to see what is going on or what they want to do with these number discrepancies. Thanks for providing some insight to this with those examples Andrea!

Hey Thelee! Thank you for the heads up on this! I'll put a bug report together and get this sent off to the QA and Concept Art teams to investigate and get a fix. If you happen to discover any others like this please let us know! As always, thanks again!

Hello Topologista! Thank you for letting us know about this Arkemyr impostor! I've gone ahead and put a bug report together to have the QA and Area Design teams investigate this bug. If you happen to have a save file from before talking to Arkemyr that you could send us, that would be wonderful! In case you need it, you can find instructions on where to find your save files here. If you could attach those here or send them to me at support@obsidian.net along with your forum user name and a link to this thread, that would be appreciated. If you do not have a save that has this available, no worries, the QA team can try to reproduce this. Thanks again for the help Topologista!

Hey Bartopolis! This was supposed to have been fixed before Deadfire released! I've reopened the old bug and have the QA and Area Design team investigating this issue. Thank you for letting us know about this Bartopolis!

Hey Thelee, I just wanted to be sure that none of your companions in or out of party who may have been wielding the axe died during that combat as their equipment would have been added to that loot list so it would't be lost. Thanks!

Hello Krustenbraten, Thank you for letting me know about this discrepancy with the Cipher subclasses! I've gone ahead and created a bug report with the information you provided and sent it to the Systems Design team for investigation and a fix. If you discover anything else about this, please continue to post your findings here as I will be linking this thread to the bug report to be used as a reference. Thank you for all the help looking into this issue, and sorry for the inconvenience it has caused.

Hello Arthoor, I apologize for the lengthiness of time its taken for this fix. I checked the bug database and see that the bug has been fixed by the Area Design team and is currently going through it Fix Verification status to make sure the fix is indeed fixed and that it doesn't break anything else. Assuming nothing goes wrong with the Fix Verification, I'd expect this fix to come out pretty soon. Thank you for your patience with this issue and sorry for the inconvenience it has caused.

Hello everyone! Izzia is absolutely bugged and fortunately we have a fix for this awaiting hotfix approval. Assuming everything goes well, the fix for this should be out very soon! Keep an eye on the forums for the latest patch notes to see when this fix is implemented. Thanks again for reporting this and sorry for the inconvenience it has caused.

Hey Thelee! I'm pretty sure this is a bug. I created a bug report with all the data you've graciously provided and gave it to the QA and Systems Design teams to investigate. If you discover anything else about this or any other Fig backer items, please let us know! Thanks again for all the help!

Hey Thelee! Thanks for the reminder on this one! This bug is still slated to be fixed but had taken a lower priority compared to some other bugs that needed fixing. It is still slated to get fixed in a future patch, so you should be able to see it in future patch notes once the fix is implemented into the game. QA has already verified the bug from your save and their own, so this is basically just waiting on the Area Design team to implement the fix before moving to the Fix Verification stage. Thanks again for the help!

Hey Bargoed! Thank you for reporting these bugs to us! Fortunately AndreaColombo let us know that the Character Sheet is being cut off again, so we have that assigned to the Programming team to fix. I do not have the lack of collision for the lake bugged however, so I'll be putting that in right now If you find anything else, please continue to post about them in the forums! Thanks again for the help Bargoed!

Hello Romaje, I'm sorry you have been experiencing this from the very beginning. I'm going to create a bug report for this and send it to the Programming team to investigate on your behalf. While they are looking into this there are a couple of things that we might need or suggest be done to make sure everything is up to snuff. If the game is crashing and providing that error message, that means an entire folder with crash files should be generated and that has even more data that would be very helpful to the programmers. If needed, you can find instructions on how to find that folder here. The folder should be labeled with the date and time of the crash and have the ouput_log.txt, crash.dmp, and error.log inside. If the forum doesn't allow you to attach the files, feel free to send them to me at support@obsidian.net along with your forum user name and a link to this thread as a reference. Other things to help us would be to make sure your video driver for your Radeon RX 580 is updated with the latest driver and that your Windows 10 operating system is also up to date. Though these steps sound too simple to be true, they do tend to help many users with compatibility issues. Thank you for trying these out, and sorry for the inconvenience this has casued.