I love this community 
2 Likes
There was a function called max3() which the crosscompiler doesn’t like the name of, but it wasn’t actually called from anywhere anyway so I deleted it.
2 Likes
So can we get these back onto the portal as well @MikeV?
Nice.
Yes, was puzzled why in 2025.1 suddenly all the #defines broke, looking at Frabrice’s answer. I’d never encountered that in decades of C/C++ coding.
In the original definition #define should only replace if it matches a full token, not a partial token. Looks like somewhere around the ADSK implementation must have taken a shortcut with a regex instead of staying with the established standard. Ouch. Looks like that may have gotten fixed in 2025.2 but then created a new problem elsewhere.
Well the weird thing is that it doesn’t actually complain about anything. After tweaking other things I thought the problem could be but weren’t, finally found it via trial and error by commenting out almost everything in main() and having it return a static color – when THAT didn’t work I knew something else was up…
Exactly. I was going down that same path with y_sample earlier. It’s such a barebones compiler it’s frustrating.
At least on Linux it alerts you to basic syntax errors. On Mac it’s totally silent.
The dirty secret is that (like I did with y_shape) anyone can just upload new source to the Matchbook site and overwrite what’s there. It’s not the most ideal thing, but it also has allowed me to fix/tweak a bunch of crok shaders which I obviously couldn’t in a more user-account-controlled scenario, short of forking my own versions with different names or whatever. But it’s kind of wide open for good, or abuse.
I’m not sure what the ultimate solution is or should be…
2 Likes
It seems like a Git repo as the master repository would be modern and well suited. With the portal there is an easy to use deployment method, we don’t really need a non-standard website with all the issues you highlighted.
It would also make multi-author contributions more feasible.
3 Likes
Yes, I like this idea. I would also love if the shader authors gave better description of functionality, usage and preferably even screen record demos. Some of the shaders are quite mysterious.
3 Likes
Done. All the y matchboxes are updated with the fixes on the portal.
5 Likes
Is the Matchbox collection through the portal a separate/independent source than the Matchbook site?
I looked at a few of the JB shaders and got JB_colorRemap, JB_erodeMatte, JB_lidar, and JB_skyLapse fixed and uploaded to Matchbook, but am going to bed now… I’ll poke at the others later today.
(Note: I’m not sure if erodeMatte and lidar are doing what they should be doing or do under older Flame versions, as I don’t have anything but 2025 running at the moment to test – but they at least run and do something in 2025 now 
and should still work, as ever, in older versions…)
1 Like
Hi Kemal,
The y_* shaders that are failing in 2025.2 appear to be due to Windows newline characters present in the shaders. While we work on a fix, you can resolve this issue by removing the Windows newline characters.
Here’s one way to remove them from a shader file from the shell (there are other methods as well):
tr -d '\r' < ./y_sample.1.glsl > ./y_sample.1.glsl
The only exception is the y_shape shader that also had an issue with the max3 function.
Best regards, Fabrice
1 Like
Hi Ali,
Those shaders appear to have errors and were not working prior to 2025.2. To debug these issues, shader_builder tool will be helpful. Additionally, I believe @ManChicken has identified most of the issues.
Regards, Fabrice
The portal is separate from the Matchbook site. Until I did the update of the y_ shaders last night I’ve just been mirroring the collection of shaders from the Matchbook site on the Portal for ease of use for people who have the portal to installed. It might be a good idea if someone has the time to upload the updated y_ shaders to the Matchbook site. Once that’s done I’ll just go back to mirroring it. Having two sources of matchboxes with different versions of matchboxes will probably start getting confusing and make a mess of things.
Mike
2 Likes
This thread is a case study in how awesome our community is. Props to all of you.
6 Likes
@cristhiancordoba Did the the other y_* shaders and posted the Dropbox link. Maybe he can re-upload them to the matchbook site as well?
I fixed the other JB shaders and uploaded them and had fixed a couple y_ ones too (for other problems) but now I see we are stomping on each others changes at this point (isn’t this fun?) so I am stopping for now.
I was uploading them to the matcbook site, just finished. You can go and put them on top
1 Like
Hi, Is it just me or is there a known issue that we cant install the matchboxes via the logik portal inside of Flame 2025.2.1.