controlling air units

[Tomoko]

does anyone have an issue with controls being unresponsive with air units ? throttles and rolling doesn't seem to do anything anymore, so i'm forced to have them on full auto else i risk losing them because they just stay on idle throttle

[SarahTheFoxyGirl]

same

[kn9484]

controls are working but update ♥♥♥♥♥♥ up button mapping

now they are changed to arows for wherewer reasom :(

[Ataxio]

Originally posted by kn9484:

controls are working but update ♥♥♥♥♥♥ up button mapping

now they are changed to arows for wherewer reasom :(

^this

I hate it

[AAA Battery]

you can adjust the mappings

[Tomoko]

Originally posted by AAA Battery:

you can adjust the mappings

You can ? because i only found out that using my controller was the only way to actually control air units ergonomically

[kn9484]

Originally posted by AAA Battery:

you can adjust the mappings

Realy? and what this will do if you have WASD keys and hints for controls are corectly remind you about WASD keys but they dont even react?? because they are remaped to compleatly diffrent imputs??

And what if i dont have controler? Do i am now forced to buy one now?

If these in-game hint boxes tells you that you have WASD keys (not arows) as your controls then why the ♥♥♥♥ they don't work ????????????

[Konri_one (K_o)]

so, I had look through this thread hoping for solution, since no one came up with anything I decided to look into old school way of changing config/xlm file


In case you want to help me figure this out:

you can find keybindings file in C:\Users\YourUsername\AppData\Roaming\Carrier Command 2
File is called Keybindings.xml
open it with notepad, it has number values for each key, quick google search gave me this table:
https://www.glfw.org/docs/3.3/group__keys.html
*EDIT updated table for a better one*

I need to figure out which binding on the list corresponds to which key, however I already see 4 positions assigned to 0, so this might be the culprit.

I will do some tests and update you once I find a fix

Edit: there are 31 to assign in game, and 41 assigned in XML, those might be double binds, but if order is the same as in the game, "look" options are assigned to keys 262-265 which correspond to arrow keys... but on numpad?[\strike]

Ok arrow keys are correct and it follows correct order...

[Konri_one (K_o)]

It would seem that D-pad keys (map pan keys) somehow got merged with look keys.
If you rebind D-pad keys the tool tip will change but the keys won't work.

I guess I will send it as bug report, hopefully it can be resolved soon as it seems simple keybind changes won't work.

[Scythan]

Originally posted by Konri_one (K_o):

so, I had look through this thread hoping for solution, since no one came up with anything I decided to look into old school way of changing config/xlm file


In case you want to help me figure this out:

you can find keybindings file in C:\Users\YourUsername\AppData\Roaming\Carrier Command 2
File is called Keybindings.xml
open it with notepad, it has number values for each key, quick google search gave me this table:
https://www.glfw.org/docs/3.3/group__keys.html
*EDIT updated table for a better one*

I need to figure out which binding on the list corresponds to which key, however I already see 4 positions assigned to 0, so this might be the culprit.

I will do some tests and update you once I find a fix

Edit: there are 31 to assign in game, and 41 assigned in XML, those might be double binds, but if order is the same as in the game, "look" options are assigned to keys 262-265 which correspond to arrow keys... but on numpad?

Ok arrow keys are correct and it follows correct order...

I have been dealing with this since the patch came out that bugged everything. I contacted Geometa via their in-game bug report, and I was directly told by a Geometa employee this was 'to streamline controls with ground units' and it was 'working as expected'

Which cannot be true as ground units are controlled via WASD, but this is what I was told.

I, too, sought to change this in an XML file and though you got a lot further with me with the table as I could not find out which numerical values corresponded to which key -- I remain dismayed that the direction keys are linked and cannot be separated.

of course you can change 'look' in game to WASD but what this will ruin is the map controls, you will be unable to scroll the map with keys which becomes crucial when sending barges and/or making long-range waypoints for units, which require holding down the mouse button -- the only workaround is to zoom out enough to see everything and that can be squirrley to say the least.

When this issue first appeared, the 'help text' indicating keys was simply missing, I was shocked to find in the hotfix patch that launched more recently, the help text was replaced, but it was replaced with WASD!!! This is further evidence to me that something went screwy with controller/HOTAS support and they're struggling / don't care to fix it.

I keep checking forums and mods looking for a fix for this but what was my zen go-to game after a long day of work has been barely touched for a while.

Please, @koni_one let's work together and try to get this fixed, no one else seems to really want to dive in.

[Konri_one (K_o)]

So hey Scythan~

I already saw the posts on geometa portal, while I find devs "dismissive" to put it diplomatically, lets remember, facts not emotions, since they cannot find the issue on their part their actions can be considered sensible - we are just spamming them with non issue.

As I mentioned it would seem that bindings for D pad - which are used for map, got merged with "look" controls used for flying.

Try rebinding D-pad controls to anything and it will change tooltips on map and so on, but it does nothing.
I mentioned that under their main post for this issue https://geometa.co.uk/support/carriercommand/18857

We will see what they say, I am 90% sure this is the root of the issue, in worst case I was considering going back to the table and trying to figure out which set of keys used to be plane controls.

I might have older version of the game on my previous PC - this could help to identify those.

As for cooperation, sure, just send me friend invite and we can tinker a bit together.

[Scythan]

Originally posted by Konri_one (K_o):

So hey Scythan~

I already saw the posts on geometa portal, while I find devs "dismissive" to put it diplomatically, lets remember, facts not emotions, since they cannot find the issue on their part their actions can be considered sensible - we are just spamming them with non issue.

As I mentioned it would seem that bindings for D pad - which are used for map, got merged with "look" controls used for flying.

Try rebinding D-pad controls to anything and it will change tooltips on map and so on, but it does nothing.
I mentioned that under their main post for this issue https://geometa.co.uk/support/carriercommand/18857

We will see what they say, I am 90% sure this is the root of the issue, in worst case I was considering going back to the table and trying to figure out which set of keys used to be plane controls.

I might have older version of the game on my previous PC - this could help to identify those.

As for cooperation, sure, just send me friend invite and we can tinker a bit together.

Sent.

I think you're onto something, I didn't see it as a breakdown of communication, I followed your link and I think they're confused on what they did. Which is odd as a bit of playtesting would confirm this, and you'd think in the torrent of comments someone would have sat down and PLAYED the game to see what everyone was complaining about.

they think all they've done is merged ground and air but what they've ACTUALLY done is merged map (what you call d-pad and what they call look) and air.

Meaning I either can exclusively replace map OR air controls with WASD but not both.

So, how do we fix this?

[Mr.Greykat]

Originally posted by Scythan:

So, how do we fix this?

By default "Mouse Flight Control mode" is turned on.
-> Temp solution is to rebind "Look up", "Look down", "Look left", "Look right" to WASD respectively.

If "Mouse Flight Control mode" is off:
Throttle/Yaw = WASD
Pitch/Roll = Arrowkeys (Look <dir>)

If "Mouse Flight Control mode" is on:
Throttle/Yaw or Throttle/Roll = Arrowkeys (Look <dir>)
Pitch/Roll or Pitch/Yaw = mouse

Commented on the issue ticket on dev site. I hope it will be resolved soon(tm).

[Konri_one (K_o)]

Thank you @Mr.Greykat, seems you found a missing piece in the puzzle that was bothering me.
Did you by chance check how changing Mouse Flight Control affects D-pad keys? Since again, those are supposed to be map controls but do nothing - those only change visual keys displayed in tool tips for map and planes...

[Mr.Greykat]

Originally posted by Konri_one (K_o):

Thank you @Mr.Greykat, seems you found a missing piece in the puzzle that was bothering me.
Did you by chance check how changing Mouse Flight Control affects D-pad keys? Since again, those are supposed to be map controls but do nothing - those only change visual keys displayed in tool tips for map and planes...

Yeah about that...

From what I observed it rebinding the (Look <directions>) not intefer with menus, but on the holo-map or the other maps where you can pan the map.

Panning North/South now conflicts with zoom in/out on the map....
Panning the map by click-dragging the mouse still works thou.

A minor annoyance, but somewhat playable.

[Acer Spacer]

Glitch is still here. Hopefully it gets fixed eventually