Lesson learned with elite dangerous and swapping ram slots *its bad*

So yesterday, I was playing the game like normal, no problems. Today after about 2 hours of cleaning my computer, taking the ram out, adjusting some fans just general maintainance, i wound up swapping the ram slots because i realized i accedentially placed my fan in such a manner that caused it to blow heat back into the case instead of out. That was the ONLY change i made, other than cleaning fans and to my knowledge fans dont store data. I now cannot access my custom 4.0 binds and have to redo ALL of my x56 binds. Frontier...can you people just....NOT use the %localappdata% folder for important stuff like GRAPHICS AND BINDS?!

Edit: Update to the situation on page 4
 
Last edited:
  • Like (+1)
Reactions: Imo
RAM doesn't work that way. If you disconnected your USB devices you might have plugged them in in a different order though which will cause Windows to treat them differently because USB is a garbage-tier standard.
yeah my guy it doesnt work the way you think either. the way i fixed it was finding "custom.4.0.binds.7482930274824769.backup" and deleting the "7482930274824769.backup" part and it fixed it. doesnt excuse the fact that this happened because i swapped ram. and yes i DID change the slots it was plugged into multiple times BEFORE i changed ram and it didnt cause issues, and the ONE time i changed the ram slots, it then caused issues. JUST THE SLOTS. I upgraded my ram yesterday and put it in the same slots and ZERO issue.
 
Moving the ram caused a full system check on next boot at the BIOS level, USB initialized your X56 in a different order, and ED did what it does and tossed your binds.
No, it's not really excusable on Fdevs part. But the location of the binds is not the issue. It's games insistence on chunking your binds every time a frog farts in the Amazon, or the queen has tea, or my brother ends up in jail, or the sun rises over Tokyo.

Don't fly without rebuy, and back up your binds.
 
Moving the ram caused a full system check on next boot at the BIOS level, USB initialized your X56 in a different order, and ED did what it does and tossed your binds.
No, it's not really excusable on Fdevs part. But the location of the binds is not the issue. It's games insistence on chunking your binds every time a frog farts in the Amazon, or the queen has tea, or my brother ends up in jail, or the sun rises over Tokyo.

Don't fly without rebuy, and back up your binds.
This.
I was going to say maybe you knocked an internal USB board but either way…
 
Let me tell you of the days of high adventure and 8 slots of 8GB of RAM each running in quad channel on a nearing 10 year old computer...

On the other hand, I haven't had too many binding file issues over the years, just a couple when switching and upgrading controllers - knock on wood.
 
This is not how it works. This is not how any of this works. As much as Elite's bindings management suc- is sub-par, RAM has nothing to do with either %localappdata% or whatever else the OP mentioned. When a pc is shut down and off the grid, you could swap your ram with sliced eggplant and back and your pc will know no better as soon as you boot it up again. Just make sure to properly clean the slots after the eggplant.

TL;DR - if your PC is powered down, ram modules are as good as dog sticks.
 
This is primarily an issue with Windows. The only fault on FDev's part is that they still don't access devices directly.

This is relatively easy to fix. The information at ventorvar.com/posts/joystick-intro/ is for a different game, but worked perfectly for ED and several other games I play.
 
Last edited:
This is not how it works. This is not how any of this works. As much as Elite's bindings management suc- is sub-par, RAM has nothing to do with either %localappdata% or whatever else the OP mentioned. When a pc is shut down and off the grid, you could swap your ram with sliced eggplant and back and your pc will know no better as soon as you boot it up again. Just make sure to properly clean the slots after the eggplant.

TL;DR - if your PC is powered down, ram modules are as good as dog sticks.
Right, but that's assuming things are working in the first place. I've seen Microsoft via Windows mess up a lot of stuff for no good reason the last several years, one of the many reasons I personally still use Windows 7, and a couple Linux distros.

I'm assuming the OP didn't quite seat one of the modules well enough, or changed the parallel channel usage accidentally and booted into Windows. Chance that might trigger something in Windows, I suppose. I mean, you know, other than accidentally swapping USB ports, etc. 🤷‍♂️
 
Last edited:
I don't remember ever having this issue with Win 7,unless I switched USB ports. Win 10 randomly changes device presentation order for seemingly no reason. I did have to utilize Vjoy and Joystick Gremlin to get full use of my Virpil throttle under Win 7. The random device order issue didn't appear to start until I built a new Win 10 PC last year. Setting up devreorder resolved the issue, and makes it possible to switch USB ports as well. I found a way to stop the link preview, so I've included a clickable link below.

Devreorder:https://ventorvar.com/posts/joystick-intro/
 
Last edited:
Right, but that's assuming things are working in the first place. I've seen Microsoft via Windows mess up a lot of stuff for no good reason the last several years, one of the many reasons I personally still use Windows 7, and a couple Linux distros.

I'm assuming the OP didn't quite seat one of the modules well enough, or changed the parallel channel usage accidentally and booted into Windows. Chance that might trigger something in Windows, I suppose. I mean, you know, other than accidentally swapping USB ports, etc. 🤷‍♂️

No, no chance at all, that really isn't how any of this works.
 
I don't know why people have so many problems with binds. My custom X56 binds only ever need replacing when I change the machine (which I did recently). Just take a back-up any time you change the bindings, and you are covered whatever you do.

Must be said, some people have very funny ideas of how computers work...
 
No, no chance at all, that really isn't how any of this works.
No, there is a chance, just not likely. There could be any number of bugs based on changing the amounts of RAM from not being seated, goofy controllers on the motherboard that affect USB ports, BIOS, goofy drivers, software etc. Computers aren't magic. They're a lot of mess relying on a lot of things to work as we think they should and how we want them to and there are a lot of different people doing different things that don't know what each other are doing beyond some given documentation that might not account for other factors just to get a computer to that point.

I'm not saying that's what going here necessarily though, just pointing it out.
 
Don't fly without rebuy, and back up your binds.

Just to add to that....

A while back I lost all my keybinds after an update (first and only time it's happened) and I felt quite smug knowing that I'd backed them up.
Copied them into the correct folder and.... nothing.
Wasn't quite so smug after that.

Turned out that the game had, at some point, made several different "versions" of a variety of files.
Can't recall what they were but there were a bunch of files, including the keybinds, with added 01, 02, 03, 04 and 05 suffixes.
My backed-up keybind files didn't have those suffixes.

Ended up having to figure out which was the most recent version of each file and then manually added a similar suffix to the various keybind files to get it working.

Made for a tense half hour but it wasn't that hard to do and if you're smart enough to copy/paste the keybinds you're probably also smart enough to rename them if necessary.
Isn't always as simple as a straightforward cut/paste though.
 
Maybe FDev leave these things as they are; a bit tough to get right (editing a filename, etc), to sorta keep with letting you do what you want. Once you make a custom file for controls, it stays good now (well, better than before, yes version matters, but now can switch between EDO and EDH properly), but if you dont and loose bindings enough times, you figure it out. And without that, maybe some would take much longer to learn these things are editable in ED and other games too. Apply this to HUD colours, maybe other things, and it holds true.

Thanks FDev :)
 
Back
Top Bottom