You may also want to find a monospace font to use, this way you can calculate the space required for the word, since each letter will take up equal space. That should allow for a grid like layout to become possible. Rotation will be another monster.
@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. ;-)
Remove the space between ISADORA_FLOAT_PARAM and (
So the second one ;) The first one is your example
// ISADORA_FLOAT_PARAM (noise_level, noil, 0.0, 1.0, 0.5, "This is the text that helps");
// ISADORA_FLOAT_PARAM(noise_level, noil, 0.0, 1.0, 0.5, "This is the text that helps");
Hi all ! if anyone can point how to solve this. I need to change something about this shader. It works fine but when I insert it as a Tex Map in the 3d particles it does like a very fast and sutil "black out" when the color changes. And because of that the particles dissapear for a second. I cant find in the code that behavior.
because there is no time I went back to a previous version of my patch, that solved it.
I actually use a very large .png file (because it's the only way i know to show fotos in rapid random sequences, I pan around the big file, real smooth and 60fps).
the error is much more likely to happen when the scene jumps have a fade time > 0. I assume that means running both scenes and obviously may be problematic.
awaiting version 3 i do not think it's worth the while to check this all out. it may be ok in version 3.
Thanks Michel for the reply. I just looked and I did name it correctly and the txt file doesn't show up in the GLSL column in Isadora. Will re-read the instruction page...
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.
