Very minor in the scheme of things... so why am I so bloody annoyed by it?

Stonelaughter

Stonelaughter
I have "trigger" set to primary fire and "tiny little button at the base of the stick" bound to secondary fire.

As the DSS has no secondary fire requirement, I used the secondary fire button in Horizons to activate "view far side of planet" in the DSS. I've got used to it - muscle memory is a real thing.

However, in Odyssey, you can have one or the other. It will unbind from secondary fire if you bind to "far side view".

These two functions are not in conflict, FDev!!!

Issue Tracker

issues.frontierstore.net issues.frontierstore.net
 

Caydran

Caydran
I think the problem may be this?

In the game bindings menu, there are two columns.

The one on the right seems to be more for JS/Controller buttons and axises, the one on the left seems to be more for KB/Controller keys axises.

So, I have found that you can use the same JS/Controller button in both the left and right columns, even on the same row, and the bindings file will accept it without unbinding, as long as the same key is not listed twice in the same column somewhere.

The trick seems to be a "column" check for bound key duplicates, if in the same column.

If the same key is not listed twice in the one column, it will accept it without unbinding the same key in other column.

So, try listing your secondary trigger key in the first and second columns, even on the same row, for the appropriate keybind.

Works for me. I have the same bound key in two different columns for the same keybind, but one bound key will only function when I am in a sub-menu, like DSS.
 
Last edited:

Caydran

Caydran
Interesting, In Odyssey, the column trick does not work anymore. It only seems to work in Horizons and ED.

Odyssey seems to work correctly now. You can assign Joystick buttons in column#1 and in Column#2, but they will unbind now as a duplicate assignment of the same button.

Your bug report is correct. They fixed it, dammit.

EDIT: I confirmed your bug.

The secondary fire button is a Combat Mode assignment, it should allow the bind because it is an "Analysis Mode" button assignment, even though it is the same controller button. Fdev should allow for this in the DSS sub-menu, as this is in Analysis Mode.
 
Last edited:

yianniv

yianniv
Take a backup of your bindings file. Then, with a text editor try and find the location in it where those settings are stored, and enter the desired value directly.
I've done it successfully for some fa on/off setting. The game will accept it as long as you don't try to edit this value in the game again.
 

Agony_Aunt

Agony_Aunt
Stonelaughter said:
I have "trigger" set to primary fire and "tiny little button at the base of the stick" bound to secondary fire.

As the DSS has no secondary fire requirement, I used the secondary fire button in Horizons to activate "view far side of planet" in the DSS. I've got used to it - muscle memory is a real thing.

However, in Odyssey, you can have one or the other. It will unbind from secondary fire if you bind to "far side view".

These two functions are not in conflict, FDev!!!

Issue Tracker

issues.frontierstore.net issues.frontierstore.net
Click to expand...

Ugh, don't get me started on this.

I used to have shift key which worked as exit (back out) all menus. But in Odyssey, it only works on some menus and if i try and bind the other binding for the same function to the same key, which does the same thing, just on a different menu, it thinks its a conflict and unassigns the other binding.
 

Agony_Aunt

Agony_Aunt
Paul Eddington said:
I think the problem may be this?

In the game bindings menu, there are two columns.

The one on the right seems to be more for JS/Controller buttons and axises, the one on the left seems to be more for KB/Controller keys axises.

So, I have found that you can use the same JS/Controller button in both the left and right columns, even on the same row, and the bindings file will accept it without unbinding, as long as the same key is not listed twice in the same column somewhere.

The trick seems to be a "column" check for bound key duplicates, if in the same column.

If the same key is not listed twice in the one column, it will accept it without unbinding the same key in other column.

So, try listing your secondary trigger key in the first and second columns, even on the same row, for the appropriate keybind.

Works for me. I have the same bound key in two different columns for the same keybind, but one bound key will only function when I am in a sub-menu, like DSS.
Click to expand...

Ooooh, i'll have a look at this. Thank you very much kind sir!
 

Treya

Treya
Stonelaughter said:
These two functions are not in conflict, FDev!!!
Click to expand...
They can potentially conflict because FDev forgot to add a binding option for "Fire DSS Probe". The button for that follows the trigger used to enter DSS mode. Assign the DSS to secondary fire in a fire group and you have a conflict.
Apparently a dev noticed that and added a check for EDO but didn't bother to actually fix the problem by adding that missing binding option.

As a workaround you could put "View far side" on a different binding and then use a makro to send that binding when you press secondary fire.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom