Best Of
Re: August 7 Twitch Drops
I got both my drops after watching the Bethesda stream first and then that of an affiliated creator (KhamulESO). I think the issue might be a change in how Twitch counts viewers. My progress bar only actually progressed when I was interacting with the chat, and when I had it on in the background it stopped progressing. So it seems that you actually have to watch and interact with each stream for any progress to happen. Idk if this is intentional on Twitch's part but this appears to be the current way of getting the drops.
Re: Official Discussion Thread for "Watch Amazing Livestreams & Earn a Special Pet at QuakeCon 2025"
For anyone with Drop issues, please place a ticket with customer service. We will help get you the pet. Twitch has been having issues with drops.
I got a response that essentially is passing the buck off to Twitch Support instead of ZOS Support helping me.
Re: v11.1.4 and STILL no mention of a fix for heavy attack bug.
*Laughs in necro* First time? Still waiting on fix since April..... :') But hey we at least got mentioned!
People are most likely not up in arms, because they have given up. I certainly given up on necro ever getting fixed
People are most likely not up in arms, because they have given up. I certainly given up on necro ever getting fixed
Re: Why can't we preview the buttons of the new house?
When possible, I use Home Tours to preview houses. Would be nice if the crown store preview option was more feature complete though.
Re: Extreme FPS drops
DenverRalphy wrote: »katanagirl1 wrote: »Mathius_Mordred wrote: »If you have an RTX GPU make sure to enable DLSS in the video settings.
These fps issues and complains are across all platforms, all system types, all areas of the game. There is something very deep going on. These complains are far to loud to be an isolated thing. @ZOS_Kevin
Yes, please don’t forget those of us on console. I have the Performance option on PS5 which is supposed to guarantee 60 fps and I often get far less than that.
There aren’t any more options that I know of that we can use to address this problem.
I also have seen severe performance degradation in the same timeframe as you have on PC.
Yeah. On PS5 I find that in IA all will be fine, until towards the end of Arc 2 the FPS starts to degrade and by the end of Arc 3 it's pretty bad. Step in to Arc 4, and it's bordering on unplayable.
Dunno when this behavior started as I had recently stopped going into IA regularly and even then rarely beyond the Arc 2 Marauder. But the symptoms are definitely similar to the effects of a memory leak issue. Dynamic objects not completely removed from memory after they're no longer used. Then once I end my IA session (by timing out after leaving or by spinning the hourglass), the problem goes away (mostly, not entirely).
As well, outside of IA the same degradation happens. Just much more slowly. So much so that you don't notice it until it's too late.
For me, IA has had much worse frame rate drops than even busy Cyrodiil Gray Host campaign for a long time. I only get partially through arc 2 and quit when I get the 10 fabled quest done. The worst areas are where the large light diffuser objects are present. Frame rate drops to less than 10 I am guessing. It’s like a slideshow.
Busy cities are bad too, and even Riften has low frame rate drops when doing crafting dailies and turning them in. I mentioned before that near wayshrines I am regularly seeing black silhouettes of players on PS5.
Re: PC Server Downtime & Extending Whitestrake's Mayhem
@ZOS_Kevin ever since the most recent maintenance I have to use a VPN to connect. Without a VPN my ping is now 2k-5k. (day 1 is it was 10k, but it got slightly better after they "fixed" it.) With a VPN it's around 300ish (I'm in Asia), but I have been playing on NA servers since beta, most of that time has been in Asia. This only started w/ the most recent maintenance.
We are looking into this to see why this is happening.
Re: Writhing Wall Event which server will win.. but???
Love how people make up scenarios in their head to get bent out of shape about. Lol
Re: v11.1.4 and STILL no mention of a fix for heavy attack bug.
YandereGirlfriend wrote: »CameraBeardThePirate wrote: »dark_hunterxmg wrote: »For those who don't know, the "heavy attack bug" is actually few different things.
1. Heavy attacks will auto cancel. This means that if a player is trying to continuously heavy attack, they can stop for no reason with the command still held. The command has to be released before starting again.
2. Heavy attacks may not start when the command is held. The player will just stand there doing nothing.
3. The heavy attack may miss the enemy who is directly in front of the player, or do no damage on the hit, while still applying a status effect.
Here is the thread on the topic. I have submitted roughly 50 bug reports over the last 10 months and sent multiple clips of the problems occurring.
https://forums.elderscrollsonline.com/en/discussion/668394/heavy-attacks-auto-canceling#latest
Don't forget
4. Dual Wield heavy attacks are bugged and deal significantly less damage than they should (less damage than a single Dual Wield light attack).
WHAT?!
That is both hilarious and sad.
Yep. Both hits of a dual wield heavy deal about 90% of a single light attack. For comparison, most heavy attacks deal about 1.3x the damage of a light attack.
Re: Writhing Wall Event which server will win.. but???
We will have more info on the Writhing Wall event next month. But to answer the main question, PC and console will start at the same time. So no two week delay between platforms.
ZOS_Kevin
22
Re: Surprise surprise, Blastbones and Animate Blastbones (ulti) are unusable in PvP now.
CameraBeardThePirate wrote: »randconfig wrote: »DanteTheDeviant wrote: »CameraBeardThePirate wrote: »A bug reported early on in the PTS cycle persisted to the live patch, and we still aren't even sure if the dev team is aware of it.
Tested this morning in IC, Blastbones was failing to cast over 50% of the time, and Animate Blastbones simply does nothing - consumes three corpses, but 0 blastbones are spawned. Blastbones would work the first 2 or 3 casts of the fight, then fail for the next two or 3. Rinse and repeat.
If the PTS isn't used to fix bugs like this before live, even when those bugs are reported through official channels early on in the cycle, what exactly is PTS used for? Clearly its not used to ensure a class' core ability functions.
Has there been no update on this, or did I miss it? Looks like the issue persists in live and on the current U47 PTS.
I missed the very beginning of subclasses and didn't see this issue. However, BB is currently functioning properly. In the past month, I haven't noticed this problem in the vast majority of PvP engagements on BG. However, I only have BB as my pet, and I don't have many corpses.
BB generally works if you're not around a bunch of corpses/using only it as a summon, but when you use your full Necromancer abilities as the class was designed, BB or one of your summons, or even your ultimate summons, will fail to spawn and show the error text in the top right of the screen.
It's especially annoying in PVP, and the devs said the pet limit for PVP would be 5, but that means Necromancer fundamentally cannot use Animate Blastbones with their other summons because it would be 6 summons in total. Therefore, even after the bug(s) is fixed, the PVP pet limit needs to be raised to a minimum of 6 for the Necromancer class to fully function as intended (and as was advertised to all the people who purchased it).
The limit was raised to 10 shortly after last patch dropped. The issue still seems to persist both in PvP and PvE because it seems that something with how corpses are replaced is not functioning correctly.
That was a hotfix. They made it clear they intend to make it a 5 pet limit, and gave no explanation or commentary on what this would mean for the Necromancer class, which has always been able to summon 6 pets.
Also, it has been 66 days since ZOS has told us anything about this issue, and no communication regarding it on the U47 PTS as of 11.1.4. The issue persists on both the upcoming patch U47 and live.
