The V-REP API framework can be extended in various ways, in order to offer interfaces that are not directly part of V-REP. This usually happens via a plugin, but other options are also available (add-ons, remote API clients, ROS nodes, BlueZero nodes, etc.). Following lists just a few of them:
The OMPL plugin, courtesy of Federico Ferri. More details here.
The custom UI plugin, courtesy of Federico Ferri. More details here.
The CGAL plugin, courtesy of Federico Ferri.
The ICP plugin
The image plugin
V-REP ROS bridge, courtesy of Riccardo Spica and Giovanni Claudio.
ROS control loop in V-REP, courtesy of Antoine Rennuit.
OpenRTM-aist interface to V-REP, courtesy of Yuki Suga.
Snap! interface for V-REP, courtesy of Ilya Nemihin
Bridge to OpenCV, courtesy of Marco Bellaccini
Shared memory communication, courtesy of Diego Daniel Santiago
Labview interface for the legacy remote API, courtesy of Peter Mačička
C# wrapper for the legacy remote API, courtesy of Hendrik Wiese
Project to control NAO with the NAOqi Python SDK, courtesy of Pierre Jacquot & Gurvan Le Bleis
Xbox 360 controller plugin for V-REP, courtesy of Nicola Di Pol
A VR interface for V-REP was developed by Boris Bogaerts. It can visualize any V-REP scene in steamVR (openVR) compatible VR devices and return user manipulations to V-REP. Installer files are available here (no compilation required, windows only). Instructions on how to use the interface are provided here.
A ROS extension for the e-puck, developed by Andrei Florea and Catalin Buiu, is available here.
V-REP API framework