To add Feel to your project, simply follow the simple steps below :
- using 2019.4.13f (or a recent version of Unity of your choice), create a new project, pick the “3D” template
- via the asset store panel, go to the Feel page, click the download button, then the import button
- wait until a “import Unity package” popup appears, make sure everything is checked (it should be by default), click “import”
- open Unity’s Package Manager, install the latest version of the Post Processing package
- in the package manager, install the latest version of the Cinemachine package
- in the package manager, install the latest version of the TextMesh Pro package
- in the package manager, install the latest version of the Animation 2D package (this is only useful for the Letters demo)
- open the MMFeedbacksDemo scene (or any other demo), press play, enjoy
Note that steps 4, 5, 6 and 7 are optional, but if you want to get access to post processing, TextMesh Pro and Cinemachine feedbacks, you’ll need these. Also note that most of the Feel demos make use of as many feedbacks as needed, and will feature most of these dependencies. You’ll get errors in these if you haven’t installed the corresponding dependencies. You can check the MMFeedbacksMinimalDemo scene if you’re not interested in any of the Unity packages feedbacks.
URP and HDRP
Feel will work on all render pipelines, and you can absolutely import Feel in a URP or HDRP project. Just note that most demos are made using the standard RP, and they may not render correctly when opened in projects using other pipelines. And of course there’s no need to install the Post Processing package on URP or HDRP, they both ship with their own post processing Volume system.
As of v2.3 you’ll find dedicated HDRP and URP demos (see the dedicated section of the documentation). Of course you’ll have to install them in a project matching their RP.
Nice Vibration’s AHAP converter
Since v2.4, the Nice Vibrations scripts that let you convert AHAP files into assets for Android and rumble are available via a .unitypackage located in the NiceVibrations folder. The reason for that is that in some cases they could cause a minor error (see below), and apparently a lot of people don’t read the documentation. Not you though, so thank you! If you need these files, simply unpack the .unitypackage. If you don’t need them, you can safely ignore it.
I’m getting an error about Newtonsoft.Json.dll
Before v2.4, if you’re getting the following error :
PrecompiledAssemblyException: Multiple precompiled assemblies with the same name Newtonsoft.Json.dll included on the current platform. Only one assembly with the same name is allowed per platform.
then you likely have two instances (or more) of that dll in your project. This dll that ships with Nice Vibrations helps it serialize and deserialize JSON to generate advanced haptics files. If you’re getting this error, it may be because you’re using another asset or plugin that shipped with it, or maybe you’re using a version of Unity that directly includes it (typically 20201.1).
In any case, as the error message suggests, you can simply delete the dll that ships with FEEL, and your error will go away. You’ll find that dll at Feel/NiceVibrations/ThirdParty/Newtonsoft. Simply right click on it, and remove it. Unity will then recompile scripts, after that you can clear the console and the error will be gone.