Total cast time of actions is affected by connection speed in an unintended way
Date & Time: Still current on 27th of April, 2022, starting as far back as ARR launch
Frequency: Many times during every fight (every action cast)
World name: Gilgamesh, and all other worlds
Character name: Muirgel Caterwaul, and all other characters
Retainer name: Not affected
NPC name: Not affected
Monster name: All
Class/Level: All Disciples of War, Level 1-90
Party or solo: Both solo and party content
In-game time: Any
Area and coordinates: Any
Housing: Not affected
Steps:
1. Repeat this experiment once on a computer with a fast connection to the FFXIV servers (<50ms) and once on a computer with a below average connection (~200ms).
2. Use any GCD action, e.g. the DNC action "Cascade"
3. The game applies an uneven amount of animation lock, depending on your connection speed, for reasons detailed here (LINK) at length.
4. Follow up with any oGCD action, e.g. Fan Dance, as soon as able.
5. See 3.
6. Follow up with another oGCD action, e.g. Fan Dance, as soon as able.
7. See 3.
8. Check if the global cooldown is still on hold, or has finished already.
On a fast connection, the action delay is short enough to allow for using the second oGCD action without delaying the next GCD action. But on a connection with higher latency, each individual action delays the next cast for a longer time than intended - thus, the second action will delay the next GCD action.
This issue has been widely reproduced among the EU and NA region raiding communities over the years. It's not related to any unavoidable or temporary connection issues, but to how the game client handles the animation lock communicated by the server.
Currently, the duration of the animation lock on each action is handled incorrectly (see https://forum.square-enix.com/ffxiv/...=1#post5926978) and effectively increases with the server response time, making "dual weaving" impossible at higher latencies but possible at lower ones. Certain jobs are affected strongly enough that, depending on the player's physical distance from the data center, they cannot perform appropriately at high level play at all.
The bug has existed for a very, very long time now, but is straightforward to fix - to arrive at the intended animation lock duration consistently, the game simply has to take into account how long it took for the server to confirm the action and communicate the intended duration.
For more information, please revisit the original thread (which was moved to the "Insufficient Information" section, as it did not follow the bug report template): https://forum.square-enix.com/ffxiv/...onse-is-ignore
Connection Specs
- Type of internet connection/provider: Cable (Vodafone)
- Modem maker/model number: FritzBox 4040 GI
■ PC Specs
To obtain the system information, open the FFXIV launcher and select Config → System Information → Display.
-=-=-=-=-=-=- System Information -=-=-=-=-=-=-
SYSTEM_OS Windows 8.1 Pro 64-bit (6.2, Build 9200) (9600.winblue_ltsb_escrow.220324-1651)
SYSTEM_CPU Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 CPUs), ~4.0GHz
SYSTEM_CORE_NUM SYSTEM_CORE_LOGIC 8 SYSTEM_CORE_PHYSICS 4
SYSTEM_BIOS 3402
SYSTEM_LANGUAGE Deutsch (Regional Setting: Deutsch)
SYSTEM_MEMORY 32708.359MB
SYSTEM_VIRTUAL_MEMORY 134217727.875MB
SYSTEM_PAGE_FILE 57736.477MB
SYSTEM_STORAGE C:\ SYSTEM_HARDDISK_DRIVE SYSTEM_TOTALDISC_SPACE 446.615GB SYSTEM_FREEDISC_SPACE 18.822GB
SYSTEM_STORAGE D:\ SYSTEM_HARDDISK_DRIVE SYSTEM_TOTALDISC_SPACE 1862.891GB SYSTEM_FREEDISC_SPACE 102.168GB
SYSTEM_STORAGE E:\ SYSTEM_HARDDISK_DRIVE SYSTEM_TOTALDISC_SPACE 447.129GB SYSTEM_FREEDISC_SPACE 109.470GB
SYSTEM_DIRECTX_VERSION DirectX 11
SYSTEM_GRAPHICS NVIDIA GeForce GTX 970
SYSTEM_GRAPHICS_DEVICE \\.\DISPLAY1
SYSTEM_GRAPHICS_CHIP NVIDIA GeForce GTX 970
SYSTEM_GRAPHICS_MAKER NVIDIA
SYSTEM_GRAPHICS_VRAM 3992.375 MB
SYSTEM_GRAPHICS_SHARED_VRAM 16354.180 MB
SYSTEM_GRAPHICS_DAC Integrated RAMDAC
SYSTEM_GRAPHICS_DISPLAY_MODE 1920 x 1080 (32 bit) (60Hz)
SYSTEM_GRAPHICS_DRIVER nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
SYSTEM_GRAPHICS_DRIVER_VERSION 30.00.0014.7212
SYSTEM_GRAPHICS_DRIVER_DATE 16.09.2021 04:41:26
SYSTEM_GRAPHICS_DRIVER_LANGUAGE English
3.0
SYSTEM_GRAPHICS_PIXEL_SHADER 3.0
SYSTEM_GRAPHICS_VERTEX_TEXTURE SYSTEM_SUPPORT
SYSTEM_GRAPHICS NVIDIA GeForce GTX 970
SYSTEM_GRAPHICS_DEVICE \\.\DISPLAY2
SYSTEM_GRAPHICS_CHIP NVIDIA GeForce GTX 970
SYSTEM_GRAPHICS_MAKER NVIDIA
SYSTEM_GRAPHICS_VRAM 3992.375 MB
SYSTEM_GRAPHICS_SHARED_VRAM 16354.180 MB
SYSTEM_GRAPHICS_DAC Integrated RAMDAC
SYSTEM_GRAPHICS_DISPLAY_MODE 1920 x 1080 (32 bit) (60Hz)
SYSTEM_GRAPHICS_DRIVER nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
SYSTEM_GRAPHICS_DRIVER_VERSION 30.00.0014.7212
SYSTEM_GRAPHICS_DRIVER_DATE 16.09.2021 04:41:26
SYSTEM_GRAPHICS_DRIVER_LANGUAGE English
3.0
SYSTEM_GRAPHICS_PIXEL_SHADER 3.0
SYSTEM_GRAPHICS_VERTEX_TEXTURE SYSTEM_SUPPORT
SYSTEM_SOUND CABLE-B Input (VB-Audio Cable B)
SYSTEM_SOUND_DEVICE_ID {11718051-7790-4010-A848-943D14E1150C}
SYSTEM_SOUND_DEVICE_NAME vbaudio_cableb64_win7.sys
SYSTEM_SOUND_DRIVER_VERSION 6.01.7600.16385
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 19.10.2015 17:59:42
SYSTEM_SOUND VoiceMeeter Input (VB-Audio VoiceMeeter VAIO)
SYSTEM_SOUND_DEVICE_ID {20705610-2289-49D7-9D40-C2866ECEC3C5}
SYSTEM_SOUND_DEVICE_NAME vbaudio_vmvaio64_win7.sys
SYSTEM_SOUND_DRIVER_VERSION 6.01.7600.16385
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 24.10.2019 21:09:20
SYSTEM_SOUND CABLE Input (VB-Audio Virtual Cable)
SYSTEM_SOUND_DEVICE_ID {3D73D78D-7DDF-4335-9D3E-71197733E65D}
SYSTEM_SOUND_DEVICE_NAME vbaudio_cable64_win7.sys
SYSTEM_SOUND_DRIVER_VERSION 6.01.7600.16385
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 02.09.2014 19:01:16
SYSTEM_SOUND LG IPS FULLHD (NVIDIA High Definition Audio)
SYSTEM_SOUND_DEVICE_ID {71CC6933-AEA2-463D-8E46-8486650CCF76}
SYSTEM_SOUND_DEVICE_NAME nvhda64v.sys
SYSTEM_SOUND_DRIVER_VERSION 1.03.0038.0060
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 09.06.2021 05:42:54
SYSTEM_SOUND CABLE-A Input (VB-Audio Cable A)
SYSTEM_SOUND_DEVICE_ID {7E8D8976-66E5-4A1A-BE26-765053291BAA}
SYSTEM_SOUND_DEVICE_NAME vbaudio_cablea64_win7.sys
SYSTEM_SOUND_DRIVER_VERSION 6.01.7600.16385
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 19.10.2015 18:22:32
SYSTEM_SOUND Speakers (Realtek High Definition Audio)
SYSTEM_SOUND_DEVICE_ID {B943D4F7-D2BB-4043-82BA-DA7CCD161F81}
SYSTEM_SOUND_DEVICE_NAME RTKVHD64.sys
SYSTEM_SOUND_DRIVER_VERSION 6.00.0001.7982
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 09.11.2016 10:49:02
SYSTEM_SOUND VoiceMeeter Aux Input (VB-Audio VoiceMeeter AUX VAIO)
SYSTEM_SOUND_DEVICE_ID {DA20F862-C89A-43A0-AF38-6A4A43D424F7}
SYSTEM_SOUND_DEVICE_NAME vbaudio_vmauxvaio64_win7.sys
SYSTEM_SOUND_DRIVER_VERSION 6.01.7600.16385
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 24.10.2019 21:09:21
SYSTEM_SOUND Realtek Digital Output (Realtek High Definition Audio)
SYSTEM_SOUND_DEVICE_ID {F02BB017-1DD7-41A4-BC3B-66DAD8B8AC22}
SYSTEM_SOUND_DEVICE_NAME RTKVHD64.sys
SYSTEM_SOUND_DRIVER_VERSION 6.00.0001.7982
SYSTEM_SOUND_DRIVER_LANGUAGE English
SYSTEM_SOUND_DRIVER_DATE 09.11.2016 10:49:02
SYSTEM_INPUT {6F1D2B60-D5A0-11CF-BFC7444553540000}
SYSTEM_INPUT_NAME Mouse
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 3 SYSTEM_GAMEPAD_BUTTON 5 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {6F1D2B61-D5A0-11CF-BFC7444553540000}
SYSTEM_INPUT_NAME Keyboard
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 128 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {DCAE7CB0-1B02-11EC-8001444553540000}
SYSTEM_INPUT_NAME TWCS Throttle
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 8 SYSTEM_GAMEPAD_BUTTON 14 SYSTEM_GAMEPAD_FOV 1
SYSTEM_INPUT {55ACDF10-85F0-11EB-8003444553540000}
SYSTEM_INPUT_NAME Saitek Magic Hotkey Device
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 669 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {DFEC81C0-A2E9-11EA-8001444553540000}
SYSTEM_INPUT_NAME IMU
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {E0B01FE0-A2E9-11EA-8004444553540000}
SYSTEM_INPUT_NAME Valve VR Radio & HMD Mic
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {DFECA8D0-A2E9-11EA-8002444553540000}
SYSTEM_INPUT_NAME Optical
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {F5266880-9FB9-11E6-8005444553540000}
SYSTEM_INPUT_NAME Wacom Tablet
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 3 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {F5266880-9FB9-11E6-8009444553540000}
SYSTEM_INPUT_NAME Wacom Tablet
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 11 SYSTEM_GAMEPAD_BUTTON 6 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {F5266880-9FB9-11E6-8003444553540000}
SYSTEM_INPUT_NAME Controller (XBOX 360 For Windows)
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 5 SYSTEM_GAMEPAD_BUTTON 10 SYSTEM_GAMEPAD_FOV 1
SYSTEM_INPUT {F5266880-9FB9-11E6-8004444553540000}
SYSTEM_INPUT_NAME Yeti Stereo Microphone
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 1 SYSTEM_GAMEPAD_BUTTON 8 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {F5266880-9FB9-11E6-8006444553540000}
SYSTEM_INPUT_NAME Yeti Stereo Microphone
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {E0B01FE0-A2E9-11EA-8003444553540000}
SYSTEM_INPUT_NAME Controller
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {C6D6B370-1C7A-11EC-8001444553540000}
SYSTEM_INPUT_NAME VKB-Sim Gladiator NXT R
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 8 SYSTEM_GAMEPAD_BUTTON 128 SYSTEM_GAMEPAD_FOV 1
SYSTEM_INPUT {7AE700B0-28F5-11EB-8001444553540000}
SYSTEM_INPUT_NAME USB Keyboard
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 1 SYSTEM_GAMEPAD_BUTTON 1 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {9650CD10-1C72-11EC-8006444553540000}
SYSTEM_INPUT_NAME vJoy Device
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 4 SYSTEM_GAMEPAD_BUTTON 12 SYSTEM_GAMEPAD_FOV 1
SYSTEM_INPUT {7AE727C0-28F5-11EB-8002444553540000}
SYSTEM_INPUT_NAME USB Keyboard
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 3 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {8FF59DC0-1C76-11EC-8003444553540000}
SYSTEM_INPUT_NAME vJoy Device
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 6 SYSTEM_GAMEPAD_BUTTON 14 SYSTEM_GAMEPAD_FOV 1
SYSTEM_INPUT {7AE727C0-28F5-11EB-8003444553540000}
SYSTEM_INPUT_NAME USB Keyboard
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 21 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {E0B046F0-A2E9-11EA-8005444553540000}
SYSTEM_INPUT_NAME Valve VR Radio
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {8FF59DC0-1C76-11EC-8005444553540000}
SYSTEM_INPUT_NAME vJoy Device
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 8 SYSTEM_GAMEPAD_BUTTON 30 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {8FF59DC0-1C76-11EC-8007444553540000}
SYSTEM_INPUT_NAME vJoy Device
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 8 SYSTEM_GAMEPAD_BUTTON 29 SYSTEM_GAMEPAD_FOV 0
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Quote:
Originally Posted by Gildrein
If you continue to experience the bug even after your report is moved here, please use the appropriate template and create a new report in the In-Game Bugs forum.
This report follows up on this thread, which got moved to "Insufficient Information" as it did not follow the bug report template closely enough. In following the template, I hope I've provided enough information this time around.
Total cast time of actions is affected by connection speed in an unintended way
This is something that can be seen when testing between servers. If connected to a local sever with a low ping (Europe to Eurpe), you can usually weave/double weave OGCDs without clipping. if you're on a higher one (Europe to America) then even something as simple as a weaving an OGCD can sometimes clip.
From my understanding of another website, this is due to the time between when the packet is sent to the server, and the servers response.
If say the server 'tick is every 100ms, if you get in before the 100ms it'll register the action, however, if you hit it at 101ms, you'll have to wait til 200ms for it to register (the times are less than this, but I was giving a very dumbed down version of it)
It's a terrible system which penalises high pings, be that from distance or just poor internet in the area. There is a similar issue if your FPS is low where it has to wait and send the 'tick' to the server once the frame is sent. Theoretically, someone who is East coast on an 'OKish' PC will not benefit as much as someone on the west coast with a good PC