The Intel® RealSense™ SDK has been discontinued. No ongoing support or updates will be available.
It's always a challenge, as hardware improves, to maintain software that is compatible with multiple generations. This may seem the case to make sure an app will run on both the Intel® RealSense™ 3D F200 and SR300 cameras; but it's really not too complicated.
If you already have an F200 app, written with R4 (v6) or earlier version of the ;Intel® RealSense™ SDK, it will most likely run fine on an SR300 camera (when run by itself); since any R4 or earlier app has a marker that tells the SR300 to go into "hardware compatibility" mode.
Note: Once in hardware compatibility mode, all other simultaneously run applications will also run in compatibility mode.
But native mode on the SR300 is better - so whether it's an existing or new app, use the 2016 R1 (v8) or later RealSense SDK and get the increased range and other improvements when run on the SR300. Plus you can choose whether to add cursor mode for faster, more fluid hand motions that don't require hand calibration.
So let's say you already have an F200 app. To update it to run on the SR300 camera in native mode, Intel suggests that you:
- Confirm your app works with Win 10, DCM 22.214.171.124944 (F200) and DCM 3.1 (SR300)
- Neutralize your code and follow best practices
- Research API and other changes between the SDK versions and check out the Online documentation
- Obtain an SR300 Intel RealSense 3D camera
- Branch your code for any purely SR300 features (currently Cursor mode. See also Moving from hand to cursor mode and Create-a-virtual-joystick-using-the-intel-realsense-sdk-hand-cursor-module.)
- Recompile with RS SDK 2016 R1 and include the 2016 R1 Runtime in your installer.
RealSense Cursor mode
Moving from hand to cursor mode