SChin

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.

Hey everyone! Your concerns and suggestions have been recorded as suggestion bugs and sent to the Systems and Programming teams for review. Thank you Silverwar for posting instructions for other users! In regards to adding more God Challenges, we have been releasing a couple every few patches and have more to come, with my favorite challenge still to be released in a future patch! Stay tuned to the patch notes to see when these are implemented into Deadfire! Thanks again for your thoughts and suggestions! They help to make Deadfire even better for everyone!

Hey everyone, From my understanding, there is a bug here. I put a report together for it from a previous post and it is on Area Design and Programming for a fix. After reading some other forum posts about this, it sounds like a Fog of War issue, and I've read that you can move away from the NPC to kite them out and then see them to kill them. Thank you for posting bugs and sorry for the inconvenience this may have caused during your playthroughs.

Hey everyone, Sorry for the lengthy fix on this. We still have this active in our bug database to be fixed and have prioritized other fixes above it so far. Needless to say, this should get fixed, it's just a matter of when. You should notice the fix in future patch notes when it has been implemented into the game. Thanks for the reminder

Hello Cromagnon, I'm sorry you crashed and can't get back into the game. If you could send anything pertaining to this issue to support@obsidian.net along with your forum user name and a link to this thread as a reference that would be great. Things that would be useful would be the crash folder(error.log, output_log.txt, crash.dmp) and a screenshot of the error that pops up when you attempt to launch the game. If needed, you can find instructions for those files for the crash folder here. Thank you, and sorry for the inconvenience this is causing you.

(Bangs head on wall) You're right Andrea! I just tested this again and it is indeed back. I'll have Programming fix this again and hopefully it'll stay fixed this time! Thanks again for all the help Andrea!

Hello Archaven, Aegis of Loyalty should remove Dominated, Charmed, and Confused status afflictions from party members when they are hit with a melee attack by another party member with this ability. Based on your description, it sounds like this might be bugged. I will put a bug report together and send it to the QA and Systems Design teams to investigate and get a fix in. If you happen to have a save file where this is occurring, I would love if you could send that to us just in case we are unable to reproduce this issue in-house. If you could attach that here or send it to support@obsidian.net with your forum name and a link to this thread that would be great! If needed, you can find instructions on where to find your save files here. Thank you for reporting this issue and sorry for any inconvenience it may have caused.

Hello Rolandur, Thank you for letting us know about this! I will put a bug report together with this information and send it to the QA and Systems Design teams to investigate to get a fix in. If you happen to discover anything else about this, please continue to post that here as I will be linking this thread to the bug report to be used as a reference. Thanks again for helping make Deadfire even better!

Hey everyone, Boeroer is correct. We have had an issue where items were missing parts of their statblocks and as a result their upgrades and enchants. After checking into the bug database, it looks like this issue has been fixed and verified by the QA team and is awaiting a patch release. You should notice when the fix is implemented in future patch notes or potentially the Beta Patch branch, when that is updated. Thank you for reporting this issue, and sorry for the inconvenience it has caused.

Hello Manticore, I'm sorry you lost so much progress from this crash Did this crash force you to your computer desktop or to the Title Screen? Also, I'm not seeing those files on this post and am wondering if it is because of the size limit the forum allows. If you could, would you be able to send those files to me at support@obsidian.net along with where the crash occurred, what you were doing at the time of the crash, and where you were transitioning to(if applicable). Thank you Manticore, and sorry for the inconvenience this crash has caused.

Hello FifthGear, I'm sorry you ran into a crash transitioning into the Old City. Fortunately you've provided everything we might need to be able to get this investigated and fixed up so that yourself and other future players won't run into this again. I hope the rest of your adventure in the Deadfire is smooth sailing! Thank you for those files and sorry for the inconvenience this caused.

Hello RKHeliplex, Thank you for letting us know about this! I will put this information into a report and sent it to the Systems Design and Programming teams for a fix. If you happen to discover anything else about this, please keep posting about it here as I will be linking this thread to the bug report. Thanks again for looking into this for us and sorry for the inconvenience it caused.

Hey everyone, I apologize for these pushes to the Title Screen. Generally something is going wrong and the game boots players there to protect the save file from being corrupted. If you are able to send the output_log.txt file just after that happens we should be able to see a bit of what was going on that pushed you to the Title Screen. Though this gives a decent amount of information, it is significantly less than if the game happened to crash to the desktop and provide the crash.dmp and error.log as well. Programming investigates each of these issues and fixes as many as they can, but as you may have noticed from reading through the forums, people tend to have this happen in different locations from each other and it can happen seemingly anywhere, so there are a lot of variables when looking for the cause and trying to fix. None of these issues are given up on and we add any provided information for each scene to give us more to work with and compare. If you run into these situations in the future and want to get it fixed as soon as possible, please grab that output_log.txt file right after the occurrence as well as the most recent save file and send them to support@obsidian.net along with an explanation of where you were, what you were doing, and where you were transitioning to(if applicable). If needed, you can find instructions on where to obtain the output_log,.txt file and save files here. Thank you for all the help you've all provided to make Deadfire better, and sorry for the inconveniences you have been running into.

Hey Nuix, Just to update you, Abaris sent us some of the requested information and we are working with that. If you happen to have those files as well, that could also prove useful to compare and get this fixed up. Thanks, and sorry for the inconvenience this is causing you.

Hello MJWilliams! Thank you for bringing this to our attention! I have created a bug report and sent it to the Narrative team to investigate for a fix. By any chance, would you happen to have a save just before going into that dialogue with Eothas that we could use for testing? If not, it's no big deal as we can have QA get us there and test it out, it just saves some time. Thanks again for the help and sorry for the inconvenience this caused during your playthrough.

Hey everyone, We haven't been able to reproduce this in house so we were wondering if a couple of you would be able to provide a save file where this is occurring. If you have a save file from before obtaining you ship and one after, that would be even better, but understandable if you do not. If needed you can find instructions on where to obtain the save files here. If the forums say the file is too big, you can send them to me at support@obsidian.net with your forum name and a link to this thread as a reference. Thanks for the help!

Hello Raficzeqq, I apologize that you have been affected by a low frame rate issue and will make sure your specific instance is looked into. I added the files you linked to a separate bug report and linked that report to the original report we have for this issue pertaining to the Seeker, Slayer, Survivor DLC. In regards to the folks who have been having frame rate issues longer than the DLC release, the Programming team has been working on fixing this issue between Unity and high end Nvidia graphics cards as their number one priority. Your case is a bit more specific in that it only started since the DLC release. I checked the log you provided and noticed a LOT of spam happening and flagged that for the programmers to look into. I sincerely do apologize as I wish everyone to have the best possible experience when playing Deadfire, and hope to have a fix out as soon as possible to help make that happen. I'm sorry for this inconvenience this has caused and thank you for your patience with this issue.

Hello Smzh, Thank you for bringing this to our attention. Would you be able to provide us a copy of your save file where this is occurring for further testing? If needed, you can find instructions on where to obtain your saves here. If the forums say the file is too large, you can email it to me at support@obsidian.net along with your Steam ID and a link to this thread as a reference. Thank you for the help Smzh!

Hey Ptarror, I'm sorry to hear you're still having the issue. Would you be able to send us a copy of the output_log.txt file and your System Specifications so we can try to glean more information to help fix this? If needed, you can find instructions on how to obtain these here. If the forum doesn't allow you to attach them here, you can send them to me at support@obsidian.net with your forum ID and a link to this thread as a reference. Thanks Ptarror.

Hello Mkall, I'm sorry Deadfire is freezing up on you during the Family Pride quest. I've taken all the information you provided, along with the attachments you emailed me and put them into a bug report for the QA and Programming teams to investigate. We will definitely let you know if there is anything else they might need to get a fix in. If you do happen to discover anything else about this bug, please let us know on this thread as I will be linking it to the bug report as a reference. Thank you and sorry for the inconvenience this is causing.

Hey everyone, Programming got back to me about this bug and what would need to be done as their fix went in the 3.0.0.0012 patch. Prior to the fix, if you had character A finish the Beast of Winter DLC and loaded a save from character B, that save file would become affected by the bug. The fix unfortunately can't retroactively fix that affected save, but if you now load an earlier save for character B that had not been loaded and saved over at the time of the bug, then you should be good to go and be able to progress the DLC normally without the issue. I hope this clears things up and is able to get you folks back on track to do the DLC on your other characters. Any new characters should also be unaffected since the fix has gone in. if for some reason this does not seem to be the case, please let me know and I will have the Programming team investigate the issue again. Thanks everyone, and sorry for the inconvenience this has been causing.

Hello Sevrin, I'm sorry you have run into an issue with Rusare not responding to you. I put a bug report together for this and sent the save files to the QA and Area Design teams so they can investigate the issue and get a fix in for this. There is a very similar bug to this already being worked on, so I'm hoping the fix will come sooner as a result. If you discover anything else about this please let me know so I can relay the information to the team for their investigation. Thank you, and sorry for the inconvenience this is causing.

Hello Abaris, I'm sorry you are getting freeze issues during your playthrough. My best recommendation for people who hadn't had this problem until adding DLC is to uninstall and reinstall the entire game at once. If that doesn't fix it for you, then would you be able to reproduce the issue and then send us a copy of your output_log.txt file. If needed, you can find instructions on how to obtain that file here. You can either provide a link to your file via Dropbox or you may attach it to an email for us at support@obsidian.net. If you do email us, please link this post and mention your forum username so that we may identify you easily. Thank you and sorry for the inconvenience this has caused.