Known Issues

This page details the known issues that exist in the most recent release of SOLIS as well as possible workarounds.

Contents

Loading pre-11.4 Scenarios

There is no autonomous capability to load scenarios that were developed prior to SOLIS 11.4. We apologize for the inconvenience, but the product modifications are simply too great to provide seamless transition. If you have a scenario that is not loading correctly in 11.4 or later that you would like to recover, please contact us through the Service Desk (https://max.rocketlabusa.com/support), and we will help with the transition.

Beta scenarios during 2017 should work with this release.

User Interface Scaling

On some high-DPI displays and/or custom scaling settings, elements in the SOLIS user interface may appear unreadable or unusable. The example below shows what you may see in this situation. The Components list is difficult to read, and the Connections and Parameters tables are not stretched to the end of the window as expected.

4k_api_page_display

Workaround

For Windows 7, Windows 8/8.1, and Windows 10, there is an option in the STK application properties to override the high-DPI scaling behavior. The following steps walks you through the workaround for Windows 10. Steps for Windows 7 and Windows 8/8.1 should be similar.

Access STK Application Properties
  1. Right click the STK application shortcut or STK executable file to display the context menu
  2. Click "Properties"

context_menu_for_STK_12_shortcut

OR

  1. Right click the STK taskbar icon
  2. From the menu that appears, right click on "STK 12"
  3. Click "Properties"

Right Click Menu for STK 12 Taskbar Icon

Set the Scaling Option

In the STK Properties window:

  1. Click the "Compatibility" tab
  2. Click the "Change high DPI settings" button
  3. In the popup, check the "Override high-DPI scaling behavior" checkbox
  4. Under "Scaling performed by:" select "System" (or whichever option provides the best results)

STK 12 Properties

Finalize changes by launching or relaunching STK.

Automation with MATLAB 2018a

This has been resolved in MATLAB 2018a Update 3.

Mathworks introduced a known bug into their .NET code for MATLAB 2018a that caused crashes when working with SOLIS Automation. ASI reported this to Mathworks, and they released a solution in Update 3 of 2018a. Please ensure your MATLAB 2018a is updated to avoid this issue.

Raw Sequence Editor Return Key

When using the Raw Sequence Editor or the Raw Code section of the Sequence Editor, the Return key will stop going to the next line if you have used Ctrl-C at any point.

Workaround

Use Ctrl-Return to go to the next line.

DevTool will not open

Users with strict security settings may find that the DevTool will not open. You will see an error that looks like the following.

Workaround

  1. Open the folder that contains the DevTool `C:\Program Files\AGI\STK 12\Solis\MAXDevTool.
  2. Right click on MAXDevTool.exe and select properties.
  3. Check the `Unblock` checkbox and hit `OK`.

Fixed Issues Set for Release

The following issues have been addressed and will be released with the next version of SOLIS. Until then, please use the provided workarounds to avoid these issues.

Known Issue Description Workaround
Time Editor Crash on Sequence Editor Page When updating any of the Time options in the Time Editor, SOLIS will crash if you try to immediately Add, Copy, or Delete a Sequence or Sequence Modifier and then type in the same Time option text box again without clicking elsewhere. After updating a Time option and adding either a Sequence or Sequence Modifier, click elsewhere on the window before returning to the Time option.
Payload Name Not Saving When adding/changing the name to a Payload, the name will not save if you try to immediately Add, Copy, or Delete the Payload or Payload Modes. Update the Payload name and click "Accept All Changes" at the top of the SOLIS UI to accept the name change.