Stretched graphics (solved)

Hello, I'm having a similar problem to a gamer on this forum from 2017 and I copied his screenshot of the issue. My char and other char's have "stretched" limbs that are annoying at best and at worst block my view of the game. I have tried deleting the .dat file and restarting the game and, unfortunately, that didn't work. I am currently trying -image to see if that might help. It appears that most people's solution to the problem years ago was to run the game in -dx8, however, according to the guild wars wiki, "DirectX 8 support was removed on June 12, 2019, so this likely no longer has an effect.". So, I don't know if that will do anything for me. This is the only game that I have this issue with and it only started recently. I tried uninstalling a recent windows update to see if maybe that was an issue, but running the game after the fact I still had the same problem. Not sure what's left to do other than uninstalling and reinstalling the game. Any ideas would be appreciated as I haven't been able to find much information online about this.

Thanks for the responses guys. I thought I would've got an email notification for responses on this thread otherwise I would've checked back sooner. I did reach out to the support team and they directed me to do what both of you have mentioned. An Intel graphics update must have caused the problem sometime after January. When I rolled back my driver the issue is fixed.

If anyone is reading this looking for a way to do that on Windows 11 search device manager, click on display adapters, click on the drop down (for me it is Intel(R) UHD graphics), in the top tabs click on driver, and then choose the option to roll back drivers. This resets the driver to factory which will cause GW to say that you are playing on a system that may not support GW, but I was able to load up the game just fine. To play smoothly I'd probably need to turn the graphics down, but that's not a bother for someone like me trying to play a 20 year old game. According to the reddit thread that Marty shared one of the commenters was able to manually update his driver to the 2nd before last update caused the issue. I'll have to look into how to do that.