I always wondered about gankers. Do they have an organization, a discord page...or are they just unaffiliated randos? Is there a club already?

Finally jumping back into Elite after a year long hiatus!

I still have my squadron with one other guy that plays consistently.

Anyone interested in flying with a couple of rusty, but experienced pilots?

Trade, Combat, Engineering, Exploration, Xeno research.

We have most ships, mostly outfitted and engineered.

We own 2 carriers and we have plenty of billions to keep us going.

UK & EST time zone

I finally got my Corvette so I am trying to outfit it now. Looked up the 7A prismatic shield generator on Inara.cz and flew to the nearest station that is supposed to have it. No dice. Tried 5 more stations based on inara and none of them have it in stock. Am I using the website wrong or is it less accurate than it used to be? (I'm coming back after 5 years or so) The station updates were between 1 and 6 days ago. Most were 1-2 days old

See if you can discover why this E:D binds file will not work as written. With one change, it will.

Sorry, the binds file is over Reddit's character limit for posts (40k, while it is 58K+), therefore the need to link to the daft copy.

Feel free to copy it for your own use, and change it as you please to fit your needs. As stated before, you will need to make one small change to get it to work as written. If you read my previous article, you'll have no trouble finding and making the ONE change to make it work.

[hint: it isn't a Horizons file] :)

https://www.reddit.com/user/Dustball414CA/draft/5374bd68-6f4e-11ee-8c6c-d2936df56d87

The reason why WinWing Orion 2 HOTAS does not work properly in Elite:Dangerous - and a solution!

Ok, so after much beating of my head against the wall that is WinWing, I have discovered..

1. Elite: Dangerous’ 32 key binding limit is both dumb and stupid;
2. WinWing did us all an extreme disservice by saddling us with the worst software they could invent;
3. No amount of tweaking WW’s SimAppPro is going to make any change to the file format that E:D uses in-game;
4. And why in God’s name won’t WW make their Z-Axis adaptor available – it’s only been unavailable for more than two years…

In the end, WWO2 HOTAS and E:D are completely incompatible as they stand right out of the box, that is, if you want to use more than 32 buttons.

That having been said, all is not lost. Because even though WW has some of THE WORST customer service I’ve ever encountered, they still make one hell of a product. Allow me to explain..

There is nothing wrong with E:D’s binds file configuration, it just needs to be tweaked for WWO2 HOTAS to be put to good use. Since WWO2 has way more than 32 buttons, you need to trick E:D into thinking that there are only 32 buttons being used at any given time. The solution is simple.. You trick E:D into thinking there is more than one device, and that they only have 32 buttons each!

We all know that E:D has a nasty 32 button limit and that WWO2 HOTAS has more buttons, knobs and switches than you can shake a stick at. So, how the hell do you get the two to “see” each other? Simple, split your WWO2 HOTAS into four (4) separate VIRTUAL DEVICES (six, exactly, but more on that later..).

And the really great news is you do NOT need SimAppPro to do it! Though, you may/do need it running in the background when playing to make this work. But I promise, no SimAppPro programing is required.

What you do need is a text editor, such as Notepad, to make the madness stop.

What is the one thing that HOSAS players know, that HOTAS players may not have known this whole time? You need to split devices with more than 32 buttons up into devices with 32 or fewer buttons for E:D to make use of them.

If you have a device, say a Logitech Extreme 3D Pro, you’ve nothing to worry about as far as E:D’s 32 button limit, because you only have 12 buttons to work with. But you could also use a modifier to change what those buttons do for certain situations. Such as telling E:D you want to lower the landing gear, you’d use a modifier to trigger say, button 10 to a different setting within your E:D device’s binds file. So instead of firing off a heat sink to that of lowering the landing gear and you’d still be well within the 32 button limit because you’re using a modifier.

Now, if you have plenty of buttons to go around, didn’t see the need to use a modifier and wanted to make things easy on yourself, you just split up the one (1) physical device into two (2) or more virtual devices and assign what you want to wherever you want it!

Those devices might look like this:

Primary Joystick would be called: DeviceIndex="0"

And written so E:D could make use of it as:

<Binding Device="4098BEA9" DeviceIndex="0" Key="Joy_XAxis" />

A Second Joystick would be called: DeviceIndex="1"

And written as:

<Binding Device="4098BEA9" DeviceIndex="1" Key="Joy_XAxis" />

Notice the command, Binding Device="4098BEA9"

“4098BEA9” is from WW’s SimAppPro. It is telling us that this is an F-16 joystick and “4098BEA9” is the device’s identifier. If it was “4098BE62”, that would be an F-18 Throttle identifier.

So, since we have two (2) physical devices, it is possible to have up to EIGHT (8) virtual devices at one time.

A second physical device, like say a throttle, could be written as:

<Binding Device="4098BE62" DeviceIndex="2" Key="Key_0" />

Because it is listed as an entirely different binding device you could have another 32 buttons to assign 32 other commands to.

Throttle - Primary Device="4098BE62" DeviceIndex="x"; where x equals 0, 1, 2, or 3.

Example:

<Binding Device="4098BE62" DeviceIndex="0" Key="Key_X" />
<Binding Device="4098BE62" DeviceIndex="1" Key="Key_X" />
<Binding Device="4098BE62" DeviceIndex="2" Key="Key_X" />
<Binding Device="4098BE62" DeviceIndex="3" Key="Key_3" />

The thing that throws people for a loop is the numbering scheme used for a given manufacturer’s device. Which is key to binding correctly in E:D.

WinWing’s Orion 2 HOTAS has 42 buttons on their F-16 stick. Their F-18 throttle has 27 buttons and switches on the handle, with another 84(!) on the base. Giving us an amazing total of 111 control surfaces – on the throttle unit alone!!

How in the world do you get E:D to see, much less use, all this buttons?!?

The key is splitting up the device into four (4) virtual devices. And giving each of those virtual devices no more than 32 buttons/controls at a time. Also, each group of 32 would be numbered 1-32 each of those four times.

So, in the end, you’d need to divide the stick into two (2) virtual devices (1 device with 32 buttons/controls and one with 10) and the throttle into four (4) virtual devices, three (3) with 43 buttons/controls) the last one with 15 controls. Or you can divide the controls into however many you want, so long as you do not go over 32.

Example:

<Binding Device="4098BEA9" DeviceIndex="0" Key="Joy_XAxis" />
<Binding Device="4098BEA9" DeviceIndex="1" Key="Joy_XAxis" />
<Binding Device="4098BE62" DeviceIndex="0" Key="Key_X" />
<Binding Device="4098BE62" DeviceIndex="1" Key="Key_X" />
<Binding Device="4098BE62" DeviceIndex="2" Key="Key_X" />
<Binding Device="4098BE62" DeviceIndex="3" Key="Key_X" />

The following example uses the 32 button limit native in E:D –

<UseBoostJuice>
    <Primary Device="Keyboard" Key="Key_Tab" />
    <Secondary Device="4098BE62" Key="Joy_16" />
</UseBoostJuice>

Notice how there isn’t any “Binding Device”. But there is a call to what device the game is to use as both Primary and Secondary devices.

Primary is “Keyboard”.

Secondary is “4098BE62” - the O2 throttle.

--------------------------------------------------------

Here is an example of using “DeviceIndex=” and a modifier:

<AheadThrust>
    </Binding Device="4098BE62" DeviceIndex="0" Key="Joy_RXAxis" />
    <Inverted Value="1" />
    <Deadzone Value="0.25000000" />
</AheadThrust>
<ForwardThrustButton>
    <Primary Device="4098BE62" DeviceIndex="0" Key="Neg_Joy_RYAxis">
    <Modifier Device="4098BE62" DeviceIndex="0" Key="Neg_Joy_RXAxis" />
</Primary>
    <Secondary Device="{NoDevice}" Key="" />
    </ForwardThrustButton>
<BackwardThrustButton>
      <Primary Device="4098BE62" DeviceIndex="0" Key="Pos_Joy_RYAxis">
      <Modifier Device="4098BE62" DeviceIndex="0" Key="Pos_Joy_RXAxis" />  
</Primary>
	<Secondary Device="{NoDevice}" Key="" />
</BackwardThrustButton>

Example of using a modifier alone:

<ForwardThrustButton>  
<Primary Device="LogitechExtreme3DPro" Key="Joy_POV1Up">
	<Modifier Device="LogitechExtreme3DPro" Key="Joy_11" />
	</Primary>
	<Secondary Device="{NoDevice}" Key="" />
</ForwardThrustButton>

Here’s an example of using both a Z-axis joystick and rudder pedals to bind the same function (and it works!):

<YawAxisRaw>  
    <Binding Device="LogitechExtreme3DPro" Key="Joy_RZAxis" />
        <Inverted Value="0" />
	<Deadzone Value="0.20000000" />
</YawAxisRaw>
<YawLeftButton>
    <Primary Device="Keyboard" Key="Key_A" />
    <Secondary Device="T-Rudder" Key="Pos_Joy_ZAxis">
        <Hold Value="1" />
    </Secondary>
</YawLeftButton>
<YawRightButton>
    <Primary Device="Keyboard" Key="Key_D" />
    <Secondary Device="T-Rudder" Key="Neg_Joy_ZAxis">
	<Hold Value="1" />
	</Secondary>
</YawRightButton>

NOTE: If you have a joystick that does NOT have a Z-Axis, you (really!) need to use rudder pedals.

NOTE: All examples are from my own, working binds files for E:D.

Something else to make note of.. When you go looking for the binds files, they are found here:

C:\Users\[SOMEONES_NAME_HERE]\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings

In there you will find several files. Files you do not need to copy:

BindingLoadingErrors.log – Tells you where you screwed up writing your binds or missing hardware/devices.

StartPreset.4.start – Tells you what files will start and control what section in game.

COPY the rest, and place them in a SEPARATE folder location far, far away from where you found them. If you screw up writing to these files, you still have the master files to copy from again.

DO NOT OVERWRITE THESE MASTER FILES!!!

Personally, I have a few different copies of these and keep them separate at all times. It’s a good practice to keep those files you’re working on separate from everything else – just in case you screw up, and you will. I’ve done it many times myself, and will do so again, of this I am certain.

Horizions files first two lines look like this:

<?xml version="1.0" encoding="UTF-8" ?>
<Root PresetName="TEST_1" MajorVersion="3" MinorVersion="0">

Odyssey files look like this:

<?xml version="1.0" encoding="UTF-8" ?>
<Root PresetName=" TEST_1" MajorVersion="4" MinorVersion="0">

Notice the “MajorVersion=” is different. Horizions is 3. Odyssey is 4. You cannot mix and match these files. Ie, A 4 configuration will not work in Horizions. And vice versa. Because you’ve told the game to read a file type it knows little to nothing about. Kinda like telling Windows 3.11 to read a Windows 10 file. It may know it’s there, but hasn’t a clue what to do with it.

Another thing to remember when editing these binds files is naming. You can name the file itself as whatever you feel like, say, “This_is_my_binds_file.binds” But the game doesn’t care what name you gave it, only that it is in the folder it needs to be in to be seen, and the name the game is looking at INSIDE the file.

For example, the file name for your OS is “This_is_my_binds_file.binds”, but the INTERNAL, E:D name is whatever the “Root PresetName=” is:

Example:

<Root PresetName="LE3DProWWT" MajorVersion="4" MinorVersion="0">

This tells me that the name I can expect to see in-game is “LE3DProWWT” and that it is an Odyssey file.

In-game, as part of the list of profiles available to use, you might see something like this:

DEFAULT
LE3DProWWT
Keyboard Only
Keyboard & Mouse
Custom

Also, you can only have up to three (3) homemade profiles at a time.

--------------------------------------------------------

Here’s some info you may find useful, including an example of what a binds file looks like inside.

Winwing Orion 2 Throttle:  
    <Binding Device="4098BE62" DeviceIndex="0" Key="Joy_RZAxis"
Winwing Orion 2 Joystick:  
    <Binding Device="4098BEA9" DeviceIndex="0" Key="Joy_XAxis"
Xbox Controller:  
    <Binding Device="045E02EA" Key="Pad_RStickX" />
Logitech Extreme 3D Pro:  
    <Binding Device="LogitechExtreme3DPro" Key="Joy_RZAxis" />

..install a REFINERY!!!

Limpets - CHECK. Plenty of cargo space - CHECK. Pizza, be-ah and assorted snacks - CHECK. Filled up on explosives to crack big-azzed rocks - CHECK.

Can't figure out why you limpets aren't running out to gather all that sweet Alexandriaum.. it may be because you left the refinery unit sitting in the hanger bay..!!! ARGH!!!!!

Since you can't post material on the other r/ maybe you guys would like a laugh.

If you are looking for a Thargoid battle over a surface base, then come to Asher Barracks. The combat is tight, and with multiple live players the action is pretty awesome.

Ever been flying thru space on thrusters and wondered "How fast am I going compared to actual modern craft?"

This quote from a science article will add some perspective:

"The fastest object ever built by humans is the Parker Solar Probe, which reached 163 kilometers per second in 2021."

That probe hits 350,000kph!

.

Using filters in galaxy map, I can isolate guardian systems near ETA Carina. But there are more than 2 dozen guardian systems in the Norma Expanse....and none of them show up in a filtered search.

Wtf? Over.

Note: I am currently in deep space, and no way to test this question myself

Goal: to line up my ships on a planet surface.

Question: if I landed right next to a surface base or settlement (that has a hangar), could I disembark, goto the base and climb into another of my ships...would the first ship still be parked there? Would I even be able to reenter the base?

.

I have worked about a month on this...hope you all enjoy the story and channel lore. It has made me cry upon completion. Thankyou and enjoy

https://www.youtube.com/watch?v=HQ2bF_VFEwg

Embark on a gripping journey through a future Earth, ravaged by war and united under a dominant nation. "Aspirations" takes you on a thrilling cinematic adventure, following a hero torn between duty and love.

Witness epic space battles, heartfelt reunions, and the struggle for freedom in the vast expanse of Elite Dangerous. Brace yourself for a fan-made masterpiece that will leave you on the edge of your seat.

Join us in this mesmerizing tale of courage, sacrifice, and the pursuit of dreams. Elite Dangerous + Horizons and Odyssey have always held a special place in my heart. On the sheer cosmic scale and amplitude of space has always been awe inspiring.

What could be out there? Is there anything out there? What is it that we do not know and what can we achieve? All greater questions of humanity in the pursuit of knowledge and indulgence on exploration. We hope to conquer and achieve all that is creation to be under our rule.

Hey I’m looking for sponsors for my new group Explorers United, we’ve been working for awhile and we were wondering if any rich players were looking to spend an absurd amount of money on helping us build up!

Found this planet with Recepta signals on it. It took me "only" 8.4 hours searching at low altitude to find this single field, despite the DSS showing plenty of blue areas scattered around. Finally there we have them, R. conditivus, lime, located near the equator (lat -1.58) in a green flat area, temp 250K. Will post system name once i've sold the data.

Field of hard to find R. Conditivus