Results 1 to 3 of 3
  1. #1
    Player
    Exrage's Avatar
    Join Date
    Sep 2013
    Location
    Limsa Lominsa
    Posts
    114
    Character
    Rage Bladerunner
    World
    Behemoth
    Main Class
    Marauder Lv 50

    Teleported, crashes on character login

    ISP: Comcast

    Type of Internet Connection:Cable

    Internet Connection Speed:
    25 MB/ps

    Date & Time:
    9/25/13 8:50PM PST

    Frequency: Always

    Character Name: Rage Bladerunner

    Race: Hyur M

    World: Typhon

    Class/Level: Blacksmith/29

    Area and Coordinates: Western La Nosca or outside zone-in areas

    Party or Solo: Solo

    NPC Name: None

    Monster Name: None

    In-Game Time: Unknown

    Steps:

    Clicked Teleport from Upper Limsa Lominsa to Aleport

    Loading screen completes, client crashes immediately upon completion

    Waited until next day, same error occurs. Created character on Exodus with same name, game operates with no issues.

    Attempted character Log In on Typhon, error continues to occur. Submitted ticket via the lodestone and began post on tech support forum to track movement and pin-point cause of error.

    Moved character on Exodus by foot from Upper Limsa Lominsa to Middle La Nosca, as soon as character was within 5m from the zone-in area into Wester La Nosca client crashed.

    After serveral attemps to log in with Exodus character, load screen completes to the point I can see the character before client crashes, no changes with Typhon character error either. Believe error is in map data for Western La Nosca.

    Downloaded new client data from FFXIV website, reinstalling FFXIV from scratch- will post results at completion.
    (1)

  2. #2
    Player
    Exrage's Avatar
    Join Date
    Sep 2013
    Location
    Limsa Lominsa
    Posts
    114
    Character
    Rage Bladerunner
    World
    Behemoth
    Main Class
    Marauder Lv 50
    Note: Wrote this under the bugs section, after the first getting moved for not putting it into the right template, then moved again to the "duplicate bugs" without anything written as to the results or further reading on the issue I would try my luck here.

    Second Note: Downloading fresh copy has completed, issues regarding test character on Exodus has shown to have fixed it and I can now zone into western La Nosca and continue moving around and teleporting freely. Will wait until maintenance on Japanese servers are done in 2 hours to confirm if issue is fixed and narrow down the problem areas, as well as provide suggestions.
    (1)

  3. #3
    Player
    Exrage's Avatar
    Join Date
    Sep 2013
    Location
    Limsa Lominsa
    Posts
    114
    Character
    Rage Bladerunner
    World
    Behemoth
    Main Class
    Marauder Lv 50
    Alright, redownloading the 2 hour long download time for the game fixed the issue. A couple of points to note:

    For players:
    If you zone in or join a dungeon and find your client constantly crashing try making a new character, preferably on the same server. If you can create the new character and the game works fine you may have corrupt game data- it's a pain in the ass but uninstall FFXIV and reinstall it, should clear up the problem.

    For FFXIV staff:
    Forums- I know you guys have a ton of error requests every hour of everyday but if someone submits a report and finds it tagged "duplicate" some follow up on where the in-progress or resolved bug report would be nice instead of simply dumping it in a place where it won't be answered with zero input from the guy that put it there. This would increase customer satisfaction and reduce some of that workload from redundant reposts of guys needing answers that they aren't getting.

    Client- A repair feature would *really* help the process of redownloading data as I'm certain this was caused by a temporary loss of connection during the game data download causing the file to corrupt. Add a feature that segments the data and can assess if any of those segments are corrupt- I was playing for weeks without issue until last night when something magically went wrong, and having two hours of downtime downloading everything over again is both insanely wasteful and leaves more chances for data corruption to occur in what was previously fine.
    (1)