LunarFlight Plugin (Steam Version)

Hi all I've been grinding away at trying to make a memoryhook plugin and I have this to present to you.

Wooohoooo A half working plugin

Its a bit ruff and it needs tweaking but Roll/Pitch work pretty well Yaw works but not in the best of ways and Heave Sway and Surge are a bit meh

Please can someone test it Let me know how it goes


Work in progress may I add

@DaVinster you were wanting this weren't you ?

Dont say that @noorbeast lol that means all the memory locations will change Looks really nice tho

Great work @SilentChill! However, when I download your plugin the .zip seems to be invalid (wont work when dragged into the plugin updater, and i can't uncompress it otherwise).

I'd looked at getting values from Lunar Flight since it seemed a bit more straightforward, but couldn't get much further than just finding the current locations with GameEngine. Glad you took a look at it after you became an expert with GTA V!

I'd love to test it as soon as I can get the plugin working. Maybe re-upload?

Looks more like Kuiper Belt Flight, lol.

If you remember the procedures you used to find the values at least it should be a little easier to find them again! Thanks for your efforts!

Works fine here I just downloaded on a different computer and it works ok ??

Can someone else try downloading it please

I get the same here, invalid folder.

Huh weird. I downloaded it from 2 browsers on my PC, 1 from my Mac.. no go. Is it supposed to be only 8 or so KB?

I have uploaded again Just to be safe

Got it! Invalid folder was 8.1kb and working one is 8.7kb.

That download worked.

I have the game patched and it connects to the game, but no motion... Nothing seems to be happening in the Output Testing Virtual Axis in Game Engine either. Maybe I'm missing something? (I did setup axis assignments for the game).

Ahh thought I was onto something- I went and downloaded the DK2 Beta version in case that's the one your wrote to. But no dice. In any case, is that the version you're running? (Hopefully so for us Rifters

This is the steam version

Sorry I have changed the title to steam version forgot there was more than one version

I got them both from Steam- it's just that I opted into the beta on steam to get the Oculus version. But I did try both.

what about the oculus version, is it good?

Actually to be clear it's worked with the DK1 for a long time, but I think the beta adds DK2 support. I haven't tried it yet but it was a pretty cool experience back with the 1. Now, DK2 + motion should be pretty amazing

Ahhh bugger I didn't realise I hadn't got the VR version, what a complete tit I am.

I've just upgraded to the VR beta version will try and get it sorted tomorrow.

@value1 you must have a secret to finding memory pointer addresses, you have the patience of a saint

With LunarFlight I can get the memory locations for Roll/Pitch/Yaw only problem is that there are about 3 addresses producing the exact same information so other than doing a pointer scan to the start of each address then restarting the game then finding the same 3 memory addresses again then trying rescan of these addresses in each of the 3 pointer scans. That means a possibilty of 9 rescans and then I restart the game to scan them again and there seems to be the real chance of me getting muddled up that I rescan all the pointer scans and get nothing lol.

I'll get there, I can find the values easy enough its just the pointers I'm having a hard time with.

I can get the values into simtools and get movement so its just these bloody pointers !!!!

hopefully tonight I will have a breakthrough

Hi Craig
To find a pointer, find your Roll, Pitch or Yaw memory location. Add this location to the lower window in CheatEngine:

In the lower window, right-click on the address and select Pointer scan for this address:


This will take a while until all the pointers are found (there might be thousands…)
Restart the Lunar Flight simulation and find the (changed) Roll memory location again.
In CheatEngine re-do a pointer scan by rescaning the memory with the new Roll memory location


Repeat this step several times until you have found a *really* stable pointer to the Roll memory location.
It can be that there still are thousands of stable different pointer combinations.
Just take a simple one.
Hope this helps!