Breaking Parameter DAT forward compatibility issue

2025.32820 vs 2025.33070 - Win11

A Parameter DAT with a single column and row output used to “collapse” to a Text DAT instead of a single cell Table DAT.

Since the latest release this is not true, breaking some of my networks, notably where I used the Parameter DAT to create #defines for my shaders.

You can also see that the Merge DAT produced then some sort of a square character for newlines as well.

Before:

After:

This all results in broken shaders.

Thanks, we’ll look into this right away.

1 Like

It looks like this was a change intended to fix a different issue with the Parameter DAT mentioned here: FIXED: 2025.32820: String Menu Bind issues

We’re looking into the best way to address both problems now.

1 Like

Hi, so after some discussion we’ve come to the conclusion the new behavior is the correct behavior, unfortunately causing the issue in your existing toe file.

Having the DAT sometimes output a table and sometimes output text was causing inconsistencies for some other user setups.

This change should have included a ‘BACKWARDS COMPATIBILITY’ warning in the release notes unforutnately. In your case, you will need to add a Convert DAT after the Parameter DAT to ensure its the text format you need. Or you could convert after the Merge so the shader accepts it.

Is this a workflow you’ve used quite a bit, or a new technique?
Sorry for the inconvenience.
-Rob

Hi Rob, I’d agree this new one should be the correct behavior - unfortunately for some of my older COMPs, but it should be fine, thanks for looking into it.