Will this likely prevent me from finishing VMA for the first time?
I started this morning and got to round 5 with fairly little problems after learning the mechanics. I rarely had to use sweeps in the those 4 rounds outside of engine guardian, but I think as I progress I'm going to be much more reliant on them.
I eventually had to stop to go to work, but what I'm wondering is if I'm just asking for problems and frustration trying to complete my first vet run while this issue is ongoing? Should I wait for a fix? Change up cp?
Justice31st wrote: »NewBlacksmurf wrote: »Have you all thought that maybe it is working as intended due to how the tool tips read and perhaps that the change discussed on PC PTS was done as an exception only.
Meaning that it's possible that a future PC change will align consoles and PC (if it's really not working and not a UI error)
Except it is already working on the PC live version, but not on consoles. And @Wrobel already stated that puncturing sweeps goes off both elemental expert and thaumaturge, unless you are calling him a liar.
NewBlacksmurf wrote: »Justice31st wrote: »NewBlacksmurf wrote: »Have you all thought that maybe it is working as intended due to how the tool tips read and perhaps that the change discussed on PC PTS was done as an exception only.
Meaning that it's possible that a future PC change will align consoles and PC (if it's really not working and not a UI error)
Except it is already working on the PC live version, but not on consoles. And @Wrobel already stated that puncturing sweeps goes off both elemental expert and thaumaturge, unless you are calling him a liar.
Not calling him a liar, but his comment was one that took a very long time to change for PTS and the tool tips don't align with his statement.
Maybe it just takes twice as long on consoles to make the same adjustment....but I just don't see that it's a bug because there are no console comments for weeks on this. Everyone is pointing out PTS stuff but we have a recent console official statement on upcoming changes and this isn't part of it.
It's one thing if it's a bug and in the works but it's another thing if after all this time and the PTS comments, that no official statement was made towards consoles.
That's all
Will this likely prevent me from finishing VMA for the first time?
I started this morning and got to round 5 with fairly little problems after learning the mechanics. I rarely had to use sweeps in the those 4 rounds outside of engine guardian, but I think as I progress I'm going to be much more reliant on them.
I eventually had to stop to go to work, but what I'm wondering is if I'm just asking for problems and frustration trying to complete my first vet run while this issue is ongoing? Should I wait for a fix? Change up cp?
yes, it will affect you quite a bit as you lose 18% of your dps (assuming you got 18% in thaumaturge 20 elm expert) . Since ZOS did not fix it yet or has given any decent answer on this topic, I would say they won't fix it untill next major incremantal patch wich will be over a month from now for console.
Yes, change your cp for now; put a 100 into elemental expert for now and whatever points you got left from what was in thaumaturge put em into crit or pen. if you do so you only lose about 13% dps
ZOS_GinaBruno wrote: »As a quick update, this is still being worked on and we haven't forgotten about it! It likely won't be fixed in next week's PTS incremental patch, but we do want to address it before Dark Brotherhood goes live.
ZOS_GinaBruno wrote: »The fix is currently being tested, so we can't say with 100% certainty it will most definitely without a doubt be fixed. We want it fixed as much as you do, though, and are working on it.Wanting to and doing so are entirely different things please fix this. Templars finally feel competitive across pvp pve etc
ZOS_GinaBruno wrote: »
zos_jessicafolsom wrote: »Night-blade
Assassination
- Teleport Strike: Fixed an issue where this ability and its morphs could be used to get on top of Keep walls.
zos_jessicafolsom wrote: »Maw of Lorkhaj Trial
Some item set pieces in Maw of Lorkhaj were incorrectly dropping as bind-on-equip instead of bind-on-pickup. Those items have been corrected and include the following sets:General
- Roar of Alkosh
- Lunar Bastion
- Moondancer
- Twilight’s Remedy
Vampire
- Fixed an issue with the Grouping Tool that was resulting in groups of two players having longer queue times than expected.
Alchemy
- Dark Stalker: Fixed an issue where this passive ability was reducing the Movement Speed penalty of Crouch by 50% instead of 100%. This ability’s tooltip has also been updated to better describe its bonuses.
Exploration & Itemization
- Fixed the Medicinal Use passive so it once again improves the duration of consumed potions.
- Fixed an issue that was preventing the following potions from being usable while moving:
- Potions of Stamina
Item Sets
- Fixed an issue where the default enchantments on Alliance War weapons had higher values than intended.
- Added the ability to toggle item locking from within the keyboard bank UI.
willymchilybily wrote: »Please ZOS. Get This Sorted
jediprime74 wrote: »willymchilybily wrote: »Please ZOS. Get This Sorted
This, to me, is what is most egregious. These issues were known to exist on the PC/Mac platform. They were fixed prior to DB going live.
These issues were known to exist in the code that was sent to the console servers. They were NOT fixed prior to DB going live, and here we are more than two weeks later and not only are the issues still present, but Zenimax hasn't even acknowledged them as existing and being addressed.
It's something of a slap in the face. Zenimax hasn't even had the courtesy to say 'these are known issues.' As a result we are left entirely in the dark.
Like others, I have spent copious amounts of gold to test and isolate the Thaumaturge issue, and to verify it's not functioning correctly. Like others, I invested heavily in a Templar build that focused on using Jabs or Sweeps. Spent the AP for new set pieces, spent gold, used gold improvement mats to push everything up to Legendary. Like others, that character is collecting dust right now, because the damage output isn't where it needs to be for endgame content, and we refuse to use a gimped character that may decrease overall DPS output in trials.
So...while I acknowledge that the Thaumaturge issue doesn't render Templars unplayable generally, it sure as hell renders them unplayable as damage dealers for the hardest content in the game.
This is most unsatisfactory.
willymchilybily wrote: »Will this likely prevent me from finishing VMA for the first time?
I started this morning and got to round 5 with fairly little problems after learning the mechanics. I rarely had to use sweeps in the those 4 rounds outside of engine guardian, but I think as I progress I'm going to be much more reliant on them.
I eventually had to stop to go to work, but what I'm wondering is if I'm just asking for problems and frustration trying to complete my first vet run while this issue is ongoing? Should I wait for a fix? Change up cp?
yes, it will affect you quite a bit as you lose 18% of your dps (assuming you got 18% in thaumaturge 20 elm expert) . Since ZOS did not fix it yet or has given any decent answer on this topic, I would say they won't fix it untill next major incremantal patch wich will be over a month from now for console.
Yes, change your cp for now; put a 100 into elemental expert for now and whatever points you got left from what was in thaumaturge put em into crit or pen. if you do so you only lose about 13% dps
This would be unacceptable to me.
on PC PTS it got this responseZOS_GinaBruno wrote: »As a quick update, this is still being worked on and we haven't forgotten about it! It likely won't be fixed in next week's PTS incremental patch, but we do want to address it before Dark Brotherhood goes live.ZOS_GinaBruno wrote: »The fix is currently being tested, so we can't say with 100% certainty it will most definitely without a doubt be fixed. We want it fixed as much as you do, though, and are working on it.Wanting to and doing so are entirely different things please fix this. Templars finally feel competitive across pvp pve etcZOS_GinaBruno wrote: »
It is not just this issue.
I can still get an okay puncturing sweep and go more into elfborn. It is every issue that was fixed on PC is left on consoles. if you look updates we appear to be at 2.4.5, and PC 2.4.9.
in update 2.4.6 nighblades could not ambush up keeps on PC.zos_jessicafolsom wrote: »Night-blade
Assassination
- Teleport Strike: Fixed an issue where this ability and its morphs could be used to get on top of Keep walls.
in update 2.4.7 i can confirm the following has not changed for consoles i include the ones i think MOST important.zos_jessicafolsom wrote: »Maw of Lorkhaj Trial
Some item set pieces in Maw of Lorkhaj were incorrectly dropping as bind-on-equip instead of bind-on-pickup. Those items have been corrected and include the following sets:General
- Roar of Alkosh
- Lunar Bastion
- Moondancer
- Twilight’s Remedy
Vampire
- Fixed an issue with the Grouping Tool that was resulting in groups of two players having longer queue times than expected.
Alchemy
- Dark Stalker: Fixed an issue where this passive ability was reducing the Movement Speed penalty of Crouch by 50% instead of 100%. This ability’s tooltip has also been updated to better describe its bonuses.
Exploration & Itemization
- Fixed the Medicinal Use passive so it once again improves the duration of consumed potions.
- Fixed an issue that was preventing the following potions from being usable while moving:
- Potions of Stamina
Item Sets
- Fixed an issue where the default enchantments on Alliance War weapons had higher values than intended.
- Added the ability to toggle item locking from within the keyboard bank UI.
Please ZOS. Get This Sorted
ZOS_JessicaFolsom wrote: »(Cross-posted to the PlayStation 4 Technical Support forum area)
Hi everyone,
We have identified a cause of the majority of the crashes to dashboard and crash loops that some characters are getting caught in on Xbox One and PlayStation 4. The issue is related to memory, and we have a fix that improves memory handling for both console clients.
We are rolling out this fix on both Xbox One and PlayStation 4 on Wednesday, July 6. Once this fix goes live, you should no longer see frequent crashes to dashboard and crash loops on specific characters.
In the meantime, we’d like to ask for your help. The highest volume of crash loops we’re seeing are in and around Orsinium and Wrothgar, especially where you pick up and do Crafting Writs, and to a lesser degree in Elden Root and Grahtwood. If you are experiencing crashing those areas, we ask that you please consider staying out of them until we patch the issue on Wednesday of next week—we’d greatly appreciate it. If your character does get stuck in a crash loop, our Support team can move your character if you contact them. If they do have to move your character, please be sure to not return to that area as they won’t be able to move you a second time until they’ve moved everyone waiting for their first character move – which could mean they won’t get to you before the 6th.
There is still one edge-case crash cause in Orsinium that we are working on a fix for, but it is easily avoidable. If you Wayshrine into Orsinium (the city) and quickly run into the city, especially with a movement speed buff on, you may crash. Waiting a few seconds before moving after you Wayshrine into Orsinium will greatly reduce the likelihood that you will crash. This issue will be fixed in a future patch.
Thank you for your patience as we worked to resolve this issue. After the patch goes live on Wednesday, please let us know if you are running into any other crash issues on Xbox One and PlayStation 4.
There was this:ZOS_JessicaFolsom wrote: »(Cross-posted to the PlayStation 4 Technical Support forum area)
Hi everyone,
We have identified a cause of the majority of the crashes to dashboard and crash loops that some characters are getting caught in on Xbox One and PlayStation 4. The issue is related to memory, and we have a fix that improves memory handling for both console clients.
We are rolling out this fix on both Xbox One and PlayStation 4 on Wednesday, July 6. Once this fix goes live, you should no longer see frequent crashes to dashboard and crash loops on specific characters.
In the meantime, we’d like to ask for your help. The highest volume of crash loops we’re seeing are in and around Orsinium and Wrothgar, especially where you pick up and do Crafting Writs, and to a lesser degree in Elden Root and Grahtwood. If you are experiencing crashing those areas, we ask that you please consider staying out of them until we patch the issue on Wednesday of next week—we’d greatly appreciate it. If your character does get stuck in a crash loop, our Support team can move your character if you contact them. If they do have to move your character, please be sure to not return to that area as they won’t be able to move you a second time until they’ve moved everyone waiting for their first character move – which could mean they won’t get to you before the 6th.
There is still one edge-case crash cause in Orsinium that we are working on a fix for, but it is easily avoidable. If you Wayshrine into Orsinium (the city) and quickly run into the city, especially with a movement speed buff on, you may crash. Waiting a few seconds before moving after you Wayshrine into Orsinium will greatly reduce the likelihood that you will crash. This issue will be fixed in a future patch.
Thank you for your patience as we worked to resolve this issue. After the patch goes live on Wednesday, please let us know if you are running into any other crash issues on Xbox One and PlayStation 4.
Nothing about Templars though as of yet. Templars are doomed.
Templar
Aedric Spear
Puncturing Strikes: Fixed an issue where the Champion Passive Thaumaturge was not applying to this ability and its morphs.
Will this finally put to rest the debate from "Flat-Earthers" about this issue?
Please?
jediprime74 wrote: »Right? I am quite pleased that the issue appears to have been resolved, but at this point I want ZOS to understand that they dropped the ball in communications with the player base as to this issue, which is what fed the flames of those that were taking up the silly position that something considered broken on the PC/Mac platform wasn't considered broken on the console platforms...