Drift

Drift

33.5k Downloads

New patch

Welinth opened this issue ยท 9 comments

commented

Hi,

Looks like something with the new patch messed with the addon? Every time I have it enabled, I am not able to get past the loading screen. Every time I disable it, I am good to go. Wondering if others are dealing with the same or if it is just me?

Thanks

commented

Confirmed... please update.
Sadly I cannot provide any logfiles.

commented

Thanks for the heads up. Apologies for the inconvenience.

commented

Unfortunately, I am not able to reproduce this. I can log into the game fine, and I am not seeing any issues when moving frames. Is it the case you're not able to enter the world at all?

commented

I've did some more testing:
It's happening when loggin in with a character. As soon as the loading bar hits the end the game is not responding.

It is NOT happening when I delete the SavedVariables for Drift!

I will attach my config maybe it helps.
Drift.zip

Thanks!

commented

Confirmed the saved variables fix. Went into my account folder, savedvariables, and deleted the drift one and was able to get past the login screen

commented

@Aur0r4 - I really appreciate the testing. Using your config, I am able to reproduce the issue on my side. Thanks @Welinth for the confirmation as well.
I will investigate more when I have some time.

commented

It is

["miscellaneousDisabled"] = true,

what is causing the issue.

As soon as you enable the miscellaneous box in the Drift-Options you get stuck in the loading screen.

commented

Good find @Aur0r4. I isolated the issue on my side to a bad interaction between Drift and the VehicleSeatIndicator frame. The Fractures in Time update added VehicleSeatIndicator to Edit Mode (https://worldofwarcraft.blizzard.com/en-us/news/23968772/updated-july-11-dragonflight-fractures-in-time-content-update-notes-now-live#item15) which is most likely why this manifested with the new patch. I am going to disable VehicleSeatIndicator in Drift for now.

commented

Fixed in Drift v2.2.9. Please reopen this issue if the problem comes back.