| Issue Id |
Release Note |
Category |
| 114222 |
Fixed a memory leak when loading image textures through Object Model |
3D Graphics |
| 114371 |
Once a 3D PolylinePrimitive was set to use TimeIntervals, there was no way to remove the intervals. The intervals can now be cleared from the primitive by calling the Set method on the PolylinePrimitive without specifying any TimeIntervals. |
3D Graphics |
| 114504 |
The DeckAccess Tool has been corrected to no longer cause a crash when adding satellites to the scenario as part of the DeckAccess computation. |
Access |
| 114661 |
Updated file loading of Fluent Aero's AERO files to ensure the data loaded is in the necessary sort order to build the underlying interpolation data structures. Output warnings have also been added when there may be an issue with EOL characters as can happen when data is generated on Linux and loaded on Windows (or vice versa). |
Aviator |
| 115166 |
Added an element of Total Lift Force called Unaccounted Lift. Unaccounted Lift = Total Lift - (Aero Lift + Lift due to Thrust). Unaccounted Lift will be non-zero when the aerodynamic forces available to the aircraft are not sufficient to generate the defined maneuver. When Unaccounted Lift is non-zero, the aero data providers indicate an invalid state. |
Aviator |
| 114073 |
The JupyterNotebook.dll, installed with the Jupyter Notebook plugin, was not properly digitally signed. This has been corrected. |
Build Process |
| 112294 |
The Scalable Networks Modeling Interface has been updated to correct a problem which caused the SuperApplication of the Scenario Explorer work flow to be incorrectly written to the experiment application file. |
Communications |
| 114433 |
An issue was found in STK 12.2 when linking Communication and Radar Objects (Transmitter, Receiver, Radar, and Antenna) to components in the Component Manager. When making changes to the linked component, the Communication and Radar object would not notify the system that they had changed causing dependent computations to not reflect the current state of the object. This issue has been corrected. |
Communications |
| 114237 |
Coverage legends may position labels incorrectly in the 3D window. This has been corrected. |
Coverage |
| 114132 |
An issue where Astrogator propagators using a two-body central gravity field along with the STM function were producing incorrect STM results has been corrected. |
General Astro |
| 114184 |
The frame kernel (FK) file needed by the ceres.bsp spice ephemeris file has been added so that STK can correctly use the spice file to model the orbit of Ceres. |
General Astro |
| 114383 |
Computing sensor projections for graphics or for reporting caused memory to be leaked. This has been corrected. |
General Astro |
| 114918 |
The Launch Window Analysis Tool's stop time now loads correctly. Previously, the start time would load correctly but the stop time would be incorrect (off by the ephemeris span of the launch vehicle). |
General Astro |
| 114966 |
Documented how the Ansys licensing works and how the licensingclient\winx64 directory and the Shared Files directories are installed. |
Install |
| 114410 |
When using the Jupyter Notebook plugin, if the Jupyter server fails to start and the server is attempted to be restarted, an erroneous error message may be displayed. This has been corrected. |
Plugins |
| 114800 |
The Launch Window Analysis Tool has been corrected to consider the ephemeris span of each secondary when computing conjunctions and blackout intervals, when the secondary is defined by an ephemeris file. Secondaries defined using GP data like TLEs were (and continue to be) defined with the correct ephemeris span to do the full assessment. Previously, the computation would treat the secondary defined by an ephemeris file as being stationary at its first location for times before its ephemeris start time, and stationary at its last location for times requested after its ephemeris stop time, which is a poor model of the secondary motion. Now the assessment of such a secondary is only performed over its available ephemeris times. Moreover, the assessment interval for secondaries (i.e., the time interval over which they should have ephemeris to be able to full assess the entire launch window over the considered part of the launch trajectory) is now reported in the Launch Window Definition data provider. |
Reports and Graphs |
| 115032 |
Fixed crash that occurs when multiple Volumetric objects were computed and drawn. |
Volumetric |