Player Unit Frame - Fahrzeug einsteigen/austeigen erzeugt LUA Fehler

Seit dem letzten Patch 9.1.5 bekomme ich beim ein- und aussteigen von Fahrzeugen einen LUA Error.

Ich hab den Fehler reproduzieren können. Dabei waren keine AddOns aktiv (siehe Video). Die Fehlermeldung deutetd auf Blizzard LUA Source.

Hier das Video mit dem Problem: https://www.youtube.com/watch?v=YCOTs1EGb94

Beschreibung:
Wenn ich das Character-Fenster von seiner gewohnten Position oben Links an eine andere Position verschiebe und dann in eine Fahrzeug ein- bzw. aussteige erhalte ich einen LUA Error.

Dieser Fehler tritt bei verschiedenen Anlässen auf:

  • Besteigen eine Spielzeugs (z.B. Aspirantenbahre)
  • Dungeons (z.B. Necrotische Schneise o. Spitzen des Aufstiegs wenn man mit den Kyriarnern fliegt)
  • usw.

Fehlermeldung: Interface\FrameXML\AnimationSystem.lua:61: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: PlayerFrame:SetPoint.

Es wäre schön wenn das schnell behoben werden könnte, bis dahin kann man sich damit behelfen das Character-Fenster an seiner Standard Position zu belassen.

Diesen Fehler hatte ich auch. Ich konnte ihn mit dem vollständigen Interface Reser (also auch CVar) beseitigen.

Antwort vom Support erhalten werde ich ausprobieren und halte euch auf dem laufenden ob es das problem löst und welchen dieser Schritte geholfen hat.

Here are 3 steps to try in the order below and test out after each one to see if the issue continues:

1- Reset your user interface to make sure your files and addons are not corrupted (please do remember that usually if just renaming doesn’t work, by deleting these files, if you had addons, those would be wiped, and you would need to redownload them again):
a. Close WOW and the BNET app
b. Uninstall addon managers to make sure they don’t re-add your removed addons
c. Find the folder where you have installed WOW
d. Open the folder for the game version you’re troubleshooting (retail or classic)
e. Delete or Rename the Cache, Interface, and WTF folders to CacheOld, InterfaceOld, and WTFOld.
f. Re-launch the app and the game so the changes can take effect.

NOTE: This process will return your game client to default settings. If you wish to keep any addons you play with, I recommend moving the ‚Interface‘ folder to your desktop temporarily. Once you have completed the UI reset, you can then go in and move your addons over to the new ‚Interface > Addons‘ folder one at a time to see if it was causing the issue.

2- Inside the in game chat, paste these commands:

/console cvar_default
/console scriptErrors 0 to hide LUA errors

3- Reset your in-game options to default following the guide below (When you make any changes to your machine or in the game without knowing, sometimes something can break, and resetting it back to default may save you from the problem returning):
https://us.battle.net/support/en/article/126203

Hopefully that works, In case the issuace continues happening, please send us |||||UPDATED||||| system MSINFO files so we can check if all the steps were done correctly and what else could be done:

Export the MSINFO in txt:
https://us.battle.net/support/en/article/12988

Update:

TL;DR: Bug is known, issue will be fixed in future. None of the above steps solved the issue.

Temporay Solution:
/console scriptErrors 0

We have seen other reports about this issue and it appears to be a bug at this time. We have not seen any resolutions other than to keep default settings for now.

Your video is outstanding when we talk about players providing detail to help resolve issues fast this is exact the gold standard and I got this over to our QA and Developers to confirm. It will help them resolve the issue faster. I also provided them your account information for testing (Not that they will access your account but they may copy the data internally and use it for testing which is standard.)

I don’t have an an exact ETA on when this will be resolved but our team is aware of it and we in customer service are tracking reports for them. We would expect this issue to be resolved soon in a future hotfix.