**This is a ticket I sent to Support, who told me nothing but to post this here.**
Edited by ZOS_Bill on January 19, 2022 11:12PM
I am on MacOS and have been experiencing frequent crashes to desktop ever since I re-downloaded the game in June. Below is a description of some crash conditions observed over the last 1.5 months:
(1) Player-to-player teleporting, e.g. moving to a group member: nearly 100% crash rate. Queueing for dungeons results in the same crash rate
(2) Wayshrine teleporting inter-zone, e.g. moving from Glenumbra to Deshaan: approx 70% crash rate (NB: using the non-city wayshrines between those zones are more reliable, e.g. don't port directly between Daggerfall and Davon's Watch, 30% crash rate)
(3) Wayshrine teleporting intra-zone: 10% crash rate
(4) Map teleport, i.e. non-shrine teleport: around 70% crash rate
(5) Entering delves: usually fine, but some delves are completely broken, see (8)
(6) Having a pet, companion or a group member: nearly 100% crash rate when travelling using (1) or (2), around 20% when engaging (3), (4) and (5)
(7) Zone main quests that have portals back and forth (e.g. Stonefalls end quest, Summerset Evergloam quest) crashes without pets or group members, no remedy found
(8) Certain delves/portals are completely inaccessible: Old Orsimer, Emberflint Mine. I have a list of more, including the start of the main Coldharbour quest (teleporting from Benefactor!)
As you might imagine, this is at best frustrating and at worst absolutely fatal to core aspects of the game (e.g. not being able to start Soul Shriven quest line). At this stage the game is quite unplayable. Dungeons and certain quests cannot be completed, and I have been softlocked in the game world multiple times and had to have a friend on a Windows PC log into my account to move me manually.
There have been numerous forum posts dating from March identifying the cause of this fatal bug which I can link if you'd like. Decided to send in a support ticket to provide more information to the team to fix this as it is quite ridiculous to have to put up with it. I know M1 Macs are not officially supported but Intel Mac users on the forums are experiencing this as well, and the problem identified has nothing to do with the chipset.