Setting up Global City for Mouse and Keyboard Input
I spent three weeks dealing with input lag issues on this project before I figured out the proper configuration path. The official documentation skips over a few critical steps that most people run into immediately after installation. First thing you need to know is that the default binding scheme assumes controller input. You can switch it during initial setup, but if you already installed it without changing that setting, you will need to navigate to the settings menu and find the input tab. Look for the section labeled "Control Preferences." From there, select keyboard and mouse as your primary input method. The system will then reload the configuration files and remap all the action bindings. The remapping itself is straightforward but slow. Each individual action requires you to press the new key or click the new button. I usually go through the entire list alphabetically to make sure I do not miss anything. This process takes about twenty minutes if you are paying attention.
One thing most guides do not mention is that the sensitivity curves are pre-set for analog sticks. When you switch to a mouse, the default curves make the camera movement feel floaty and imprecise. You need to go back into that same settings menu and change the look sensitivity curve from "Standard" to "Linear." This adjustment alone fixes about eighty percent of the complaints I see on the forums. Your mouse will feel much more responsive and accurate after this change. Keyboard bindings have their own set of quirks. The jump mechanic binds to spacebar by default, but if you are playing on a laptop, that key sits right next to your WASD cluster and gets mashed accidentally during intense moments. I mapped it to the left shift key instead. You need to hold the action button for half a second to confirm the new binding. This prevents accidental overrides when you are reconfiguring multiple keys in sequence. Here is the problem that took me the longest to solve. After about forty minutes of continuous play, my keyboard inputs started registering late. The delay was maybe two hundred milliseconds, but it was noticeable enough to throw off timing-based mechanics. I spent hours checking driver conflicts and background processes before realizing it was a power management setting on my motherboard. The USB ports were entering selective suspend mode to save power. I disabled that feature in the BIOS and the latency issue disappeared completely.
Another counter-intuitive thing: having all your important keys bound on the same hand side actually hurts your performance. Everyone instinctively wants to put movement on WASD and abilities on Q, E, R, F. But your left hand has to cross over your body to reach F while your right hand is managing the mouse. I rearranged everything so my left hand handles movement plus one ability, and my right hand covers mouse plus three abilities. This eliminates crossing motions and cuts my reaction time down by roughly a third during combat sequences. If you are running into issues where the game does not detect your keyboard at all, check whether you have Game Mode enabled in Windows Settings. It interferes with direct input polling in some versions. Turn it off temporarily to test. You can turn it back on after verifying that is the cause. The download link for the latest patch is on the official website under the support section. Make sure you grab the version labeled "Input Update Build" since regular builds still have some of the older binding bugs. The file is about two hundred and fifty megabytes and takes roughly eight minutes to install on a standard broadband connection.
Get the Full Details
Some people report that certain Asian keyboard layouts cause conflicts with the escape key during menu navigation. If that happens to you, switching to US English layout in Windows Regional Settings fixes it. The workaround is a bit annoying but it works consistently across all tested configurations. There is no way to bind the same key to two different actions simultaneously. The game simply ignores the second binding. If you need dual-purpose keys, you have to use a hardware macro solution or accept that you need separate keys for separate functions. I found that clearing the shader cache after changing input settings helps prevent visual glitches during the first session. Navigate to the installation folder and delete the "ShaderCache" directory. The game will rebuild it automatically on launch. This adds about five minutes to startup time but prevents weird texture popping issues that only show up during movement sequences.
Performance scales differently depending on whether you are using a wired or wireless keyboard. Wired connections consistently show lower latency, but good quality wireless keyboards with low polling rates can perform within acceptable margins. I would recommend a polling rate of at least one thousand hertz for competitive play. Anything lower introduces a detectable delay between your keypress and the game registering it.
