Ok some further investigating:
The bare minimum for this to occur=
*birth terrain
*terrain mesh
a ty terrain colour map in a material (it doesn't matter what type) linked to a tyflow. The material doesn't have to be assigned to an object, it can sit in the editor.
It seems to me that something is being evaluated every frame and the ram just keeps geting eaten up. Even advancing 1 frame is sluggish.......
***update***
closing the material editor stops this behaviour, so very wierd.
[attachment=3190][attachment=3190]
ram_eating_monster.max (Size: 812 KB / Downloads: 132)
The bare minimum for this to occur=
*birth terrain
*terrain mesh
a ty terrain colour map in a material (it doesn't matter what type) linked to a tyflow. The material doesn't have to be assigned to an object, it can sit in the editor.
It seems to me that something is being evaluated every frame and the ram just keeps geting eaten up. Even advancing 1 frame is sluggish.......
***update***
closing the material editor stops this behaviour, so very wierd.
[attachment=3190][attachment=3190]
ram_eating_monster.max (Size: 812 KB / Downloads: 132)