@michel, I wasn't suggesting an email notification! Rather, the idea that when you clicked on a plugin it would say that I downloaded it on H=December 12, 2020, or something or something like that. Or perhaps when you looked at your profile, it shows you a list? I imagine that the tech is already built in, because it knows when you look at a topic or when the topic has been updated?
@dako-arkYes, the error shows the the shader cannot be be converted. ""Cannot process ISF Shaders with Vertex Shaders"" means that the program does not yet have the ability to process a shader (.fs file) that has a companion vertex shader (.vs file). We will see to improve this tool, but for now this is a limitation.
ok ... I guessed.
I hope in your furious profiquo.npn job having no skills in this regard.
j'aurai besoin d'un peu d'aide . Je suis nouveau sur isadora et je n'arrive pas à convertir des ISF en GLSL Isadora . j'ai bien suivi le tutoriel ( Isadora Guru Session 11 vers la fin de la vidéo ) mais je suis sur pc et non mac .
Je peux utiliser Google Translate si vous souhaitez écrire en français. Je ferai de mon mieux pour vous aider. ;-)
i seem to have noticed that occasional <SPACE> characters that remain attached to a variable name after dbl-click select and copy, when pasted into the preprocessor code // ISADORA_FLOAT_PARAM(name, id, min, max, default, "help text"); do create the corresponding inputs , but they do not react unless you cancel the <SPACE> character in the preprocessor statement.
took me an hour to figure, one night.
the GLSL editor is kind of tricky, but i attribute this mainly to my italian keyboard. the character '[' freezes the editor until i re-compile.
I think these are very similar to what Isadora already uses, just the parameters are wrapped in JSON... where Isadora is using a comment structure. Perhaps I will spend sometime converting a couple, and if successful right up a how to.