ESABASE2 13.0 Release Notes

These release notes include all features, updates, extensions, and bug fixes
included in ESABASE2 since release 12.1.


ESABASE2 is now started via executable again. The “startEsabase2.bat” script was removed.

Updated Java to version 17 and dependencies

Upgraded EclipseRCP

Upgraded OpenCascade to version 7.5

Windows 11 Support

Optimised mouse handling in geometry editor. Removed buttons for rotation, translation and zoom functions.

Added a view cube in geometry editor.

Improved performance.

Post Processor is available again and is now compatible with Interplanetary mode

Scripting Editor and Batch Processor are compatible with Interplanetary mode now


IMEM and IMEM2 can be used for conventional mode now

They can be used in all planetary orbits


Updated textures of planets in mission editor


Please be aware that the Divine-Staubach model of MASTER 8.0.2 (used by ESABASE2) has a bug and overestimates the fluxes. MASTER 8 executable will need an update after this problem is fixed by the MASTER developer.

Please be aware that the current GUI design is mainly designed for full-HD resolution and a Windows visualization scale of 100%. Lower resolutions/a higher scale can lead to some windows not showing all its contents. E.g. for the frame pointing option window, the “ok” and “cancel” buttons might not be visible. Hence, the setting can not be confirmed and applied. In this case, please try to apply a smaller Windows visualization scaling as a first approach or a higher resolution.

Please consider that MEMR2 relies on Microsoft Visual Studio C++ Redistributables 2008 (32bit). If you have the problem that during the analysis with MEMR2 the Spd… files are not found, please go to “ESABASE2-ROOTFOLDER\Solver\DEBRIS\MEMR2” and double click on “MEMR2CLW.exe”. If you get a message pointing out a problem with “Side-by-Side” installation, then you need to install the MSVC 2008 Redistributables (32bit), e.g. can be found in E2_ROOT\components\install-supplements.

When using the OEM2SPK converter, please make sure no major step size from one step to another occurs, since this exceeds the default threshold for the MAXIMUM_SEP_QUOTIENT parameter of OEM2SPK which is currently used. For more information, refer to

The externally provided OEM2SPK only processes input arguments with a maximum of 80 characters within its setup file. This may lead to problems when trying to use the meta kernel e.g. keep in mind to keep the number of characters lower this threshold to avoid errors during the conversion process.

Please consider that the maximum time span for an S/C trajectory is 100 years, you will not be able to use trajectory kernels including longer mission durations. (This does not apply to the basic kernels provided by the Meta Kernel, but only the trajectory kernel with the trajectory to be analyzed.)

There are inconsistencies with the time representation in the mission file. Each point of the generated trajectory points lists is having an offset of one hour (plus one hour). Manually added trajectory points appear with the exact user-defined date. However, it can be generalized that internal processing works by subtracting one hour from the times of the visualized trajectory list. As a consequence, for manually adding individual trajectory points, one one-hour offset needs to be foreseen.

Bug Fixes

Fixed lighting issues in geometry editor.

Fixed renaming issues when workspace is not available (e.g. if workspace is on network directory).

Fixed memory leaks

Several minor bugs have been fixed.


A new version (1.24) of the Framework User Manual was established.

A new version (1.19) of the ESABASE2/Debris User Manual was established.

A new version (1.12) of the ESABASE2/Debris Technical Description was established.

Known Issues

NetGen is currently not available in ESABASE2 Linux Version.

ORDEM2K is currently not usable under Linux.

An insufficient error message is provided in the case that Weak-Spot visualization is selected for mission results.

Currently, the direct definition of minimum and maximum values in the 2D diagrams are not applied correctly. However, the zoom function can be used to get the desired closer look.

There are inconsistencies with the time representation in the mission file. (See Notes).