Elite Dangerous Horizons/Odyssey Plugin (XML edition) Odyssey 18.07

Hi, verify inside the XML if you have the one dated <!-- 2023 February 02 -->
If its the same date, there could be 2 possibility,
1- Not perfect pointer that work for everyone (ill have to search better pointers) Not impossible but unlikely.
2- Some Antivirus / protection /sandboxing software can prevent the memory hooking.

If you still can't find out why it's not working, I could maybe check on your computer directly with teamviewer or any other software to check it myself another day.

Try Legacy Horizons instead of Odyssey and see if you get motion.

thanks for your replies
Yes I get motion with Legacy.

I have a non-key version of Elite Dangerous, meaning I can only start it from steam,
but not directly with EDLaunch.exe
XML dated 2023 February 02
nothing prevents memory hooking, never had a problem with it.

I guess that this non-key version is probably different than the one we launch on the EDLaunch. Mine is on steam too but it launch the EDLauncher.

My steam account is linked to my frontier account, thus steam logs me in without my frontier login/PW
and launches Edlauncher too. I cannot launch the game without steam, because I did not buy it on the frontier store. I don't think the version is different, I would say the memory pointer does not work for me.
But for now it is ok, just experimenting with the game, the motion rig and VR.
I don't even know the difference between Legacy and Horizons

If the exe if slightly different, that is enough to make the pointer fail. So it's quite possible le that my pointer are not made for this version.
legacy is based on a different u diverse version an I think it also use cheaper graphics (faster in VR) so it's not bad for testing VR and motion. Anyway, enjoy.

Attached my file sizes and versions which you could compare to yours

It's not on the EDLaunch that i'm hoking, it's the EliteDangerous executable
located in "\Elite Dangerous\Products\elite-dangerous-odyssey-64\EliteDangerous64.exe"

ok, i have 2 versions, one with your executable, probably in the Legacy folder,
and another older file version 3.8.14.0 in the default folder.
So I may just use pointers from that version, if it was made.
I purchased it june 22.
Or maybe copy the working executable...

the path seems to be the issue.
The plugin check if it's odyssey is loaded if it find "odyssey" in the path. If not found, it use the pointers for the "legacy"

Maybe you can hack around the path and add "odyssey" somewhere so the plugin will use the odyssey pointers.

On my end it's this for odyssey/horizon (non legacy) : SteamLibrary\steamapps\common\Elite Dangerous\Products\elite-dangerous-odyssey-64

legacy path : E:\SteamLibrary\steamapps\common\Elite Dangerous\Products\elite-dangerous-64

The plugin check the path, if it find the string "odyssey" it will load the pointers for odyssey; if not, it load the legacy one.

I will try to update the plugin to also recognize the FORC-FDEV-DO-38-IN-40 as an odyssey executable.

Wagnard updated Elite Dangerous Horizons/Odyssey Plugin (XML edition) with a new update entry:

Odyssey detection fix.

Read the rest of this update entry...

@TomSawyer2112 I just posted a new version with a potential fix for your path.

WOW, great, Elite Horizons has motion now, thanks a lot.

My pleasure and thanks to you for reporting, I wasn't aware of this path. This will probably fix the issues for others that didn't try to contact me as I'm sure you were not alone with this patch.

It is incredibly more fun with motion on triple screen, will check VR tonight
I only had to invert the Roll, to make it behave like a flying object, not like a car.

unfortunately still not working for me...
Is there a way to uninstall and freshly reinstall everything about the plugin?

does legacy work ? can you show us some path / details ?
If legacy horizon and the 4.0 one is both not working, then I don't think the plugin is at cause here.

Legacy doesn't work as well.
I should be seeing movement on the Sim Tools screen on this, right?:


And here are the folders:


let me know if you need any more info.

The date on the XML offset is 2019 that's is really old, probably you don't have the latest. what is inside that file?
plugin seems old too, it should be dated from today