The following table lists the technical issues known to exist in STK.
| Issue Id | Release Note | Capability |
|---|---|---|
| 86955 | The animation interval time components do not display name changes in the timeline when you rename the scenario. | Analysis Workbench |
| 87637 | When multiple Aviator aircraft make use of the same or related TimeComponents and those aircraft also depend on each other in some way, they will not always recalculate in the correct order when the time component is changed. You should manually recalculate those aircraft in the necessary order. | Analysis Workbench |
| 16422 | Copying a propagate or maneuver segment to another satellite does not copy linked autosequences. | Astrogator |
| 39407 | Copying an initial state segment to another satellite does not copy the volume or maximum fuel mass. | Astrogator |
| 55686 | Astrogator files with extended ASCII characters cannot load into STK. You must remove these characters before loading the file. | Astrogator |
| 58165 | Lines in calculation graphs in Astrogator with the 'Use Segment Colors' check box selected lose their color when the graph is refreshed. | Astrogator |
| 94239 | The RA and DEC angles for the Target Incoming Asymptote elements do not locate the incoming asymptote direction using the standard convention formulas. Instead, the incoming asymptote direction, defined as the direction of the incoming velocity vector at infinity, is defined by (X,Y,Z) with X=cos(DEC)*cos(RA+pi), Y=cos(DEC)*sin(RA+pi), Z=sin(DEC). | Astrogator |
| 84196 | Aviator Connect commands do not work with many new phase and procedure options. | Aviator |
| AIR-464 | The NOAA Wind Model no longer works. | Aviator |
| 16587 | A chain that involves objects at large distances (i.e., interplanetary) may produce incorrect answers. | Chains |
| 32078 | There are known anomalies for certain use cases associated with drawing RIP contours. | CommRad |
| 35328 | 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 |
| 35336 | Antenna contours computation gets azimuth of one backlobe sample wrong. Increasing the Az-El may help draw the contour closer to the sensor's horizon. | CommRad |
| 35407 | On very rare occasions, when the antenna gain contour resolution is set low, the backlobe gain may not appear. Increasing the resolution on the Receiver, Transmitter, or Radar object's 2D Graphics Contours Antenna Gain page will display it. | CommRad |
| 43134 | The Basic Refraction properties page, although shown for both Cable type receivers and Cable type transmitters, is not used in their modeling. Refraction is related to propagation through the atmosphere, which is not defined for receiver/transmitter models that propagate through cables. | CommRad |
| 49167 | 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 being honored by the interference constraints. Instead, the interference constraints rely on the Access Defaults settings under 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. | CommRad |
| 54331 | Comm system graphics may not be displayed if the Comm System contains a transmitter or receiver that is used as the grid instance of a coverage when the grid is specified to use the actual instance and a figure of merit exists using a Comm access constraint. To work around the problem, you should use a copy of the Comm object for the grid instance or set the coverage grid to not use the actual instance. | CommRad |
| 69144 | The polarization loss is not accounting for the direction of propagation at the receiver. If the signal is arriving from the direction opposite to the boresight direction (the backlobe direction), then the result is not correct; that is, the direction of signal arrival is the -Z axis in the antenna coordinate frame. One potential workaround for this issue is to use a targeted sensor that targets your receiver antenna to the transmitter object. This ensures that the signal will arrive on the positive Z axis (boresight) of the receiver antenna coordinate frame. | CommRad |
| COMMRAD-201 | The antenna's valid X/Y Dimension limits are not consistent with X/Y Beamwidth limits. Switch to "Use Dimensions" to reach full limits. | CommRad |
| COMMRAD-252 | TIREM does not use the terrain server. | CommRad |
| 01508 | Grid points may not be generated for small custom grids with a single very small area (less than a degree in size). | Coverage |
| 34902 | A coverage definition that uses an object as a grid instance that has an attitude coverage as a child may cause STK to terminate. | Coverage |
| 57979 | EOIR maintains its own global material map separate from STK and Bing imagery. This results in misregistration in certain areas reaching up to multiple kilometers. | EOIR |
| EOIR-116 | Reporting sensor-to-target metrics for a multiband EOIR sensor will display a band selection dialog. 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, and to avoid this you can manually set the render band either through the EOIR sensor properties GUI or the object model. | EOIR |
| EOIR-131 | Date and time values passed by Connect commands on the edges of access windows can occasionally cause zero values to be returned by data providers. | EOIR |
| 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 |
| 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 |
| 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 sawtooth boundary. This applies when Scene Detail is set to Smoothed or Fine. | EOIR |
| EOIR-1071 | Point-source targets in a sensor scene always return 0.0 for Target Az/El. | EOIR |
| EOIR-1108 | For the case where you change the Input level for Image Quality to Custom Point Spread Function (PSF) from something else, the new value for effective instantaneous field of view will not be correct. | EOIR |
| PLAT-1847 | You can no longer add LocalTime, GMT, ApparentTime, Intervals, and Duration constraints to a single object multiple times via the Object Model. | General Astro |
| GFX-1920 | CommSystem computations may be cleared if the CommSystem 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. | Graphics |
| PLAT-1675 | When using the Object Model HPOP propagator programmatically, any references to the ForceModel, Integrator, or Covariance interface and properties become invalid after the Propagate method is called. Therefore, you must reobtain them from the propagator main interface. The same behavior and workaround also apply to the LOP propagator ForceModel interface. | Object Model & APIs |
| PLAT-1648 | When you create a new Intervals constraint using the Object Model's IAgAccessCnstrIntervals interface, it only allows for intervals from an external file to be imported into the constraint. You cannot set it to reload intervals if the contents of the external file were changed. | Object Model & APIs |
| 120657 | The unattended install for the Portal is not working. | Parallel Computing |
| COMMRAD-288 | The Component Manager user interface may show incorrect data when displaying 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 distance, use "meters" for both display and internal units; use "rad" when registering a property returning an angle, etc. | Plugins |
| PLAT-1752 | The strip chart customization dialog box interferes with setting strip chart duration and Y limits. Set colors are not retained. | Reports & Graphs |
| 48494 | 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 STK in real-time mode with an offset value of -1 seconds. | RT3 |
| 118207 | 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. | STK Engine |
| 121382 | When loading STK Engine in MATLAB, there is a risk of having missing Intel Fortran symbols with older versions of MATLAB. The following features might not work when STK Engine is loaded into a MATLAB process:
|
STK Engine |
| 04660 | Graphics do not update correctly for an object using ephemeris based on another object's coordinate frame and when the other object is updated. | STK General |
| 04798 | STK may not properly update date and time values to reflect daylight savings time if the scenario is not being run in real time. | STK General |
| 05008 | 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. | STK General |
| 101063 | F-35B built-in model numbers have been updated to reflect generic fighter aircraft | STK General |
| 103957 | Attempting to load objects which use glTF models in the modelList option into versions of STK prior to 11.5 can cause STK to exit if the model files are stored locally with the object or are included in a VDF. | STK General |
| 105496 | Sensor visualizations may appear incorrect if a sensor is set to intersect with terrain, but no terrain data is available at the intersections point. | STK General |
| 105702 | Significantly reduced the memory footprint of glTF models using the default reflection environment. | STK General |
| 13207 | 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. | STK General |
| 19694 | The 2D Graphics sensor fill does not work correctly for complex sensors that are not simple shapes. | STK General |
| 22657 | While in Xrealtime mode of animation, vector persistence is not correctly supported. | STK General |
| 23935 | Set As Default with 3D Graphics window annotation does not retain annotations for new scenarios. | STK General |
| 28211 | Waypoints and the area target centroid do not display on terrain. | STK General |
| 34071 | Planet and star object labels do not follow the declutter option in 3D Graphics windows. | STK General |
| 35538 | The sensor pointing option "Grazing Alt" should optimally be used to point a sensor if it is on an object with a nadir-aligned Z axis attitude, as it assumes an azimuth constraint and solves for elevation. During a period where 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 as well as a graphical representation. | STK General |
| 35647 | Facility-based sensors do not fill their projection in the 2D Graphics window. | STK General |
| 40703 | Models cannot have multiple SolarPanel commands in one component or data may not be generated correctly. | STK General |
| 47956 | Camera control paths may generate errors if "Compute Times Automatically" is used and the first two points of the path are at identical locations. | STK General |
| 48729 | Report style places in subdirectories of MyStyles and the scenario folder in the Report and Graph Manager cannot be selected for 3D dynamic displays. | STK General |
| 49338 | There is a known issue with a TabControl .NET class and custom property pages created by the UI Plugins implemented in .NET. Using instances of TabControl class within a user control embedded into a custom property page for the UI Plugin may lead to unexpected results and should not be used. | STK General |
| 51337 | If you export a graph file to a directory and the directory name contains a period (.), the file extension is not included when the file is saved. The workaround is to either pick a different directory or append the file extension after the file is saved using the Windows file browser. | STK General |
| 53247 | The Google KML API returns the incorrect value when the visibility field has leading spaces. An example of incorrect behavior is |
STK General |
| 54205 | The ExecSingleElementsArray does not return valid results when used with a Chain object. | STK General |
| 55720 | Sensors located on Facility or Target objects using Fixed In Axes pointing method include additional 180 deg offset about Y-axis of the reference axes. This behavior was designed to be consistent with that of the legacy Fixed pointing method. | STK General |
| 56514 | Launching a child application from an STK Engine Java application may cause subsequent launches of the STK engine Java application to fail if the child application is not terminated. | STK General |
| 57866 | Using 2D fill for complex conic sensors may not fill correctly on the 2D map depending on the sensor intersection with the central body. | STK General |
| 58153 | Java plugins cannot debug via the Eclipse IDE. | STK General |
| 60934 | Adding a key frame in the Camera Control tool recalculates splined data even when recalculate options are disabled. | STK General |
| 63993 | The SetState Connect command cannot be used to create hyperbolic orbits using spherical coordinates for the Two Body and HPOP propagators. | STK General |
| 64514 | Loading an interval file with optional parameters, such as targeted sensor intervals, does not work correctly if done via the STK Object Model. | STK General |
| 64881 | Using unicode characters in Connect or any external file may cause STK to function incorrectly. | STK General |
| 66339 | Running the sensor pattern intersection report while BatchGraphics is enabled may generate a report with out-of-date data. | STK General |
| 72411 | Picking on terrain using computers with certain onboard graphics chipsets, particularly the Intel HD and Intel HD 3000, is not as accurate as when using graphics cards with advanced capabilities. | STK General |
| 73437 | The 2D map will not display txm, txb, pdttx, jp2, Bing, or mxd files when the map projection is set to Hammer Aitoff, Mollweide, Sinusoidal, Azimuth Equidistant, Stereographic, Orthographic, or Perspective. | STK General |
| 74499 | Due to the complexity, the sensor range dome fill is not generated when a sensor mask is used as a visual constraint. | STK General |
| 76922 | Using a JScript access constraint may cause STK to abnormally terminate when exiting STK. | STK General |
| 79295 | There is no option to bypass the proxy for local addresses. | STK General |
| 81044 | You cannot debug a UI plugin using Visual Studio 2010. | STK General |
| 84624 | Perl plugin scripts in STK are unable to run with ActiveState Perl v5.18, v5.20, v5.22, v5.24, and v5.26. It is recommended that you continue to use version 5.16 (or lower) release of Perl. ActiveState bug #106314 in Perl v5.18 to v5.22 (https://bugs.activestate.com/show_bug.cgi?id=106314) is a known issue that prevents both the 32-bit and the 64-bit versions of STK from using Perl plugin scripts with those versions of Perl. Until that issue is resolved by ActiveState, the workaround is to fallback to Perl v5.16. | STK General |
| 86936 | Any changes made in the Timeline view's properties window are lost when you close the timeline view. | STK General |
| 90105 | Comm contours cannot be exported to a shapefile when the "NoGraphics" option is used with STK Engine. | STK General |
| COMP-4472 | Licensing checks execute earlier than expected in certain unusual situations. This leads to a licensing exception when using ActivateLicense. | STK General |
| DOC-4 | The Contact Support button is not working within the help. | STK General |
| GFX-1856 | If you bring up the sensor obscuration, Az-El Mask, and solar panel tools, the selection tree does not work as intended. You cannot select an item or click Apply. | STK General |
| 121089 | Insert > From File fails on machines running Windows 11. | STK General |
| COMP-137 | EarthFixedAxes assumes Earth from the CentralBodiesFacet.GetContext().Earth. | STK General |
| SEET-37 | Computing a condition from a Scalar based on SEET is slow. | STK General |
| PLAT-1256 | 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 the attitude not being computed correctly. The attitude can usually be corrected by reapplying the attitude settings. | STK General |
| PLAT-1648 | HTML Viewer is based on Internet Explorer. This older browser technology doesn't support newer HTML on many websites. Use STK's Web Browser when using modern HTML tools and sites. | STK General |
| PLAT-40183 | STK 12.9.0 does not support MATLAB 2024a Update3. We are working with Mathworks on a solution. | STK General |
| PLAT-1298 | Using "Terrain Height" as the interpolation method for great arc vehicles using an altitude reference of "Terrain" can be very slow when terrain server is enabled. Using "Ellipsoid Height" for the interpolation method will be much faster with approximately the same results. | Terrain & Imagery |
| 100377 |
When loading old scenarios using relative times other than Day Seconds (e.g. minutes, hours, days), two metadata tags must be added to the files Is Day Seconds and Second Multiplier. Example:
If the data is in seconds, you just need the Is Day Seconds tag. Old scenarios that used Unit Definition files (.def) need to move the .def files either to the TETK data directory specified in T&E preferences or must be in the same directory as the file using the .def file. The name of the .def file needs to match the name of the imported file (e.g., Ownship.csv and Ownship.def) |
TETK |
| 103629 | TETK only supports Watts and multiples of Watts as units for power. | TETK |
| 104155 | A bug fix to the Covariance reader in STK may prevent Covariance from an older scenario to display on scenario load. You can work around this by demoting the object, promoting it again, and then enabling covariance. | TETK |
| 104638 | If an STK object is changed with 3D edit while the graph is open, you may need to click the refresh button on the graph after 3D edit is complete to have the graph update. | TETK |
| 108158 |
STK does not support dB units for radar parameters. |
TETK |
| 109024 | If Short Name is selected on panels displaying data elements of arrayed data, the array index may not display. Changing the panel to Long Name displays the array index. | TETK |
| 109151 | When duplicating XY graphs, the Time selection returns to the default value of Y times. | TETK |
| 109008 | The save scenario connect commands duplicate scenario directories when not using the SetDefaultDir parameter. | TETK |
| 110595 | Unit validation dialog only displayed once when importing. | TETK |
| 110647 | Video audio continues when overlay is hidden and becomes choppy when animating faster or slower than 1x. | TETK |
| 110692 | ATC Data Import will error if time mapping doesn't exist. | TETK |
| 116167 | When using files with multiple objects for Associated State, you must create the mapping before starting the Associated State dialog. This may require you to start the import, create the mapping, and then restart the import. | TETK |
| 116521 | When saving a VDF file to a name that is different from the STK scenario name, groupings in the object browser are lost. | TETK |
| 117742 | If a file contains multiple time columns, it is difficult to identify which time column should be selected since the long name isn't visible. | TETK |
| 117769 | Deleting an associated state from a multi-import file deletes all imported files. | TETK |
| 117865 | If you duplicate an AzElR mapping, then the original reference frame is lost when editing the mapping. | TETK |
| 119072 | When using the scripting tool, you cannot use more than one scalar with a different time span in the same script. | TETK |
| TETK-820 | On machines where High DPI scaling is override to System (Enhanced), artifacts are created when the size of the pop up Track Pick Info window is expanded. To fix this, change the High DPI Scaling to System. Further tips on working with 4k resolution can be found in this knowledge article: https://analyticalgraphics.my.site.com/faqs/articles/knowledge/Why-are-my-STK-icons-so-small-on-Windows-10-and-how-can-I-fix-it. | TETK |
| TETK-834 | When hiding a track that is using comparison colors with a covariance ellipse, the ellipse does not disappear with the rest of the track and instead reverts to an uncolored state. | TETK |
| TETK-1022 | Loading a scenario with an integrated, full-sized graph causes an error. | TETK |
| TETK-2461 | Multi-metric time intervals require either a label or icon to be selected to create the time component. | TETK |
| TETK-2528 | If a time constraint is applied to a track using the Bounds Filter tab, the Current Marker and Connection Line MTO items are not updated correctly with the new set of valid points. | TETK |
| UI-151 | Timeline may lose mouse interaction after setting object properties or window rearrangement. Press ESC key to restore the timeline. | User Interface |
| UI-174 | Optimization tool may change Analyzer resolution on a 4K monitor. | User interface |
| UI-185 | Any changes made to the Timeline View's properties window are lost when you close the timeline view. | User Interface |
| 86111 | 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 due to single precision computations performed on GPUs. | Volumetric |