Hello everybody, When I was testing the latest version I have realized some of the matchbox nodes are not working. They were working fine in version 2025.1.2. I didn’t test all of them but these are the ones that give an error code on result: y_shape y_sample y_grid y_edgeblur y_dirblur y_blurs The error message in console is “PIPELINE : CProcessShader::RenderFrame::CreateRenderGraph”. Does anyone have the same issue or is there a fix for this?

Hi, I had the same error message with these JB matchboxes: JB_erodeMatte JB_lidar JB_PixelDisplace JB_autoMatte JB_timeDisplace JB_colorRemap JB_skyLapse

I checked a few of those y_matchboxes and they are broken for me as well. Broken on 2025.2 and 2025.2.1, on linux and mac. I guess I’ll go back to 2025.1.1

This is a massive deal breaker. I think this list has gotten worse in 2025.2.1 [image] allklier: Possibly related to this? Matchboxes not working in Flame 2025.1 - #6 by lefebvf I’ll take a look on my 2025 Mac test machine today. We were just getting ourselves ready for an upgrade. @kyener @persona Are you seeing thses errors on Mac or Linux? Probably effects both :thinking:

This has been going on since the transition away from OpenGL to Vulkan. In the old days the matchbox code was more or less sent to the GPU as is. Now a lot more processing is applied. And that can break old code. I’m not sure if ADSK is including some or all of the Logik MX in their automated test suite? Seems like they fix some issues, but then sometimes that creates new ones. See old discussion: Matchbox Shaders in the age of Vulkan & Metal - #11 by JasminRoy

Re:2025.2 and 2025.2.1 All adsk matchboxes appear to be running without issue, from the middle of last night to very early this morning, right before some ars(hole)onist set fire to the countryside, taking out power, comms and telecoms. I haven’t tried the logik matchbook tools. I’m too busy choosing my new 3 bedroom townhouse next to the country club on the land that just became available. Freedumb.

@PlaceYourBetts I haven’t checked all of them on Mac but Y_Sample and Y_Blurs are not working in 2025.2 & 2025.2.1 - same as @stu

Took a look at the code of Y-Sample. Not readily apparent what broke, might have time tomorrow to dive in deeper.

I vaguely recall something about now being able to define what GLSL version a shader is using in the documentation. Perhaps there’s something related to that? Some functions working in one version but not another…just an idea.

Yes. All the y_* shaders specify version 120, which until 2025.2 was the common denominator and very old. It got bumped up to 460 I believe which gives access to some extra features like round() IIRC. That was based on a feature request I made about a year ago. But that’s not it. I made the error go away last night by commenting out one line in the first pass. Just not sure yet what’s wrong with it. All the broken ones are multi-pass shaders, but that could be coincidence. Several y_* shaders do work fine and have similar code patterns including the version 120 declarations. It’s something more detailed. Could also be in the XML

Broken matchbox nodes in Flame 2025.2 (Linux)

Flame Matchbox

allklier November 6, 2024, 5:21pm 3

Possibly related to this? Matchboxes not working in Flame 2025.1 - #6 by lefebvf

Topic		Replies	Views
What type of Matchbox Shader do you wish you had available? Matchbox	74	5873	June 30, 2023
Matchbox shader bug fixes Matchbox matchbox	24	2670	February 11, 2023
Logik Matchbook installation / machbox icons are gone in the BFX & Batch tab Flame Questions matchbox	16	1337	July 24, 2026
Matchbox shaders disappeared from Node bin Flame Questions batch , matchbox	2	480	February 15, 2023
Matchboxes not working in Flame 2025.1 Flame Questions matchbox , flame2025	6	803	October 24, 2024

Broken matchbox nodes in Flame 2025.2 (Linux)

Related topics