@PeterJohnson PeterJohnson released this Jan 15, 2019 · 4 commits to master since this release

Assets 6

Getting Started

Download the appropriate file for your platform and see the installation instructions here: https://wpilib.screenstepslive.com/s/currentCS/m/getting_started/l/999999-installing-c-and-java-development-tools-for-frc

For this update, it's okay to skip reinstalling vscode, JDK, and the compiler if you already installed them with 2019.1.1.

After you install the update, vscode will prompt you when opening an older project whether or not you want to upgrade it to 2019.2.1.

Installing Visual Studio Code

Visual Studio Code (vscode) is the recommended and supported IDE. However, it requires a separate download as part of the install process. Make sure to click the "Select/Download" button during the install process if you want to install vscode.

If you need to install vscode on an offline machine, run the installer first on an Internet-connected machine and click the "Select/Download vscode" button. Then copy both the installer and the downloaded OfflineVsCodeFiles zip file to the offline machine.

What's Changed In This Release (since 2019.1.1)


  • [CameraServer] Fix FPS limiting to actually limit average FPS (#1536)
  • [CameraServer] startAutomaticCapture(VideoSource) now returns the created MjpegServer (#1544)
  • [Java CameraServer] Some MjpegServer functions were mistakenly package-private, are now public (#1545)
  • [CameraServer] VideoSink now supports configuration via JSON, similar to VideoSource (#1543)
  • [Java] Fixed Timer.get() handling of accumulated time (#1531)
  • [Simulation] Fix Windows USB camera race condition (#1534)
  • [Simulation] Add notifyNewData function to DriverStationSim class (#1537)
  • The Watchdog implementation no longer clobbers its internal isExpired flag after callback (this lets the callback call Watchdog.disable) (#1527)




Visual Studio Code Extensions



Known Issues and Workarounds

See http://wpilib.screenstepslive.com/s/currentCS/m/getting_started/l/1028964-known-issues

  • Only "known issue" fixed in this release is "Installing and Using GradleRIO Directly May not Deploy JRE"