Here are some unordered thoughts on things to look at if the plugin isn't working for you.

1. If you're having trouble pairing, calibrating, etc., charge the PSMove controller fully (overnight) before attempting again.
2. Do not use the PSMove controller when connected by USB. This will just confuse the software.
3. Your C:\Users<username>\AppData\Roaming.psmoveapi (~ \ .psmoveapi in Mac) directory should contain at least 2 files per controller (<controller_address>.calibration and .magnetometer.csv). If the first is missing then run psmovepair again. If the latter is missing then run magnetometer_calibration again.
4. If you are running your UE4 game outside the editor then you'll have to copy psmoveapi.dll and psmoveapi_tracker.dll to the folder containing the game executable.
5. If something crashed when the tracker was running, you may have to unplug your PSEye and plug it back in before it will work again.
6. Your project cannot be named PSMovePlugin or PSMove.
7. If you are on OSX and you cannot link against the .dylibs, despite them being in the correct folder, I may have missed a step before pushing new .dylibs to the plugin. Please let me know, but you can also try opening a terminal window to the PSMovePlugin\Binaries\Mac folder and running the following commands:

install_name_tool -change "libpsmoveapi.3.dylib" "@rpath/libpsmoveapi.3.1.0.dylib" libpsmoveapi_tracker.dylib
install_name_tool -id "@rpath/libpsmoveapi_tracker.3.1.0.dylib" libpsmoveapi_tracker.dylib
install_name_tool -id "@rpath/libpsmoveapi.3.1.0.dylib" libpsmoveapi.dylib

If you'd like to report a problem to me then please state that you've tested the above (otherwise I will redirect you here), and also do the following:

If you're having a problem with the tracker, report whether ps3eye_sdl.exe works, and send me a copy of the contents of the command prompt after running test_tracker.exe

If you've having a problem with orientation, send me a copy of the contents of the command prompt after running test_calibration.exe