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

Hey guys.

i have installed the plugin , patched edtc.. but when i started the simtools, it shows lite

Could not find the file

....\EliteDangerous64_Configs.xml

What i missing here please

Aw no - update 12 has killed the motion. After what seems like ages since the last ED update - really hoping @Wagnard can work his usual magic (joystick mode just isn't the same)

I'm already on it.

Here is EDH and EDO pointers for update 12.

Latest xml work great - as usual. Many thanks again @Wagnard

@Wagnard

Thank you for all that you do!!

I've had a report that the Odyssey XML is causing an issue of detection between the Spaceship and SRV. When reviewing the XML file, it looks like the Odyssey memory locations are the same for both the ship and SRV "0551D2A8" where as for Horizons its different "041D5438" for the ship and for the SRV "041CB998"

Do you think this would cause the issue of motion software being confused in Odyssey and switching back and forth between ship and SRV motion profiles?

Thanks again for finding these!

Hi.

First of all, thank yoy @Wagnard for your awesome work, getting the memory pointers is a tedious job and I really appreciate your work.

I'm the one with this switching profile issue, it happens in Oddysey only, I've tried with horizons and it seems to work correctly. Problem is that it seems every time I put joystick, pedals and throttle in neutral positions, it switches to the srv profile.

Nowadays... it seems frontier just updated the oddisey version again, so right now the motion doesn't work. It works only in Horizon

For curiosity... anybody knows how srs profile is selected? Maybe it is selected when there are switching variables on the memory pointers?

Pointer updates for update 12 Hotfix.

You rock Wagnard!! Thank you!!

Thank you very much! It works.

I'll check that but it's possible. There is no easy way to tell when we are in SRV / ship so I kind of did a few things here and here to give the sim a Hint.

Tell me if with the new pointer update you still have the issue. Also If I understand you are not using simtools ? because the stuff I did to avoid that is in the simtool plugin.

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

Odyssey update 12 hotfix

Read the rest of this update entry...

Yeah... I'm not using simtools, currently I am using SRS.
It still happens, but I suppose SRS is only getting your memory pointers to the variables to move the platform.

How SRS determine if its a spaceship or a srv I don't know, but I expect that it's doing some checks on the variables in order to select one profile or the other one depending the values on memory. At least that is what I would try.
Thanks again, pointers are working perfect.

Hi,

I can't get ED to work with flypt .
It gets connected if you look at the red box on connect , but no data is coming in .
Can anyone help me with this problem.

Does it have anything to do with pointer updates ? and how does that work

Enumerate all the steps you did to connect, so we can know if you missed something.

-I started Flypt
-Added source in flypt for elite dangerous .(connect box is yellow)
-Opended steam
-Started Elite Dangerous
-Connect source in Flypt ( connect box changes from yellow to red )

also tried to start ED first and then Flypt with same result.

It's been a while since I connected anything so other people might be better than me for checking this out.
But, ED requires Simtools, No? I don't remember a direct connection from Mover. Am I wrong?
And with Simtools, you need to patch the game.

The FlyPT Mover source for ED does not work. I had to create a custom source using Wagnard's offsets. I can provide more info when I get home, but it works rather well, and whenever a new patch comes out, you just have to change the offset address to the new one and it works as before.

Hi Nisch , that would be great I like flypt with MSFS so prefer to get ED running in it .

Here you go. You'll have to modify the rig parameters and whatnot, or just delete everything but the source module and then merge it with your current Mover profile.