I’m pretty sure nodes in my batches are randomly resetting. Anyone else seen this? Pretty fucking irritating.
@ytf - not to date…
are there specific nodes that are resetting or entire batch groups?
auto-key / no auto-key
random nodes
@ ytf - ouch.
do you save your batch-groups or do you iterate?
if you iterate, do you write over the previous iteration or make a new iteration?
I never iterate
Some of my write nodes have started to give grief 
None of my other nodes upset me in quite this way.
Am still only on Flame 2023.3
What version @ytf ?
2025.latest
@ytf - sometimes iterations are useful because you can diff between saves and isolate/identify problems.
if you don’t work this way then you need to use a different method such as filesystem snapshots to see what happens between save and re-load.
Until recently I’ve never had an issue.
@ytf - yep - could be a system disk failure? not writing the setup files?
It’s not when I reload. It’s random resetting of all the parameters of a node back to default as I’m working.
@ytf - this also sounds like a disk failure.
check your nodes name.
We have had a bug where this would happen to 1 node type and the propagate, this seemigly has been fixed in 2025.2
The affected batch setup would have a bunch of comp nodes for example all set to a empty name, which caused havok
Dude, I haven’t set anything to an empty name since day 1. That’s crazy shit.
1 Like
How do you save your batches then?
I use the save button. It’s on the left. Then I save my desktop. Then I archive.
EDIT: I forgot to mention, I hold down the Alt Key when I save.
in pokemon you also had a higher chance of catching a pokemon when you hold down B really hard after you throw a pokeball.
2 Likes
this is some bug, check the nodes that got reset , do they have a name?
Of the two that I took note of, one was a colour correct and one was a degrain. I’m not ruling out a PEBSAK. I was working fast in unfamiliar territory. They always have a name, but they were default names that are created when I pull them up into the batch.
yea thats fine then and not the same bug we had where the name would dissapear and we had nameless nodes, a state that should exists