devtrackers.gg
EDIT 2:
see this post for additional info and advice.
here's a place to save your builds. you need to make an account on uesp.
EDIT:
upon further testing, the same issue occurs even without equipping build 2 at any point. simply saving over & subsequently loading an armory slot that had assigned CP saved before the fix rolled out, will create the issue.
-assign CP
-save build over previously saved build that included CP config
-load build
-CP is unassigned despite your saved build having CP config saved
in order to address it, you have to save the build with assigned CP (just one star is enough), load the build, reassign CP (your actual config). seems to work afterwards.
see this post for additional info and advice.
here's a place to save your builds. you need to make an account on uesp.
EDIT:
upon further testing, the same issue occurs even without equipping build 2 at any point. simply saving over & subsequently loading an armory slot that had assigned CP saved before the fix rolled out, will create the issue.
-assign CP
-save build over previously saved build that included CP config
-load build
-CP is unassigned despite your saved build having CP config saved
in order to address it, you have to save the build with assigned CP (just one star is enough), load the build, reassign CP (your actual config). seems to work afterwards.
assigned CP config that is saved to an armory build doesn't actually apply, in this specific situation:
-both the old build 1 and build 2 have assigned CP config saved (? i thought they were supposed to reset after fix)
-save over build 2 with unassigned CP (no gear, no active skills, only crafting passives and attributes assigned)
-reassign CP (equip gear, equip active skills)*
-save over build 1
-equip build 2
-CP is now again unassigned, as it should be, because build 2 has empty CP config saved
-equip build 1
-CP is now again unassigned, despite build 1 having assigned CP config saved
*this is the first reassign after the reset from the fix