DirectX11 crash related to entering raids?

[FrenorWolf]

Tonight for the first time I went ahead and slid into the roulette for a normal raid, it loaded up omegascape v1 (I was able to see it from my character select screen) but then dropped me immediately to desktop with no error. I tried to log in but again, loading screen, dropped to desktop. Hopped on another character and loaded into limsa with no issue. Tried with the other character, drop to desktop on loading screen. I then decided to swap to directx9 and I was able to load in (All be it the raid was done.) and leave the raid. Logged out, swapped back to directx11 and got in with no issue in uldah.

Queueing up again to see if I can repeat.


EDIT: Second try loaded into Alexander raid with no issue.

EDIT2: Third try got another Alexander raid, no issue. Gonna now specific queue for something omega related.

EDIT3: After standing around waiting for Sigmascape v1 to pop again, I big brained and remembered I could partial party solo load it, Upon which it IMMEDIATELY dropped me to desktop. Swapping to DX9 mode now.

[FrenorWolf]

Alright, after repeating this situation multiple times I can soundly say that DX11 turned on crashes me when loading into Sigmascape V1. Swapping to dX9 loads me into the raid but in doing so, the platform that you fight from is invisible and a weird red box is floating beneath the ground. I will update this post further if I encounter any other issues cases of having DX11 related drops to desktop.

NOTE: I never have encountered this issue before 5.5

EDIT: Further tested this out, solo joined into various stormblood trials with no issue. Decided to head back to the raid, this time firing up Alphascape V1, no issue. Tried Sigmascape v2 and did the drop to desktop crash with no error report. This time however, much to my concern reloading in with DX9 however now has me looking at a perpetual loading screen. Can log onto another character with no issue, but its starting to appear Sigmascape somehow got messed up for me in the recent patch. Will now move on to reinstalling the game since I can't play on my character I want to play as until they get booted from the raid due to the timer.

Edit2: Fully reinstalling the game appears to have fixed the issue, But will keep thread open in case anyone else hits a issue like this.

[FrenorWolf]

After hopping on today and deciding to work on my Edenverse progression I loaded into the Furor just fine. However upon beating the boss the victory cinematic started to play and the game crashed, this time with a error window. Logging back in it I was able to leave the raid, talk to turn in the quest, but the same error pops up now whenever starting up the next quest cinematic.

[Lucas_Angelini]

I keep getting the same directx error but it's a 11000002 error. I got kicked, twice, during a raid because of it.

[FrenorWolf]

Day 3. Reinstalling the game sometimes fixes it for what feels like a day then it will randomly drop to desktop when specifically loading a into a new area, be it raid, trial and now flat out area. My character is now stuck in the tempest until I reinstall the game.

[MilkieTea]

Are you in Amaurot at the very least?

[FrenorWolf]

Nope. Gonna try a experiment and delete the ex3 folder in the install area and see if the launcher redownloads it. I'll chime back in if this works as redownloading a little bit is better than sitting through a whole shakedown.

[MilkieTea]

Nope. Gonna try a experiment and delete the ex3 folder in the install area and see if the launcher redownloads it. I'll chime back in if this works as redownloading a little bit is better than sitting through a whole shakedown.

Please do. I only asked bc Amaurot is a lot calmer in terms of how much things are around (not many characters, definitely not many to talk to, and if you've already done the aetheryte quests, no quests to load up) so it seems as safe a spot as any to plop your character in at first.

[FrenorWolf]

Confirming that going into the install area, and removing the folder related to where the area is located expansion wise and then letting the launcher redownload it will "fix" the problem but this may just be until it happens again or discovers another bad file.

[Rhaervis]

Good morning and thank you for posting on the Final Fantasy XIV Technical Support Forums.

Thank you for keeping us updated. We will be moving this thread to "Closed Concerns".

Good luck with your adventures through Eorzea!