A hotfix just went live for 2.1.0 with a fix for a crash that could happen if using Crunch talent on slayer in Weaves, and another common crash.
A hotfix just went live for 2.1.0 with a fix for a crash that could happen if using Crunch talent on slayer in Weaves, and another common crash.
Similarly to adventure the bots should be using the same loadouts as your last used loadout on the hero in the Athanor. Is that not the case for you/people?
We’ll be dropping in the remaining Curse of Drachenfels maps.
The commendation chests remain unchanged for now, same hats and rates. I doubt we’ll ever change them but if we wanted to alter how it worked we’d make a new box or something and deprecate the old ones (of course not just delete them, but no longer allow acquisition of them).
Cosmetics haven’t been added to them either, so anything that wasn’t in the boxes before 2.1 will only be in the store.
Our aim was and is platform parity in 2020. It wont be an easy process however, and we will do all we can to keep releases as close to each other as possible, but this might not always be so.
We’re going to fix that. Seems to have slipped through a crack.
The “classic” skins from V1 are full skins, head and body.
We’re looking in to it.
I asked QA to look in to this. This was the outcome:
Cannot repro this. However I think it might be the case of them changing character when they are returned to their keep.
So if I am Kerillian in my keep, I join another lobby where my character is picked so I have to pick another character. This will result in me becoming Kerillian again when I get kicked to my lobby.
So if I open a chest as (lets say Bardin) when I’m in another player’s keep and then I get kicked midway, I will be Kerillian in my keep. If I then look at my salvage section as Kerillian I will only be able to see Neckless/Charm/Trinkets that I got from that chest because I opened it as Bardin and any weapon in it would then be for Bardin and would not show up for me as Kerillian
I’m assuming you’ve restarted your PC since reverting these changes, and the performance issues persist?
There’s still more to add to the store from the existing game files. As for rotation, I understand it to be on hold for now at least.
Unfortunately this crash is occurring as a result of an issue in our backend. We’re working on it - apologies for the inconvenience.
I’ve passed this on, thanks!
No all new armor skins at the moment. We’re holding back with the WOM illusions as we have plans for those to solve, or mitigate at the very least, one of the core complaints with the Athanor vs Vanilla Crafting*.
*plans may change
I haven’t had any experience with Error Code 0x0003
but it appears to be an error produced by NVIDIA GeForce Experience.
Sorry, AMD* driver.
Unfortunately I don’t know - may simply be a driver instability, perhaps wait for the next NVIDIA driver or roll back a version and see if the issue persists.
This will likely be due to your high ‘Worker Thread’ count. I’d recommend lowering it within the launcher’s ‘Settings’ menu for improved stability.
Our hats are between like £2 and £4.
It’s unfortunate because there isn’t a lot of consistency in your crashes.
I’d recommend a clean re-installation of your GPU drivers: https://support.fatshark.se/hc/en-us/articles/360021233554--PC-How-to-perform-a-clean-re-installation-of-your-NVIDIA-GPU-drivers
If unsuccessful, please run through the solutions here: ...
Read more