.. Copyright (c) 2026, Autonomous Vehicle Systems Lab, University of Colorado at Boulder

Version 2.9 Known Issues
========================

.. _bsk-known-issues-2-9-0:

Version 2.9.0
-------------
- The denton flux model API has changed. The module now uses the new data fetching
  API and thus relies on users passing in the correct support data location via
  ``configureDentonFiles``. Previously, the module automatically searched for the
  data files in the ``supportData`` folder.
- When building from source on Python 3.13 using SWIG 4.4.0, a build failure may occur
  if ``pyLimitedAPI`` is set to an ABI lower than Python 3.13 (e.g., ``0x03080000``).
  SWIG 4.4.0 introduces a new C-API codepath for Python 3.13 that expects newer
  definition macros which are not present when targeting older ``abi3`` compatibility. As such, when building
  Basilisk with Python 3.13 or above, we automatically default to using the newer cp313 ABI.
- :ref:`gravityEffector` had a typo where the total gravity potential contribution of the celestial bodies
  was not being computed properly. Fixed now.
- :ref:`MJSite` has an issue where the angular velocity that was being written into the stateOutMsg
  was in the inertial frame components not the body frame components.  This is now fixed.
- :ref:`locationPointing` was calculating the value of ``omega_RN_B`` but not saving it to the
  ``attGuidOutMsg``. This value is now being saved properly.
- The way body-fixed locations are added to Vizard data is changed.  Now Vizard retains a copy of the
  list of locations and only incremental changes have to be sent using the ``vizSupport.changeLocation()``
  method.  If the script was directly manipulating the :ref:`vizSupport` list that functionality no longer works.
  If only ``addLocation()`` was being used and the location information was not live updated, no changes in the
  simulation script are required.  To do live updates to location it is recommended to use
  ``vizSupport.changeLocation()``.
- The support file :ref:`vizSupport` is updated to only have ``enableUnityVisualization()`` check
  if :ref:`vizInterface` has been built or not.  It is recommended that user scripts safe-guard
  their simulation usage of :ref:`vizSupport` function by checking that ``vizSupport.vizFound`` is true.
- In :ref:`vizSupport`, in the method ``setInstrumentGuiSetting()``, corrected the spelling of
  ``showTransceiverFrustrum`` to be ``showTransceiverFrustum``.  The prior argument name has
  been deprecated and will be removed after October 11, 2026.
- For :ref:`vizInterface`.settings, changed the name of ``viewCameraConeHUD`` to ``viewCameraFrustrumHUD``.
  Using the old settings name results in the setting not being applied.
- When building the Basilisk documentation with doxygen 1.15 or newer, warnings associated with
  unclosed quotes are treated as errors and cause the build to fail. Quotes are fixed now.
- :ref:`spinningBodyOneDOFStateEffector` and :ref:`spinningBodyNDOFStateEffector` both registered
  their state variables under the same names, resulting in one overwriting the other when both are
  added to the same simulation and producing a ``BSK_ERROR``. State names are now made unique.