| Issue Id |
Release Note |
Category |
| 116994 |
Corrected an issue where adding a Collection of Interval Lists AWB time component to a vehicle's time components graphics settings via the "Graphics TimeComponents" command would cause STK to exit. |
2D Graphics |
| 103569 |
Fixed an issue where, in the Movie Timeline, if you had a time step value change coincident in time with a stored view change, the camera view would oscillate back and forth indefinitely at that point in time. |
3D Graphics |
| 116766 |
Fixed a crash on startup impacting users with hardware limited to OpenGL 3.0 - OpenGL 3.2. |
3D Graphics |
| 116445 |
The consistency of the results computed for several access data providers that need to compute light time delay has been improved by not relying on a previously computed value of light time delay to estimate the delay for a new sample. Instead, the determination of the light time delay value always initializes from a starting point of 0.0. |
Access |
| 117363 |
The FieldOfView access constraint for Sensors has been improved when computing access to large AreaTargets, i.e., those AreaTargets with a boundary point more than 90 deg away in central angle from its centroid. The computation has always used a fast-to-compute coarse check that can determine whether or not it can avoid doing a more intensive computation to determine that no visibility is possible. However, that coarse check's algorithm wasn't correct for large AreaTargets. This coarse check has now been corrected. |
Access |
| 117362 |
An issue was found in the STK Radar jamming feature that affected scenarios that used radar jammers on an aircraft platform. The issue would result in the erroneous evaluation of jamming outside the availability of the aircraft. This issue has been corrected. |
Access |
| 116444 |
The consistency of the results computed for Points, Vector, and Axes based upon an Access object has been improved by not relying on a previously computed value of light time delay to estimate the delay for a new sample. Instead, the determination of the light time delay value always initializes from a starting point of 0.0. |
Analysis Workbench |
| 117638 |
Using the Chains AWB ObjectAccessIntervals would fail to report data if a constellation that had subobjects (sensors, transmitters, receivers, radars) was part of the chain. The naming of the components has been changed to replace '/' characters with '-'. This will change reports and Connect commands as the new names will be used where necessary. |
Analysis Workbench |
| 107348 |
Fixed the segments Position Difference Across Segments, Velocity Difference Across Segments, and Position Velocity Difference Across Segments to difference correctly when they have propagators with different central bodies. |
Astrogator |
| 116434 |
Fixed an issue where the segment occurring after an update segment in an Astrogator MCS would not be written when exporting to a CCSDS Ephemeris file. |
Astrogator |
| 116626 |
Fixed a crash that would happen when an Astrogator update segment was placed before an initial state segment in an MCS. |
Astrogator |
| 116512 |
Some saved SNOPT search profiles were not being disabled in the absence of an SNOPT license. This has been corrected. Please contact AGI Support for a complimentary license to use SNOPT in Astrogator if you require one. |
Astrogator |
| 60747 |
The checks for whether or not a segment has been modified in a given run have been moved to the end of MCS execution rather than to the end of each segment's execution. This corrects the Run Only Changed mode for the MCS to no longer be overridden when using seed finite profiles and scripting tools. |
Astrogator |
| 117147 |
Fixed some User Missile Model and User Rotorcraft Models property display issues on Japanese OS. |
Aviator |
| 113508 |
Fixed a problem where the impact of Coriolis acceleration was causing significant bank angles during pushover maneuvers on no-turn flight paths. Aviator now checks for the computed turn direction, and when that specifies "no turn," Aviator hardwires a zero bank angle for that situation. |
Aviator |
| 113809 |
Added C++ and C# example plugins for Basic Maneuver strategies; please contact Tech Support for guidance on using those projects for your own purpose. |
Aviator |
| 117167 |
Loading chains with invalid objects was causing STK to crash when the chain was computed. This has been corrected. |
Chains |
| 116858 |
The Comm Tropo-scintillation model has been updated to improve computations at very low angles. |
Communications |
| 116145 |
An issue was found in the Scenario Explorer workflow of the Scalable Networks Modeling Interface that would cause the EXata or QualNet configuration file to be written incorrectly if a node had both wireless and wired interfaces. This would lead to the EXata or QualNet simulator to crash at run time. This issue has been fixed for the latest release of the Scenario Explorer, and the configuration file is now written correctly. |
Communications |
| 116237 |
Fixed an issue where enabling Object Graphics resulted in an UrbanTerrestial loss of 3000 db. |
Communications |
| 116305 |
An issue has been corrected where an antenna model uses a .uan data file. This issue had led to STK crashing if STK did not find the .uan antenna file on scenario load. |
Communications |
| 117857 |
An issue was found in the Scalable Networks Modeling Interface configuration file workflow when loading configuration files which set the MAC-PROTOCOL configuration value at the interface level instead of the subnet level. Configuration files written in this manner would not properly load into the configuration importer and would show all network interfaces, both wireless and wired, which is incorrect. This has been corrected. |
Communications |
| 116030 |
The AddWayPoint Connect command will now obtain the terrain height from the vehicle's central body terrain sources rather than the scenario's central body terrain sources when adding the waypoint is using the "Terrain" value for altitude. Previously, if the scenario central body was Moon and the vehicle's central body was Earth, the terrain height was obtained from the lunar terrain sources, not the Earth's sources. |
Connect |
| 116538 |
The SetEpoch Connect command has been updated to NACK if you attempt to set the epoch to a TimeComponent but that TimeComponent doesn't exist or cannot be computed. Previously, the command would ACK but do nothing. |
Connect |
| 117586 |
The Collection Subset Connect command has been corrected so that a specified SqliteWhereClause, which uses a column name with a space in it, will be parsed correctly. Column names containing spaces should be enclosed with double quotes, e.g., "column name". |
Connect |
| 116702 |
The output strings from the Connect command Units_Get could not be used as inputs to the Connect commands Units_Set for the Aviator dimensions AviatorDistance, AviatorG, AviatorTSFC, and AviatorPSFC. This has been corrected. |
Connect |
| 116153 |
The Coverage GridLocation data provider has been updated to ensure that the each grid point's altitude above terrain is correctly reported when both local terrain is enabled and the terrain server is used for analysis. Previously, if both sources of terrain were enabled, then the grid point altitudes would be constructed using the terrain server values, but would be reported using the local terrain values. |
Coverage |
| 116156 |
The ground model used by the grid point of a Coverage computation, when the scenario has been set to use the terrain server for analysis, now honors the settings in the Coverage's grid point options. Previously, the ground model was always set to be the ellipsoid. |
Coverage |
| 117127 |
Area Target objects previously could not be selected as Single_Object Coverage assets. This has been corrected. |
Coverage |
| 116938 |
Documentation has been updated to include the Satellite Collection Graphics Connect commands. |
Documentation |
| 117214 |
The documentation for the Pattern_Angle_Extremals_Intersection data provider has been improved to better describe the reference plane for the extremal angle. |
Documentation |
| 115765 |
When generating an EOIR Sensor-to-Target Metrics report, a conflict occurred if the RenderBand in the sensor properties was different from the band selected as PreData. This has been corrected. |
EOIR |
| 117561 |
Enabling motion blur for an EOIR sensor that is targeting an object caused a white line to appear through the center of the screen. This has been corrected. |
EOIR |
| 117893 |
There was an issue with high polygon count custom mesh models emitting too much radiation. This has been corrected. |
EOIR |
| 116952 |
The Supplemental metadata file used in SatelliteCollection has been fixed so that it supports the creation of subsets for any CustomColumn where value of CreateSubsets has been set to Yes. |
General |
| 116479 |
If a scenario that utilizes the TimeSlipRange constraint is loaded, in the event the user does not have an Ansys STK Premium Space license, the Unlicensed Capabilities dialog box will now show that this license is required. |
General |
| 116620 |
When adding or editing Two Line Element sets for satellites using the SGP4 propagator, the BStar UI value limits have been expanded to +- 0.99999x10^9. |
General |
| 117558 |
The Walker Tool would crash STK if another window was open. This has been corrected. |
General |
| 116950 |
An error in the assignment of supplemental metadata to a Satellite Collection using the Database definition method has been corrected. The error prevented supplemental metadata from being properly removed or updated once assigned. |
General |
| 115877 |
VectorData files that specify data in the Fixed frame now also interpolate in the Fixed frame. Previously, the data was converted to the inertial frame before interpolating. This improved behavior is now consistent with interpolation behavior when using *.e ephemeris files. |
General Astro |
| 116590 |
Eclipse computations have been improved by improving the sampling to better detect eclipses. Previously, an eclipse might be missed if an object's orbital period changed substantially soon after its start time. |
General Astro |
| 116693 |
The Collection Subset Connect command has been updated to no longer support the AutoGeneration setting. Autogeneration of Subsets can still be controlled through the Walker settings or the registration of CustomColumns for orbit definition or supplemental metadata files. |
General Astro |
| 116789 |
The computation of curvilinear coordinates rates has been improved when the reference ellipse is determined to have no eccentricity. Previously, the rates computed at zero eccentricity would jump as soon as the eccentricity reached a magnitude of 1.0e-12. |
General Astro |
| 116891 |
The N Plate SRP and Drag models now correctly load from a propagator definition file. |
General Astro |
| 116991 |
The processing of the CreateSubsets keyword for Boolean, Epoch, and Integer data types in a Orbit Definition file for SatelliteCollection objects has been fixed. You can now create subsets by a column with datatype Boolean or Epoch or Integer, as documented. |
General Astro |
| 117047 |
The User Interface panel for creating a new Satellite object from the Insert STK Objects Tool -> From SP3 File has been fixed to show the correct association between PRN number in the SP3 file with the SSC Number of the actual satellite broadcasting that PRN. The GPSData.txt file contains these associations. Because these associations do change over time, you can update the GPSData.txt file using the Data Update Utility. |
General Astro |
| 117051 |
The MinValue and MaxValue columns defined in a SatelliteCollection orbit definition or supplemental data file now correctly check their content against the specified limit. Previously, these rows with values outside the specified limits would still be loaded into the collection. |
General Astro |
| 117617 |
The targeted attitude of a vehicle or subobject used as a Reference Object in a SatelliteCollection now updates correctly as each entry is being used in a computational tool. |
General Astro |
| 117923 |
The Realtime Propagator's Look Ahead duration was being ignored when the Look Ahead propagator was set to Ballistic for Missiles and Launch Vehicles. This has been corrected. |
General Astro |
| 116343 |
Fixed a problem with the VO ModelOffset Translational Connect command for Facilities that caused the model to move in the wrong direction. |
General Graphics |
| 117699 |
Fixed an issue with the Object Browser that would cause ghosted items to appear when certain objects and states occurred. |
General Graphics |
| 112414 |
Using Coverage grid points very close to one of the poles resulted in block contour graphics that wrap around the pole. This has been fixed by reducing the tolerance used to determine if a grid point is located exactly at the pole. For saved scenarios showing this problem, you will need to force a recompute of the Coverage grid since the grid is stored with the Coverage object. This is easily done by modifying the grid resolution slightly. |
General Graphics |
| 118080 |
Fixed a crash in Globe Manager when using drag and drop to move items. |
Globe Manager |
| 117097 |
The HTML Utilities have been updated to be compatible with the new Web Browser feature. They are no longer compatible with the HTML Viewer. |
HTML Page |
| 116269 |
The Object Model SetGridValuesFixedNumberOfSteps method for an AWB volumetric Cartographic grid uses only distance units when the angle dimension unit should be used. Using this method to set values therefore does not work as expected. |
Object Model |
| 106746 |
The IAgSnSARPattern:TrackParentAltitude property has been added to the STK Object Model for SAR sensors. |
Object Model |
| 117620 |
A possible exception creating code pathway when attempting to get a segment from a segment collection has been protected against. |
Object Model |
| 116668 |
Updated the version number for Windows desktop runtime to 5.0.13 in the release note for 2.4 and in the system requirements page. |
Parallel Computing |
| 110230 |
The QualNet interface experiment folder, when packaged into the VDF, became extremely large on successive executions. This has been corrected. |
Plugins |
| 113454 |
HFSS-created RCS data may be exported in two CSV format files. STK will try to match the frequency and the RCS data Theta & Phi angle(s) extents and the angle step values between the two files. An error message is displayed if the frequency and angles data is not consistent between the two files. |
Radar |
| 118089 |
You can produce two files for Ansys HFSS target RCS data for a full scattering Matrix Complex RCS. Each of the files contain two complex elements of the 2 X 2 scattering matrix. For more information, see the help. |
Radar |
| 116362 |
EOIR Sensor-to-Target Metrics data provider is now able to use time components for reporting and graphing. |
Reports and Graphs |
| 114961 |
Corrected the Ephemeris Diff in Curvilinear Coordinates satellite data provider such that it will correctly initialize on the load of a scenario when it is being used in a dynamic display. |
Reports and Graphs |
| 115143 |
Added validation to Report/Graph style names to prevent invalid names from being created. |
Reports and Graphs |
| 117059 |
An issue was found with the CommSystem which would cause GUI prompts to appear when loading scenarios with quick reports that are generated on load. This issue has been corrected and CommSystem quick reports now load properly without GUI prompts. |
Reports and Graphs |
| 116469 |
Parallel Coverage has been updated so that it no longer displays a message in the Message Viewer warning about a mismatch in the grid point altitude when the grid point has been set to use the terrain's altitude at its location. The message was false and did not indicate any Coverage computational problem. |
Terrain and Imagery |
| 114183 |
Double-clicking on a terrain or imagery file in the "Open Terrain and Imagery Data" selection dialog from Globe Manager now loads the selected image or terrain file. |
Terrain and Imagery |
| 117026 |
Discovered that there were gaps in terrain when rendering the streaming visual terrain in the 3D Graphics window. This has been corrected. |
Terrain and Imagery |
| 116382 |
The ZoomTo option for a City or Facility found using the search toolbar now correctly zooms to the object's location. Previously, the latitude would be correct, but the longitude would be wrong or cause STK to hang. |
User Interface |
| 116557 |
The SPICE segments for a body selected on the SPICE propagator panel are now sorted in time order rather than displaying in the order of the segments as they appear in the SPICE BSP file. Use the slider on the panel to scroll through the segments. |
User Interface |
| 112168 |
STK would exit when deleting an object with dependent AWB components if the Object Browser is unpinned. This has been corrected. |
User Interface |
| 116923 |
Fixed Full Screen mode to maximize the client window and hide the window tabs. |
User Interface |
| 117058 |
Fixed Astrogator so that it displays Cut, Copy, Paste, Delete, and Add To Components Browser buttons when viewing segment results in an Astrogator target sequence. |
User Interface |
| 116999 |
The SpatialTool Connect command, when used to modify a VolumeGrid by adding Custom points, is now fixed. Previously, if the Custom Replace was used to set only one (1) point and then a subsequent call to Add points was made, a crash occurred. Using Replace with two (2) or more points avoided the problem. |
Volumetric |