Project TrajectoryOptimizerMFD open for testing

Hi all,

I've attached here a public beta of TrajectoryOptimizer, an MFD that searches for
interplanetary transfer trajectories — departure/arrival dates and the ΔV to
fly them — using Orbiter's own ephemerides. It's a planning tool: it finds the
trajectory, you fly it.

This is a major new version. Highlights:

- Faster, and far more consistent — the same plan returns the same quality
result run to run.
- Any body with at least two orbiting children can be the reference body, so
Sun-centred interplanetary transfers AND moon-to-moon transfers around a
planet both work.
- No more BSP files — body positions come straight from Orbiter's own models.
Nothing to generate, nothing to install.
- Custom solar systems supported out of the box — custom stars, fictional
systems, any scale, zero configuration.
  • Export a solved plan straight to TransX or InterplanetaryMFD.
  • Deep-space maneuvers (DSMs) supported, for Cassini-style gravity-assist tours.
  • Press H on any page for context-sensitive help.
  • A work-in-progress manual is included in the download.

Install: unzip into your Orbiter root folder, tick TrajectoryOptimizer in
Launchpad → Modules, then bring up any MFD, press SEL, and choose TrajectoryOptimizer from the list.

Please test and report back here. I'd especially like to hear:

  • Any impact on Orbiter's frame rate?
  • Any unexpected behaviour?
  • Suggestions, comments, or bugs?

Thanks in advance for trying it and for your feedback.

EDIT: zip file reuploaded to fix a dependency issue reported by @Buck Rogers
 

Attachments

Last edited:
This looks seriously impressive!:)

Quick lunchbreak test, O16/24, Win10, default DG

The Doc looks good, sounds like you've tried to cover any possible loopholes/loose ends- very comprehensive.(y)
Installation ok...
BUT I'm not getting past the start!

"Open any MFD, press SHIFT and the MFD's select key, then press T." - This is a little ambiguous?

If I start the MFD I get a CTD, log attached.
If I open the left MFD, press SEL, and left-shift hold + "T" it opens the DG atmo autopilot?
Holding the left-shift and the MFD's select key just cycles through SEL options?

Edit: Tried the above with 2 other vessels, no luck.

Not sure where the error is?

Module TrajectoryOptimizer.dll [Build 260723, API 160828]
TrajectoryOptimizer: version 2.5.0-beta1 (built Jul 23 2026), MFD mode registered on key T.
============================ ERROR: ===========================
Failed loading module Modules\Plugin\TrajectoryOptimizer.dll (code 1114)
 

Attachments

Last edited:
This looks seriously impressive!:)

Quick lunchbreak test, O16/24, Win10, default DG

The Doc looks good, sounds like you've tried to cover any possible loopholes/loose ends- very comprehensive.(y)
Installation ok...
BUT I'm not getting past the start!

"Open any MFD, press SHIFT and the MFD's select key, then press T." - This is a little ambiguous?

If I start the MFD I get a CTD, log attached.
If I open the left MFD, press SEL, and left-shift hold + "T" it opens the DG atmo autopilot?
Holding the left-shift and the MFD's select key just cycles through SEL options?

Edit: Tried the above with 2 other vessels, no luck.

Not sure where the error is?

Module TrajectoryOptimizer.dll [Build 260723, API 160828]
TrajectoryOptimizer: version 2.5.0-beta1 (built Jul 23 2026), MFD mode registered on key T.
============================ ERROR: ===========================
Failed loading module Modules\Plugin\TrajectoryOptimizer.dll (code 1114)
@Buck Rogers — thank you, genuinely.

That log line was the entire diagnosis, and without your lunch-break test this would have gone straight out to everyone unnoticed.
Exactly what a beta is for. 🙏

What went wrong: the plugin is built with Visual Studio 2022 and was relying on the machine already having the Microsoft Visual C++ 2015–2022 (x86) runtime.
Yours didn't have a matching one, so Windows aborted the load before the MFD could start — that's the "code 1114" (DLL initialization failed) in your log.
Nothing wrong with your install; my packaging left a dependency out. (And with the module half-loaded, the "T" key fell through to the DeltaGlider — hence the atmo autopilot.)

Two ways forward:
• Right now: You can unzip the attached file directly into your Orbiter root folder (where orbiter.exe lives)

• Properly: I'm bundling the runtime into the download so there's nothing to install at all. The zip file in post #22 has been updated.

Also, my start-up instruction was clumsy — sorry. The simple version: once it loads, bring up any MFD, press SEL, and choose TrajectoryOptimizer from the list.

Thanks again — first report in and it's already made the release better.
:hailprobe:
 

Attachments

I'd like to try this MFD, but I don't have much experience in interplanetary flights yet (although I'm familiar with Orbiter since the 2006 version). I only know how to fly from Eeath to Moon and back, and it seems like I once flew to Mars. So I'm not sure I can understand how to use this MFD for various flighs. Is the documentation attached with the MFD enough to understand it? Like checklists/examples (I seen the only one - from Earth to Mars). Could you write in the future more basic examples of using this MFD (after release) for flying: Earth <-> Venus, Earth <-> Mars, Venus <->Saturn, Jupiter <-> Europa, etc?
(And with the module half-loaded, the "T" key fell through to the DeltaGlider — hence the atmo autopilot.)
Sorry for my off-topic, but what is the "DG atmo autopilot"? How to use it? I didn't know DG has the default autopilt that can be controled with key buttons.

By the way, does anyone know any autopilot add-ons (MFD) with pitch hold function (using control surfaces)? So you can set, for example, pitch 30 degrees and a vessel holds it. And it allows setting various angles during the flight. And it can use RCS thrusters for flying in the upper layers of the atmosphere.
 
Sorry for my off-topic, but what is the "DG atmo autopilot"? How to use it? I didn't know DG has the default autopilt that can be controled with key buttons.
Is it the "Lua MFD" that is displayed as the "Termainal MFD" (I'm familiar with this)?:

1784914147336.png
 
That log line was the entire diagnosis, and without your lunch-break test this would have gone straight out to everyone unnoticed.
Exactly what a beta is for. 🙏

What went wrong: the plugin is built with Visual Studio 2022 and was relying on the machine already having the Microsoft Visual C++ 2015–2022 (x86) runtime.
Yours didn't have a matching one, so Windows aborted the load before the MFD could start — that's the "code 1114" (DLL initialization failed) in your log.
Nothing wrong with your install; my packaging left a dependency out. (And with the module half-loaded, the "T" key fell through to the DeltaGlider — hence the atmo autopilot.)
Good news! Wasn't sure if I was just "being stupid" (generally No1 on the options list;)).
What had me a bit stumped was that the MFD was registered and listed under SEL, haven't seen a half-loaded module before!o_O
Glad to be of help.:)
Will test/confirm that it's working and Earh-Mars, would love to give it a thorough run through but it might be a while before I have time...
By the way, does anyone know any autopilot add-ons (MFD) with pitch hold function (using control surfaces)? So you can set, for example, pitch 30 degrees and a vessel holds it. And it allows setting various angles during the flight. And it can use RCS thrusters for flying in the upper layers of the atmosphere.
Check Orbiter2024/Config/MFD/Attitude.cfg, a lua autopilot that can be activated, might be useful? Otherwise I don't know of a universal AP that does all that.🤷‍♂️
 
Sorry.:( Still getting the same error message! (did also de-activate before re-installing).
Note: Orb24 ships with these files pre-installed (different sizes).
I don't think they are being blocked?

@misha.physics Can you confirm it runs your end? Might be isolated (my system).

P.S. the older version ran fine.🤷‍♂️
 
Last edited:
Hi @dgatsoulis
many thanks for this!
Had a quick test and the MFD works fine for me even without the additional MSVCP140.dll VCRUNTIME140.dll.
I ran the Earth-Mars initial screen and it gave me a selection of solutions :)
Using default Orbiter2016 and also with D3D9 GC 4.26.
Windows8.1 with Visual Studio2010 Express compiler installed, ancient PC with Intel chip.

:cheers:
 
@misha.physics Can you confirm it runs your end? Might be isolated (my system).
It runs on my laptop with Orbiter 2024 and Windows 10 (but I haven't experimented further yet (other functions)):

1784923424341.png

Also, I didn't copy those two DLL files, since they're already presented in my Orbiter directory.
 
Back
Top