I am aware that this might be put into the responsibility of the creator of the add-on, however since I did not have this problem on my Raspberry Pi and it came up new with the Vero V I would like to bring this up and see if others experienced the same and maybe, what could be done about it.
Yesterday I moved from my Raspberry Pi 3 B+ to the Vero V. I transferred my configuration using the built-in backup/restore functionality of OSMC, which worked just fine. However, the Shadertoy screensaver now shows an odd behaviour which didnāt occur on the Raspberry Pi:
Whenever the screensaver kicks in, after some time (I would guess around 30 seconds) one can see that the shader effects start moving choppy and gradually becoming choppier. Furthermore, the pixel count of the effects massively decreases. Both worsens over time, so that after several minutes only a few blocks (or pixels?) of the animation remain, and the movement almost comes to a standstill. Depending on the shader, sometimes it moves only with around 1 frame per second.
I am using the same GUI resolution as on the Pi, which is 1080p at 60 fps.
Any ideas?
Did you clear shadertoy config and reinstall from the repo ?
Also this thread may help - Visualizations not working in 19.3?
And make sure not to use āSound sinus waveā see OSMC Vero V Review - #291 by darwindesign for reference, that isnāt fixed still.
I tried to uninstall the app in order to reinstall it, however the developer obviously did not implement this option. So I tried to reset it to the default settings but that did not change the behavior.
Then I tried to install the Shadertoy repos 19.0.1 and 19.1.2 again from ZIP file, in order to try reinstalling the app from there, however I got the following error message from OSMC:
The dependency to kodi.binary.global.main in version 1.3.0 could not be resolved
What does that message mean? And what version does it refer to - Kodi?
er, why are we talking about v19 here?
Iām no expert on the Shadertoy screensaver, and I think you might get better advice from the developer and should perhaps be using a version that is compatible with Kodi 21.2 (Linux ARM 32bit)
for the current Vero-V software release and not v19 (probably the cause of that dependency error).
There are more recent updated versions of the Shadertoy app, as described here https://kodi.tv/addons/omega/screensaver.shadertoy/ and here - GitHub - xbmc/screensaver.shadertoy: Screensaver with shaders from Shadertoy for Kodi on all OS
I hear you. I just found there should be 20.1.0 (Nexus) and 21.0.2 already. Sorry about my ignorance, but isnāt OSMC on Vero V running on a 64 bit version of Kodi? If so, which Shadertoy version is the right one? Nexus, arm64, armel, armhf ā¦?
Check the links in prev post.
Sure but what made me confused is:
AFAIK the Vero V is based on a ARM64-Prozessor, and the Kodi currently shipped with supports 64bit as well. Hence my confusion about the advice using an installer for ARM 32bit. Is it for maximum compatibility?
Check the following - its a 32 bit Kodi.
1 Like
I ended up with manually uninstalling both add-ons (Screensaver Shadertoy and Visualization Shadertoy), building new ZIP files on my Vero V from the latest sources,
https://github.com/xbmc/screensaver.shadertoy
and
https://github.com/xbmc/visualization.shadertoy
and installing them. However the problem still persists. It is particularly pregnant with the screensaver and while weāre at it, sorry for mentioning the term āVisualizationā in my first post which might have been misleading.
To sum it up: Itās primarily the screensaverās shaders which show the choppiness and extreme block artifacts over time. I will try to correct my first post, respectively.
