Calling getVelocityX() or getRobotCentricVelocityX() on NavX2 causes segfault in simulation

[viggy96]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Create project with NavX2
2. Call getVelocityX(), or getRobotCentricVelocityX() (or another axis) in project
3. Run simulation
4. Profit

• Link to code (if applicable):

Expected behavior
Simulation runs correctly

Desktop (please complete the following information if applicable):

• OS: Linux
• OS Language: English
• Project Information:

WPILib Information:
Project Version: 2025.1.1-beta-1
VS Code Version: 1.95.1
WPILib Extension Version: 2025.1.1-beta-3
C++ Extension Version: Not Installed
Java Extension Version: 1.38.0
Java Debug Extension Version: 0.58.1
Java Dependencies Extension Version 0.24.1
Java Version: 17
Java Location: /home/vignesh/wpilib/2025/jdk
Vendor Libraries:
   AdvantageKit (4.0.0-alpha-1)
   CTRE-Phoenix (v5) (5.34.0-beta-4)
   CTRE-Phoenix (v6) (25.0.0-beta-4)
   REVLib (2025.0.0-beta-3)
   ReduxLib (2025.0.0-beta0)
   Studica (2025.1.1-alpha-14)
   URCL (2025.0.0-beta-1)
   WPILib-New-Commands (1.0.0)
   photonlib (v2024.3.1)

Additional context
zsh: segmentation fault (core dumped) /usr/bin/env /usr/lib/jvm/java-17-openjdk/bin/java frc.robot.Main

[viggy96]

Has this been looked at yet? We use these methods on our robot, so it would be nice for the simulation to not crash when these methods are called.