The following table lists the technical issues known to exist in the Ansys Systems Tool Kit® (STK®) application.
| Issue Id | Release Note |
|---|---|
| AIR-368 | Aviator Connect commands do not work with many new phase and procedure options. |
| ANLY-109 | Figures of Merit that use a Comm interference access constraint generate slightly incorrect numbers by default because of light time delay modeling differences. The CoverageDefinition object controls the light time delay settings, but these settings are not employed by the interference constraints. Instead, the interference constraints rely on the Access Defaults settings in Edit > Preferences. By default, Coverage will compute with light time delay off, but the Access Defaults are set to have light time delay on, resulting in a slight mismatch in the signal modeling. |
| ANLY-252 | The Strip Chart Customization dialog box interferes with setting strip chart duration and Y limits. This results in STK software not retaining the set colors. |
| ANLY-265 | The Report and Graph Manager enables you to place a report style in a subdirectory of either MyStyles or the scenario folder, but you cannot select these report styles for use by 3D Data Displays. |
| ANLY-268 | If you export a graph file to a directory that has a name containing a period (.), the file extension will not be included when the file is saved. You can avoid this problem by either choosing a different directory to save to or by appending the file extension after the file is saved, using the Windows file browser. |
| ANLY-456 | Sensors located on Facility or Target objects and using the Fixed In Axes pointing method include an additional 180 degree offset about the Y axis of the reference axes. This behavior was designed to be consistent with that of the legacy "Fixed" pointing method. |
| ANLY-465 | Access computations involving area targets with highly irregular edges and a 90-degree elevation constraint can result in errors due to inadequate sampling. You can fix this by manually changing the maximum step size allowed during access computations. |
| ANLY-472 | In STK Engine, you cannot export Comm contours to a shapefile when employing the NoGraphics option. |
| ANLY-474 | Angle and Vector Magnitude constraints are not turned off during targeting, even if they are attitude dependent. This may interfere with producing a correct schedule for targeting. |
| ANLY-521 | You should use the sensor pointing option "Grazing Alt" if the sensor is on an object with a nadir-aligned Z axis attitude, as it assumed an azimuth constraint and solved for elevation. During a period when the grazing altitude cannot be found along the azimuth vector, the sensor pointing will revert to the default fixed pointing and will not be displayed. See the Grazing Altitude Sensor Pointing help page for further information and a graphical representation. |
| ANLY-698 | Using Data Element Calc Scalars or components dependent on such Calc Scalars can cause circular dependencies when used in computing vehicle attitude. This can lead to attitude not being computed correctly. The attitude can usually be corrected by reapplying the attitude settings. |
| ANLY-724 | For custom grids with a single small area, less than a degree in size, STK software may not be able to generate grid points. |
| ANLY-754 | For a Coverage Definition object, if you select an object as a grid instance that has an Attitude Coverage object as a child, the STK application might terminate. |
| ANLY-815 | The animation interval time components do not display name changes in the timeline when the scenario is renamed. |
| ANLY-844 | A Chain that involves objects at great distances, such as interplanetary, may produce incorrect answers. |
| ANLY-845 | When two or more Aviator aircraft make use of the same or related time components, and those aircraft also depend on each other in some way, they will not always recalculate in the correct order when the time component changes. You should manually recalculate those aircraft in the proper order. |
| ANLY-853 | Filled volumes and surfaces for small Cartographic and Surface Bearing grids (from several tens to hundreds of feet in size) may appear shifted and jittery to single precision computations performed on GPUs. |
| ANLZR-991 | The Lifetime message gives a duration of days if less than one year but years if greater than one year. In Analyzer, the Lifetime folder exposes the value as number of days. This unit change leads to incorrect graphing. |
| ANLZR-997 | The STK Plugin for Analyzer cannot adjust the step size for time-dynamic data providers. Data is provided in fixed step size (60 seconds) only, so ModelCenter users can only get the aliasing data. This means it is difficult to get the significant peak value through the STK Plugin. |
| ANLZR-1001 | Analyzer is setting the data format incorrectly when using the Astrogator Scripting tool. This is only a problem for string-based formats. To work around this, change the date format to any continuous format (EpSec, EpHr, etc.). |
| ANLZR-1018 | The Optimization tool may change Analyzer resolution on a 4K monitor. |
| COMMRAD-201 | An antenna's valid X/Y dimension limits are not consistent with the X/Y beamwidth limits. You should switch to "Use Dimensions" to reach full limits. |
| COMMRAD-205 |
Polarization loss is not accounting for the direction of propagation at the receiver. If the signal is arriving from the direction opposite the boresight direction (the backlobe direction), then the result is not correct. This means that the direction of signal arrival is in the -Z direction in the antenna coordinate frame. To avoid this issue, you can use a sensor that targets your receiver antenna to the Transmitter object. This ensures that the signal will arrive on the positive Z (boresight) direction of the receiver antenna coordinate frame. |
| COMMRAD-252 | TIREM does not use the terrain server. |
| COMMRAD-386 | When you set the antenna gain contour resolution low, there are rare occasions when backlobe gain does not appear. Increasing the resolution on the Receiver, Transmitter, or Radar object's 2D Graphics Contours Antenna Gain page will trigger the backlobe gain to appear. |
| COMMRAD-395 | There are known anomalies under certain use cases associated with drawing RIP contours. |
| COMMRAD-396 | Antenna contours are not drawn properly in situations where the contours are projected past the central body's horizon. Increasing the Az-El may help draw the contour closer to the horizon. |
| COMMRAD-397 | Antenna contours computation is not correct for azimuth of one backlobe sample. Increasing the Az-El may help draw the contour closer to the sensor's horizon. |
| COMMRAD-407 | Comm System graphics may not appear if the Comm System object contains a transmitter or receiver that is used as a grid instance of a Coverage Definition object when the grid is specified to use the actual instance and a Figure of Merit object exists that uses a Comm access constraint. To work around the problem, you should either use a copy of the Comm System object for the grid instance or set the Coverage grid to not use the actual instance. |
| COMMRAD-463 | For Cable type receivers and transmitters, the Basic - Refraction properties page is available but not actually used for modeling. Refraction is related to propagation through the atmosphere, which is not defined for receiver and transmitter models that propagate through cables. |
| COMMRAD-3538 | When using the Ansys RF Channel Modeler™ (RFCM) plugin, the 3D Graphics window does not draw the RFCM extents correctly on the surface of the globe when displaying terrain. |
| COMMRAD-3767 | When importing an FFD file from HFSS and interpolating at zero degrees azimuth or elevation, the gain might produce an artificial null in the antenna gain pattern. |
| COMMRAD-3947 | The RFCM plugin uses analytical 3D tilesets from the STK scenario. If you set up an RFCM analysis to reference one of the STK scenario 3D tilesets and then you delete that tileset in STK scenario, the tileset will not be removed from the RFCM analysis. This can lead to issues with scenario loading and computations. If you need to remove a tileset from the scenario list, first remove all references to it inside of the RFCM analyses. |
| EOIR-116 | When you report sensor-to-target metrics for a multiband EOIR sensor, a band selection dialog box will appear. The computations will report results for the selected band. However, the other EOIR data providers will report on the render band's properties, such as band name, field of view, and number of pixels. This can cause confusion. To avoid this, manually set the render band either through the EOIR sensor properties GUI or through the object model. |
| EOIR-129 | EOIR maintains its own global material map, which is separate from the STK application and Bing imagery. This results in misregistration in certain areas that can extend to kilometers in dimension. |
| EOIR-131 | For EOIR, date and time values passed by Connect commands on the edges of access windows can occasionally cause data providers to return zero values. |
| EOIR-135 | EOIR shadow mapping operates at the granularity of the surface tessellation and thus generates "saw tooth" looking shadow edges or no shadows at all. |
| EOIR-151 | Using the box shape with multiple components in EOIR can result in incorrect temperature values. The workaround is to utilize custom geometric meshes. |
| EOIR-180 | Looking from space to Earth or looking to the horizon from an aircraft, when the atmosphere is turned on, the graduation of light and dark at the terminator [sunrise/sunset zone] appears as a saw tooth boundary. This applies when Scene Detail is set to Smoothed or Fine. |
| EOIR-1146 | Motion blur has two unexpected behaviors. First, in the case of a fixed sensor with a target of interest passing through, the direction of blurring does not match the direction of motion. Second, in the targeted sensor case, there is motion blur when there should be none at all since the sensor is targeted on the object of interest. |
| GATOR-146 | Copying an initial state segment to another satellite does not copy the volume or maximum fuel mass. |
| GATOR-147 | Lines in calculation graphs in Astrogator using the "Use Segment Colors" option lose their color when the graph is refreshed. |
| GATOR-285 | Astrogator files with extended ASCII characters cannot load into the STK application. You must remove these characters before loading the file. |
| GATOR-3612 | When using the Object Model HPOP propagator in your program, any references to the Force Model, Integrator, or Covariance interfaces and properties become invalid after the Propagate method is called. Therefore, you must reobtain these references from the propagator main interface. The same behavior and workaround apply to the LOP propagator Force Model interface. |
| GFX-1623 | Attempting to load objects that use glTF models in the modelList option into a version of the STK application prior to 11.5 can cause the application to exit if model files are stored locally with the object or are included in a VDF. |
| GFX-1705 | Set as Default with 3D Graphics window annotation does not retain annotations for new scenarios. |
| GFX-1706 | While in X-Realtime animation mode, vector persistence is not correctly supported. |
| GFX-1713 | Facility-based sensors do not fill their projection in the 2D Graphics window. |
| GFX-1716 | Adding a key frame in the Camera Control tool recalculates splined data even when recalculate options are disabled. |
| GFX-1728 | The 2D map will not display *.txm, *.txb, *.pdttx, *.jp2, Bing, or *.mxd when the map projection is set to Hammer Aitoff, Mollweide, Sinusoidal, Azimuth Equidistant, Stereographic, Orthographic, or Perspective. |
| GFX-1729 | Due to the complexity, the sensor range dome fill is not generated when a sensor mask is used as a visual constraint. |
| GFX-1843 | Sensor visualizations may appear incorrect if a sensor is set to intersect with terrain, but no terrain data is available at the intersection's point. |
| GFX-1856 | For fixed sensor Az-El Mask, the Central Body Obscuration flag is not being saved, so when the view is deleted, that information disappears. |
| GFX-1920 | Comm System computations may be lost if the Comm System uses a Constellation that includes the grid constraint instance of a Coverage Definition and the grid instance is set to use the actual instance, not a copy of the instance. |
| GFX-1998 | The 2D Graphics sensor fill does not work correctly for complex sensors that are not simple shapes. |
| GFX-2029 | The Google KML API returns the incorrect value when the visibility field has leading spaces. An example of incorrect formatting is <visibility> 1</visibility>. An example of correct formatting is <visibility>11</visibility>. |
| GFX-2033 | The 2D Graphics window sensor fill for complex conic sensors may not work correctly depending on the sensor intersection with the central body. |
| GFX-2054 | Picking on terrain using computers with nominal onboard graphics chipsets may not be as accurate as when using graphics cards with advanced capabilities. |
| GFX-2173 | Camera control paths may generate errors if you use "Compute Times Automatically" and the first two points of the path are at identical locations. |
| GFX-2316 | If you have an object that uses ephemeris based on another object's coordinate frame, when STK software updates the other object, the graphics do not update correctly. |
| GFX-2320 | Vehicle waypoints and area target centroids do not appear on terrain. |
| GFX-2324 | Planet and Star object labels do not respond when you select the declutter option in the 3D Graphics window. |
| GFX-7589 | There is a loss of fidelity in the 3D Graphics window when modeling thousands of subpanels in the Solar Panel Tool. |
| GFX-7636 | If you create a text annotation in your scenario's 3D Graphics properties and then save your scenario, when you reopen the scenario, the text annotation will not be in the previously designated location. |
| GFX-7663 | Sensor persistence graphics don't honor projection settings. |
| GFX-7671 | Graphics window data displays based on custom reports and calculations do not appear in movies that have been recorded with parallel computing. This is only an issue if the custom report is saved in the scenario directory instead of the STK config directory. If you move the custom report to the STK config directory or the custom report from scenario styles to MyStyles, it appears in the movie as expected. |
| PLAT-1298 | Using "Terrain Height" as the interpolation method for great arc vehicles using an altitude reference of "Terrain" can cause very slow processing when you enable the terrain server. Using "Ellipsoid Height" for the interpolation method will be much faster with approximately the same results. |
| PLAT-1395 | The ExecSingleElementsArray does not return valid results when used with a Chain object. |
| PLAT-1415 | The SetState Connect command cannot be used to create hyperbolic orbits using spherical coordinates for the Two Body and HPOP propagators. |
| PLAT-1481 | Loading an interval file with optional parameters, such as targeted sensor intervals, does not work correctly if done via the STK Object Model. |
| PLAT-1482 | Running the sensor pattern intersection report while BatchGraphics is enabled may generate a report with out-of-date data. |
| PLAT-1632 | Loading and saving a scenario in an STK Engine application without a globe or map control causes the 2D and 3D Graphics information to be lost. |
| PLAT-1648 | When a new Intervals constraint is created using the Object Model's IAgAccessCnstrIntervals interface, it only allows for intervals from an external file to be imported into the constraint. It cannot be set so that it reloads intervals if the contents of the external file were changed. |
| PLAT-1856 | F-35B built-in model parameter values are inaccurate. |
| PLAT-2068 | The STK application may not properly update date and time values to reflect Daylight Savings Time if the scenario is not being run in real time. |
| PLAT-2094 | You should not use instances of TabControl class within a user control embedded into a custom property page for the UI Plugin, as this may lead to unexpected results. |
| PLAT-2109 | Launching a child application from an STK Engine Java application may cause subsequent launches of the STK Engine Java application to fail if you do not terminate the child application. |
| PLAT-2152 | Using a JScript access constraint may cause the STK application to abnormally terminate when you exit the application. |
| PLAT-2163 | There is no option to byass the proxy for local addresses. |
| PLAT-2167 | You cannot debug a UI plugin using Visual Studio 2010. |
| PLAT-2176 | Perl slugin scripts in the STK application are unable to run with ActiveState Perl versions 5.18, 5.20, 5.22, 5.24, and 5.26. You should continue to use version 5.16 (or earlier). ActiveState bug #106314 in Perl versions 5.18 to 5.22 is a know issue that prevents both the 32-bit and 64-bit versions of the STK application from using Perl plugin scripts with those versions of Perl. Until that issue is resolved by ActiveState, the workaround is to fall back to Perl v5.16. |
| PLAT-2443 | In a scenario mixing predefined STK objects and simulated objects received using DSim, animation of some objects may appear jumpy. You can minimize this problem by running the STK application in real-time mode with an offset value of -1 seconds. |
| PLAT-2507 | You cannot debug Java plugins via the Eclipse IDE. |
| PLAT-2830 | Using unicode characters in Connect or any external file may cause the STK application to function incorrectly. |
| PLAT-40807 | Interactions between the STK application and MATLAB can show decreased performance when connecting MATLAB to a running STK Desktop application instance or starting a new STK Desktop application instance via COM on Windows 11 22h3 or later. These performance problems do not appear when starting an STK Engine instance from MATLAB or when interactions between the STK Desktop application or STK Engine and MATLAB are performed via .NET instead of using COM. |
| PLAT-40982 | The Component Manager user interface may show incorrect data when displaying STK Engine plugin properties registered with IAgAttrBuilder.AddQuantityDispatchProperty2. To work around this issue, always use the internal units when registering a plugin property with IAgAttrBuilder.AddQuantityDispatchProperty2 or IAgAttrBuilder.AddQuantityDispatchProperty. For example, when registering a property returning a distance, use "meters" for both display and internal units, use "rad" when registering a property returning an angle, etc. |
| SEET-37 | Computing a condition from a scalar based on SEET is very slow. |
| TETK-820 | In the Track Pick Info window, when you click a track point and increase the pop-up window with the pick information, artifacts appear in the graphics due to the window expansion. |
| TETK-2841 | If you attempt to import a file that has a TSPI mapping but not a time mapping, TETK will throw an error. The workaround is to import the file as additional data, create a time mapping, and then bring the file in through the ATC import panel. |
| TETK-2900 | If a file contains two or more time columns, you may not be able to identify which time column you should select due to the fact that the long name is not visible. |
| TETK-3750 | The Covariance Reader in the STK application may prevent covariance from an older scenario to appear on scenario load.You can work around this by demoting the object, promoting it again, and then enabling covariance. |
| TETK-4640 | When using the scripting tool, you cannot use more than one scalar with a different time span in the same script. |
| UI-151 | Timeline may lose mouse interaction after setting object properties or rearranging windows. Press the Esc key to restore the timeline. |
| UI-185 | Any changes made in the Timeline View's properties window are lost when you close the Timeline View. |