Before continuing, this is not a functionality bug. This is a graphical bug, which means this is only an extremely visually unappealing issue and does not hinder game play.
After reading over the issue, please let me know if there is any additional information that you would like for me to provide.
Issue: Stereoscopic 3D causes texture tearing/stretching on certain mobs/npcs. This is the same visual effect as a corrupted (or missing) skeleton file on an object. This is most frequently found on Chocobo mounts.
Time: N/A - Doesn't matter
Frequency: 10/10
World name: Coeurl
Character name: Nihon Nooblet
NPC name: Chocobo
Monster name: Chocobo
Class/Level: Conjurer / 12
Party or solo: N/A - Doesn't matter
In-game time: N/A - Doesn't matter
Area and coordinates: Anywhere there is a chocobo mount or chocobokeep
Steps:
1. Enable Stereoscopic 3D via system graphics control panel (I have NVIDIA)
2. Launch the game
3. Ensure video resolution setting is set to 120hz refresh rate or higher to enable 3D capabilities
4. Log into character of choice
5. Visit any chocobo stable or chocobo keeper.
6. Obtain chocobo mount and ride on chocobo
7. Observe tearing and stretching of textures when adjusting camera angle.
Connection Specs
Internet information is not a concern for this issue.
PC Specs
-=-=-=-=- System Information -=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130708-1532)
- Processor: Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz (8 CPUs), ~3.5GHz
- Memory: 32768MB RAM
- Available OS Memory: 32718MB RAM
- Page File: 3810MB used, 61622MB available
- DirectX Version: DirectX 11
- Card name: NVIDIA GeForce GTX 680
- Display Memory: 4095 MB
- Dedicated Memory: 3072 MB
- Shared Memory: 1023 MB
- Driver Date/Size: 5/12/2013 16:42:27, 15143904 bytes
Laptop Model Name:
I'm running on a desktop.
Gamepad Manufacturer:
Gamepad information is not a concern for this issue.
Browser Information
Browser information is not a concern for this issue.
Screenshots of the issue have been attached:
![]()