| Issue Id | Release Note | Category |
|---|---|---|
| 100391 | Improved font sizing on high resolution displays (4k, 8K, etc.). When loading scenarios that were created in older version of STK. Font sizing may be slightly different when viewed in old versions of STK. | 3D Graphics |
| 105834 | Using terrain in a scene being displayed in an Occulus Rift device can cause the view to jitter. | 3D Graphics |
| 106602 | Fixed an issue that prevented special character text (e.g.. the degree symbol) from displaying properly in the 3D window. | 3D Graphics |
| 108896 | Models that are shared across several STK Objects had been forced to share Image Based Lighting reflection environments. This has been fixed. | 3D Graphics |
| 109364 | When the Data Display Area is enabled, the 3D Window's primary scene would produce noticeable visual artifacts. This has been fixed. Volumetric graphics were incorrectly clipped if Antialiasing settings 2x2, 3x3, or 4x4 were enabled. This has been fixed. | 3D Graphics |
| 106720 | Accesses created from certain connect commands (ReportCreate, Report_RM, GraphCreate, DynamicRpt, Report, GetReport, GetRptSummary, Graph, Access, AER) now correctly set the considered time intervals when a time interval is provided by the command and the first object is a Planet or Receiver or the second object is a Transmitter. The problem is only evidenced in cases where the light time delay itself is long (e.g., greater than one (1) sec). | Access |
| 107360 | Summary statistics have been added to many of the data provider elements in the DeckAccess data provider. | Access |
| 107796 | Access processing has been improved to only recompute once when it is notified by a dependent object that it has updated and needs the Access to recompute itself. Previously, Access may have been recomputed several times. | Access |
| 107911 | The Line-Of-Sight constraint for transmitters or receivers on vehicles that use a linked antenna has been improved when computing access to ground objects (Facilities, Targets, Places). These cases no longer compute the Line-Of-Sight constraint from both objects, as one computation suffices. | Access |
| 107955 | The LineOfSight and CbObstruction constraints for ground objects (Facility, Place, Targets) and vehicles now apply to LineTargets. If both a LineTarget and another object have the LineOfSight constraint on, then the LineTarget's version is used and the other is ignored. If the LineTarget's line-of-sight constraint is off but a ground object or vehicle has LineOfSight on, then its version of line-of-sight will be used. | Access |
| 107956 | The special Sensor constraint AtFieldOfView, applicable only to AreaTargets, has been merged with the normal FieldOfView constraint---it will no longer be reported as AtFieldOfView. | Access |
| 108049 | The Access Tool and Object Model for Access no longer restricts the compute time of the computation by the scenario interval when a specified time interval (or time component) is specified and the objects involved in the access have considered to be always available (e.g., Facilities, Places, Targets, and Planets). | Access |
| 108078 | When an Access uses a TimeIntervalList to set its computation intervals that is subsequently deleted, the then-current intervals of the component will be preserved and used as the computation intervals for the Access. A new TimeIntervalList component owned by the Access itself will be automatically created, holding these specified values, and set for use as the Access's computation intervals. | Access |
| 108103 | The loading of accesses during scenario load has been fixed so that if an access was computed over a specified interval, where the start time was before the scenario start time, the specified interval will be honored when the access is computed. Previously object times would have been used. | Access |
| 108104 | An Access Object now correctly loads AWB Time Components that it owns during scenario load. Previously, these components could not be found during load. | Access |
| 109949 | The IAgStkAccess interface now respects the clock host and signal sense of an existing Access object when it was obtained. Previously, it would reset the clock host and signal sense to the default values used for the classes of the objects used in the access, unless overridden using the IAgStkAccessAdvanced interface to set UseDefaultClockHostandSignalSense to false. | Access |
| 110054 | The access stop time has been updated to consider the full input intervals when using a MinMax constraint with both Min and Max enabled. Previously, the access stop time may have been computed slightly short of the actual input stop time, by 0.1 secs or less, if the constraint was satisfied at that time. | Access |
| 106320 | Fixed the AWB point on central body to correctly compute the terrain intersection point when using the terrain server when available. | Analysis Workbench |
| 106322 | The description of the VGT Point 'CentralBody Grazing' has been updated to more accurately reflect its actual computation. The previous description (on the UI and in Help) did not comport with the actual computed value. We expect to provide a VGT Point in a later release whose computation will reflect the older description (i.e., the closest point on a central body surface to the ray defined by the starting point and the reference direction). | Analysis Workbench |
| 108945 | The IAgCrdnEventIntervalCollectionOccurredResult interface's IsValid property (available from an IAgCrdnEventIntervalCollection's Occurred() method) has been fixed to properly return True when the specified time of the Occurrence method lies within an interval of the event interval collection and False otherwise. Previously, the method returned True almost always whether the time occurred within the event interval list or not. Similarly, the IAgCrdnEventFindOccurrenceResult interface (available from an IAgCrdnEvent's FindOccurrence() method) has been fixed to properly return True when the event time is known and False otherwise. Previously, the method may have returned True although the event time was not computed. | Analysis Workbench |
| 109511 | The default values for the Displacement Vector in AWB have been updated, to help simplify the workflows that seek to measure where a second object is located relative to the owner of the displacement vector being created. | Analysis Workbench |
| 109782 | The orientation of the EclipticICRF axes in Vector Geometry Tool has been corrected. | Analysis Workbench |
| 103444 | An issue where Astrogator Connect GetValue calls would return values with user-specified units with the correct value but incorrect units has been corrected. | Astrogator |
| 107493 | Astrogator maneuver data reporting and ephemeris handling mechanisms have been improved for the object model AppendRunFromTime method. | Astrogator |
| 107603 | Running an Astrogator MCS segment with badly-formatted throttle tables would cause STK to crash. This has been fixed. | Astrogator |
| 108892 | Attitude data produced specifically using the Astrogator propagator is now deleted when the Satellite's propagator is switched to be something other than Astrogator. Previously, this attitude information was preserved but not editable. | Astrogator |
| 108971 | Invalid coordinate system choices are better detected when selecting the coordinate system for the initial state in Astrogator. Now a system that depends on a Time Component that itself depends on the satellite will not be allowed to be selected, as the definition depends on the satellite being propagated. | Astrogator |
| 109096 | Some intermittent issues causing Astrogator satellites to not load, resulting in an Unknown propagator type for the satellite, have been addressed. | Astrogator |
| 109827 | The propagator component UI panel has been extended to restore access to a setting inadvertently made inaccessible through the UI with changes for STK 11.7. | Astrogator |
| 97781 | The use of a vehicle lighting constraint on a satellite being propagated by Astrogator where an Access stopping condition is being used now correctly works the first time the propagation is attempted; previously, the lighting constraint would not compute any access times on the first propagation but would work correctly thereafter. | Astrogator |
| 106454 | Fixed the computation for Earth frame mode of the Basic maneuver Simple Turn strategy so it holds the turn radius that would result for a no wind condition. | Aviator |
| 107803 | Fixed a problem where an invalid aero file can lead to the Aero UI not fully initializing and getting into a state where clicks on the uninitialized GUI crash STK. | Aviator |
| 107984 | Corrected an issue where the Time/Fuel Ruler and Flight Range Area Targets plugin tools were not working. A new software pattern was introduced to facilitate the new Aviator Automation feature due to release in STK 12, and the UiPlugin tools for Aviator in STK 11.7 were not configured to work with the new pattern. | Aviator |
| 108004 | Updated Advanced Fixed Wing performance models to handle the situation when the aircraft can generate a positive Ps at high altitude, but not at low altitudes. Prior versions would tell the user the ceiling was Sea Level and wouldn't let the user define procedures at the desired altitudes. | Aviator |
| 108269 | Chains was no longer marking links with excessive light time delays as invalid. This has been corrected. | Chains |
| 108719 | The following releases of the ITU-R propagation models have been deprecated in STK v12. Older scenarios saved with deprecated releases will load with the default version of the latest release of the model. The models were superseded more than ten years ago. The models are:
Atmospheric models:
Rain Models:
Cloud and Fog:
|
Communications |
| 108970 | The maximum slew acceleration components for a Targeted Slew in Vehicles are now interpreted as being the body components of the inertial angular acceleration, and not the inertial components of the inertial angular acceleration, to be consistent with the use of body components in the maximum slew angular velocity components. | Communications |
| 109020 | Phased Array GUI graphics, while populating the array elements on the GUI panel, may miss a few elements on a diagonal for regular or rectangular polygons. Missing elements could still be inserted manually by clicking on the grid point. This issue has been fixed. | Communications |
| 109249 | Added a minimum limit one (1) meter on the cloud thickness. Using a value of zero cloud thickness is not reasonable. Added an option to use Rain Height as the cloud thickness (as in the case of Fog, it is from ground to the cloud ceiling altitude). Rain and cloud & Fog models may be checked (enabled) together. Removed mutual exclusivity. For example, rain clouds may have another layer of clouds above the rain. e.g. Rain cloud altitude is four (4) km and there may be another cloud layer from five (5) km to seven (7) km. User may choose to model both rain and cloud & Fog loss. | Communications |
| 109250 | Aperture antenna gain pattern computation algorithms have been updated. The results improve the patterns to be closer to the theoretical computations. | Communications |
| 109537 | Corrected an issue with the gain of a linear phase array antenna and planar array when not using element factor. | Communications |
| 107574 | The SetState SGP4 connect command now correctly processes TLE files for SSC numbers that are not in AGI's satellite database file (i.e., *.sd file). | Connect |
| 108058 | The AER connect command has been updated to remember the time settings specified by the command in the Access object, just like the Access command currently does. | Connect |
| 108061 | The Access connect command has been updated so that if a time period is specified and no access intervals are found, the input time period that was specified on the command will still be set as the compute time for the access--it no longer resets back to object times just because no access intervals were found. | Connect |
| 108065 | The Access and AER connect commands no longer deletes the existing access and re-creates it as part of its computational processing, thus AWB components owned by the access or AWB components built upon those owned by the access are no longer deleted as a consequence of using these commands. | Connect |
| 108933 | A new LoadColorIntervals option as been added to the VO SetVectorGeometry Connect command | Connect |
| 109145 | Fixed error adding a custom time varying sensor. | Connect |
| 110088 | The InitialState Import connect command caused the socket to hang when the GatorPath option was used. This has been corrected. | Connect |
| 108125 | An error in the computation of the longitude span of coverage grid points in the near polar region when using the LatLon Region grid type has been corrected. The errant longitude span values resulted in incorrect graphical representations in the 2D and 3D displays when using filled points. The coverage access times and figure of merit values were not affected by this error. | Coverage |
| 109890 | An error in the computation of the Dilution of Precision Figure of Merit in scenarios where the coverage grid point was associated with one central body and the coverage assets were referenced to a different central body has been corrected. | Coverage |
| 107328 | Corrected reporting of external data when the data file contains only one point. | Data |
| 110044 | The default save method for certain double-precision values, such as articulation values, was changed in STK 11.7. A maximum number of six (6) significant digits would be saved, causing loss of precision. This has been corrected to save these values with precision at least as good, if not better, than versions of STK prior to 11.7. | General |