![]() Link the addon folder to osmc : ln -s ln -s /home/osmc/xbmc/kodi-build/addons/visualization.shadertoy /home/osmc/.kodi/addons/visualisation. ![]() Visualizations look neat, and let you browse your media smoothly however, there are two complains in this regard. In general, this skin is amazing and very well designed. When Hovering Above The App Center Option, You Will See Your Program Addons In A Secondary Ribbon. DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=././xbmc/kodi-build/addons -DPACKAGE_ZIP=1. Kodi Destiny Skin: beautifully troublesome. Modify lines 3 and 5 like this : id="visualization.shadertoy2"Ĭompile addon : cd visualization.shadertoy & mkdir build & cd buildĬmake -DADDONS_TO_BUILD=visualization.shadertoy -DADDON_SRC_PREFIX=./. Rename plugin to Shadertoy 2 to disable conflict : nano /home/osmc/visualization.shadertoy/visualization.shadertoy/ This is my procedure with OSMC : sudo apt install git zip libgles2-mesa-dev build-essentialĬhange to GLES : nano /home/osmc/visualization.shadertoy CMakeLists.txtįorce GL_LUMINANCE nano /home/osmc/visualization.shadertoy/src/main.cppĬomment lines 24 and 26 like this : //#ifndef GL_RED The issue is due to the GL_RED and GL_LUMINANCE detection. I’ve compiled addon myself from source with changes. Thanks to this post : Where did ShaderToy go? - #12 by Panisher
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |