Results 1 to 7 of 7

Thread: Character Stuck

  1. #1
    Player
    Luxerion's Avatar
    Join Date
    Jul 2017
    Posts
    7
    Character
    Chrysalis Lonestar
    World
    Diabolos
    Main Class
    Warrior Lv 70

    Character Stuck

    In around an hour ago, my character got stuck and I literally can't log on them without receiving this type of error.



    Name: Levia Raeneris
    World: Mateus
    Location: The Ruby Sea > Yanxia (It happened during the load screen traveling to Yanxia from Ruby Sea).

    I tried logging on my other char in Diabolos, and I had no problems in doing such. This problem only happens to this char in Mateus. I believe this is caused by the heavy load of players in the server due to the Heaven-on-High, but still I'd appreciate alot if my char was unstuck!
    (0)

  2. #2
    Moderator Einmimiria's Avatar
    Join Date
    Nov 2017
    Posts
    2,510
    Good morning and thank you for posting on the Final Fantasy XIV Technical Support Forums.

    If this is only affecting one character, then it may be something to do with your locally-saved settings. Go to 'My Documents' > 'My Games' > 'Final Fantasy XIV' and delete that folder. If there are any corrupted files that are associated only with that character, this will get rid of them.

    If this does not solve the issue, try updating your graphics card drivers and doing a clean boot. To do a clean boot simply open the task manager and select the 'Start up' Tab. Disable everything here and restart the PC. This will make sure that no background processes are interfering with the game.

    We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV!
    (0)

  3. #3
    Player
    Luxerion's Avatar
    Join Date
    Jul 2017
    Posts
    7
    Character
    Chrysalis Lonestar
    World
    Diabolos
    Main Class
    Warrior Lv 70
    Good afternoon.

    Yes, this is only affecting my Mateus character, not the Diabolos one. I have done all of the suggested above and the issue still persists. The ticket I've sent towards the 'Contact Us' in the support site said that GMs couldn't solve this issue.

    Thank you for your attempt and waiting for a possible solution so I may enjoy my favorite MMO.
    (0)

  4. #4
    Moderator Einmimiria's Avatar
    Join Date
    Nov 2017
    Posts
    2,510
    Thank you for the update Luxerion.

    As a quick test, try running the game in DirectX 9 mode. This can be selected from the 'Config' menu on the launcher.

    It could still be a corrupted file. I'd suggest doing a reinstallation of the game if you can. You can redownload the game here: https://www.finalfantasyxiv.com/playersdownload/na/

    If this does not work, try some of the following:

    -Update/reinstall Graphics card drivers
    -Disable all programs/overlays running in the background
    -Set compatibility mode to Windows 7 (right click on the exe file and select ‘Properties.’ Then select the ‘Compatibility’ tab and choose Windows 7)
    -Make sure that any anti-virus software they have has the appropriate exceptions

    We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV!
    (0)

  5. #5
    Player
    Luxerion's Avatar
    Join Date
    Jul 2017
    Posts
    7
    Character
    Chrysalis Lonestar
    World
    Diabolos
    Main Class
    Warrior Lv 70
    Good evening.

    My game already runs on D9, it's been like that since I started playing in 2.0. I tried switching to D11 and the same error happens. I've also tried all the options above, to no avail. I've done some research once more, and thanks to this Reddit thread (https://www.reddit.com/r/ffxiv/comme...exiting_final/), it's proof enough that this is not a problem in my end.

    This is already an existing issue since 4.0, when the servers were heavily congestioned, and when they tried to move to Yanxia after defeating Susano, their character just go stuck and the only solution is moving them away from that cutscene lock, to another location. The same thing happened because Mateus and The Ruby Sea were heavily populated at the time this bug came. Nothing else but that will solve my issue, I'm afraid to say.

    So if it would be possible to move my character in Mateus to another location, that would be highly appreciated, because I've lost many days of sub due to this issue already. Thank you very much for your attempts thus far.
    (0)

  6. #6
    Moderator Einmimiria's Avatar
    Join Date
    Nov 2017
    Posts
    2,510
    Thank you for the update Luxerion.

    The crash you are getting is a DirectX crash. While you have a similar situation to other players in this Reddit thread, that doesn't necessarily mean that they are caused by the same thing. I'd also wager that some of the conclusions that arose in this thread are based on speculation as well. I say this because DirectX tend to be local to the PC you are using and simply moving the character may not resolve the issue like you speculate.

    However, if you are convinced that this will work, I'd suggest submitting a bug report here: http://forum.square-enix.com/ffxiv/f...2-In-Game-Bugs
    Make sure to follow the template provided in the sticky thread and give all the information it requests. You may also want to contact a GM in-game with your other character and explain the situation. I can't move your character from here, but this will get the attention of someone who can.

    We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV!
    (0)

  7. #7
    Player
    Luxerion's Avatar
    Join Date
    Jul 2017
    Posts
    7
    Character
    Chrysalis Lonestar
    World
    Diabolos
    Main Class
    Warrior Lv 70
    Good evening.

    I was told in a email ticket that this error was one regarding character data, when you disconnect improperly from the server during gameplay, not exactly a DirectX one.

    Even so, I'll be gladly to report this bug so no one suffers the same, and hopefully it'll be fixed in due time, and I will try to contact the GMs with my Diabolos character so they can attempt.

    Thank you once again for your attempts in helping!
    (0)