Bindings dissapear, again...

Beerwielder

B
I just can't belive this can happen in this game after so many years, again after an update ( or maybe I can, knowing all the other crap we've had to put up with). My bindings dissapared WHILE I was playing :-(
WHY the should I have to spend time figuring out how to restore the bindings (if I was lucky enough to know how to back the up in the fist place)?!? It takes a lot of time and effort to set up new bindings for HOTAS, probably for other controllers as well, so this is a clear sign that Frontier dosen't give a Sh** about peoples time.
People new to the game probably just leave if the have to cope with this.
Shame on You Frontier :-(
For those who say it's easy to fix... well, if you've done it som many times it's easy to fix, just say it all...
 

Beerwielder

B
Another thing. My custom binds file dosen't show up as an option at all. Even though the preset name in the file is correct. Start preset file change to keyboardmouseonly no matter what I put in there.
 

Tyres O'Flaherty

Tyres O'Flaherty
Beerwielder said:
I just can't belive this can happen in this game after so many years, again after an update ( or maybe I can, knowing all the other crap we've had to put up with). My bindings dissapared WHILE I was playing :-(
WHY the should I have to spend time figuring out how to restore the bindings (if I was lucky enough to know how to back the up in the fist place)?!? It takes a lot of time and effort to set up new bindings for HOTAS, probably for other controllers as well, so this is a clear sign that Frontier dosen't give a Sh** about peoples time.
People new to the game probably just leave if the have to cope with this.
Shame on You Frontier :-(
For those who say it's easy to fix... well, if you've done it som many times it's easy to fix, just say it all...
Click to expand...
All you need to do is copy the file to another place - different directory, drive, USB etc. - then, if your bindings go AWOL again, just copy it back.

The file ED uses is usually here:

C:\Users\YOURNAME\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings

If ypi are Odyssey player, the file you want is Custom.4.1.binds
 

Ashnak

Ashnak
Failed to find GUID for device: 33448198

That means that (one of) your input device(s) wasn't available any more - for whatever reason. In this case, ED defaults to KB+M.
Usual repair is to first get that device working again, then restart ED.

Reasons could be as trivial as a power problem (a few sticks are notorious for that) or plugging the stick into a different USB port (in that case, you can write a letter to Microsoft). Your bindings are still there - until you start to "repair" them. If you want to keep a backupo of your bindings - don't keep it in the bindings directory. That is a sure way to confuse ED when it reads in the bindings at startup.
 

the100thmonkey

the100thmonkey
Change the bindings filename to something different, keeping the .4.1 part, e.g. "hotas.4.1.binds"

Open the bindings file in notepad (right click > open with > select notepad).

Then change "Custom" in the second line to match the name of the file. Keep the "Major version" and "Minor version" bits as "4" and "1" respectively.

Save and close.

Doing this prevents your bindings file being overwritten and gives the bindings their own entry in the controls dropdown menu.

If the bindings don't appear in the menu, it means that one of the devices listed in the file is missing or otherwise has not been detected. You should then follow Ashnak's advice.
 

Beerwielder

B
Thank you for trying to help. All three devices are working. I started with a Blank bind and all three was registered when i tried to bind something. I saved it and after that the custom bind showed up as an option. The new revison is 4.2 btw. I changed the bind file to the one with my binds and it was gone again :-(
So it seems I can start doing the binds all over again (Not gonna happen) but not load my old binds.
 

Ashnak

Ashnak
Same here. I got a StartPreset.4.start, the generic Custom.4.1.binds and my ConstellationAlpha.4.1.binds (and a lot of older junk).
 

the100thmonkey

the100thmonkey
Beerwielder said:
Thank you for trying to help. All three devices are working. I started with a Blank bind and all three was registered when i tried to bind something. I saved it and after that the custom bind showed up as an option. The new revison is 4.2 btw. I changed the bind file to the one with my binds and it was gone again :-(
So it seems I can start doing the binds all over again (Not gonna happen) but not load my old binds.
Click to expand...
See Ashnak's post - you have a device that is referenced in the bindings file which is no longer available.

You can Use USBDeview to see a list of all the devices attached to your system. The device ID identified by Ashnak is 33448198 - 3344 is the vendor Id (VID) and 8198 is the product ID (PID). It is often written 3344:8198. In USBDeview, there are separate columns for VIP and PID.

3344 is a known vendor ID for Virpil devices. Have you got the driver or calibration software installed? Have you made any changes to the stick in software and flashed it to the device? I recall reading recently that Virpil devices change PIDs if you flash the stick (which you will do if you reprogram it). That will cause the game client to throw a wobbly and refuse to load hte binds file.

The frustrating thing here is that the game has a very flexible and therefore powerful control scheme, but it doesn't give you enough information.
 
Last edited:

Bravo17

B
Tyres O'Flaherty said:
Ah! Thanks for the info!

EDIT: Actually... I'm not seeing a 4.2 binds file. Did they change the path?

EDIT 2: In fact, I can't see a 4.2 file anywhere.
Click to expand...


Guess I'm just lucky!

1740866189125.png


Have you bound a key for deploying a Colonization Beacon yet?
 

STRONTIUM DOG

STRONTIUM DOG
i just renamed my 4.1 file 4.2 to keep current
if you delete the bindings folder and restart the game from the default control set any new files created are now version 4.2
i compared the two in notepad ++ but there is no difference between 4.1 and 4.2 other than the rev name of the file🤷‍♂️
 
Last edited:

Bravo17

B
STRONTIUM DOG said:
i compared the two in notepad ++ but there is no difference between 4.1 and 4.2 other than the rev name of the file🤷‍♂️
Click to expand...


Here are the differences between mine. Guess they don't appear until you bind the Colonization Module.

Code: 
    <TriggerColonisationModule>
        <Primary Device="Keyboard" Key="Key_Home">
            <Modifier Device="Keyboard" Key="Key_LeftAlt" />
        </Primary>
        <Secondary Device="{NoDevice}" Key="" />
    </TriggerColonisationModule>


    <PlaceSettlement>
        <Primary Device="Keyboard" Key="Key_T" />
        <Secondary Device="{NoDevice}" Key="" />
    </PlaceSettlement>
    <ChangeConstructionOption>
        <Primary Device="Keyboard" Key="Key_J" />
        <Secondary Device="{NoDevice}" Key="" />
    </ChangeConstructionOption>
    <RotateSettlement>
        <Binding Device="ThrustMasterWarthogCombined" Key="Joy_XAxis" />
        <Inverted Value="1" />
        <Deadzone Value="0.00000000" />
    </RotateSettlement>
    <RotateSettlementLeft>
        <Primary Device="{NoDevice}" Key="" />
        <Secondary Device="{NoDevice}" Key="" />
    </RotateSettlementLeft>
    <RotateSettlementRight>
        <Primary Device="{NoDevice}" Key="" />
        <Secondary Device="{NoDevice}" Key="" />
    </RotateSettlementRight>
    <ExitSettlementPlacementCamera>
        <Primary Device="{NoDevice}" Key="" />
        <Secondary Device="{NoDevice}" Key="" />
    </ExitSettlementPlacementCamera>
    <MovePlacementCamY>
        <Binding Device="{NoDevice}" Key="" />
        <Inverted Value="0" />
        <Deadzone Value="0.00000000" />
    </MovePlacementCamY>
    <MovePlacementCamForward>
        <Primary Device="{NoDevice}" Key="" />
        <Secondary Device="{NoDevice}" Key="" />
    </MovePlacementCamForward>
    <MovePlacementCamBackwards>
        <Primary Device="{NoDevice}" Key="" />
        <Secondary Device="{NoDevice}" Key="" />
    </MovePlacementCamBackwards>
    <MovePlacementCamX>
        <Binding Device="{NoDevice}" Key="" />
        <Inverted Value="0" />
        <Deadzone Value="0.00000000" />
    </MovePlacementCamX>
    <MovePlacementCamRight>
        <Primary Device="{NoDevice}" Key="" />
        <Secondary Device="{NoDevice}" Key="" />
    </MovePlacementCamRight>
    <MovePlacementCamLeft>
        <Primary Device="{NoDevice}" Key="" />
        <Secondary Device="{NoDevice}" Key="" />
    </MovePlacementCamLeft>
    <MovePlacementCamZ>
        <Binding Device="{NoDevice}" Key="" />
        <Inverted Value="0" />
        <Deadzone Value="0.00000000" />
    </MovePlacementCamZ>
    <MovePlacementCamUp>
        <Primary Device="Keyboard" Key="Key_W" />
        <Secondary Device="{NoDevice}" Key="" />
    </MovePlacementCamUp>
    <MovePlacementCamDown>
        <Primary Device="Keyboard" Key="Key_S" />
        <Secondary Device="{NoDevice}" Key="" />
    </MovePlacementCamDown>
    <MovePlacementCamUpAxis>
        <Binding Device="{NoDevice}" Key="" />
        <Inverted Value="0" />
        <Deadzone Value="0.00000000" />
    </MovePlacementCamUpAxis>
    <MovePlacementCamDownAxis>
        <Binding Device="{NoDevice}" Key="" />
        <Inverted Value="0" />
        <Deadzone Value="0.00000000" />
    </MovePlacementCamDownAxis>
    <PitchPlacementCamera>
        <Binding Device="ThrustMasterWarthogCombined" Key="Joy_YAxis" />
        <Inverted Value="1" />
        <Deadzone Value="0.00000000" />
    </PitchPlacementCamera>
    <PitchPlacementCameraUp>
        <Primary Device="Keyboard" Key="Key_Q" />
        <Secondary Device="{NoDevice}" Key="" />
    </PitchPlacementCameraUp>
    <PitchPlacementCameraDown>
        <Primary Device="Keyboard" Key="Key_Z" />
        <Secondary Device="{NoDevice}" Key="" />
    </PitchPlacementCameraDown>
    <YawPlacementCamera>
        <Binding Device="ThrustMasterWarthogCombined" Key="Joy_ZAxis" />
        <Inverted Value="0" />
        <Deadzone Value="0.00000000" />
    </YawPlacementCamera>
    <YawPlacementCameraRight>
        <Primary Device="Keyboard" Key="Key_D" />
        <Secondary Device="{NoDevice}" Key="" />
    </YawPlacementCameraRight>
    <YawPlacementCameraLeft>
        <Primary Device="Keyboard" Key="Key_A" />
        <Secondary Device="{NoDevice}" Key="" />
    </YawPlacementCameraLeft>
    <PlacementCamSpeedInc>
        <Primary Device="{NoDevice}" Key="" />
        <Secondary Device="{NoDevice}" Key="" />
    </PlacementCamSpeedInc>
    <PlacementCamSpeedDec>
        <Primary Device="{NoDevice}" Key="" />
        <Secondary Device="{NoDevice}" Key="" />
    </PlacementCamSpeedDec>
    <PlacementCamMouseSensitivity Value="5.00000000" />
    <PlacementCamMouseXDecay Value="1" />
    <PlacementCamMouseYDecay Value="1" />
 

Beerwielder

B
I checked the devises with USBDeview and they are all green. I have CH stick and pedals, and a Vipril Throttle and they all works fine. I can make new bindings with them and and the binding shows in game. I just can't use my old one, whitch worked fine until it suddenly didn't while I was playing.
Thanks for the help. I'l just leave the game for now. I'm not up for using hours setting it up again. I only play in VR so every thing must be assigned to buttons and it takes forever to set up.
/EB
 

Beerwielder

B
An update. The number 33448198 for my device seems to be random. By starting a Blank bind the device got another number. Using Find/Replace in my custom binds it was fixed i seconds. It worked for me since the was nothing wrong with my throttle to begin with. Thought I should let anyone know that might have the same problem.
 
You must log in or register to reply here.
Back
Top Bottom