Yes - I've observed problems with refreshing too. In my case, I was trying to simplify my graph by gradually turning off some noise/blend generators to see if I could make generation more efficient while not affecting the output too much. Was surprised to see that I'd removed half of the graph before any perceptible change to the terrain and then, *boom* clicking on the the scene window rather than the mapmagic editor window suddenly made my terrain completely flat! I did occasionally have problems in earlier versions too, but clicking "Generate" seemed to resolve. Now I have to unpin and repin terrain to make it update correctly. A second, possibly unrelated bug I've encountered is in using the new Blend generator. EDIT - Actually, forget that, I've just realised the problem: I was combining several non-commutative blend operations (i.e. an Add and a Multiply) in a single blend generator, and assumed that the order in which blends happen is from top-bottom. Of course, it's not - it's from bottom-top, so I was getting the wrong output. This might need to be made more explicit somewhere! UPDATE - Weird. Now when I create a new Blend generator node, it has a default "Add" layer (greyed out) in the bottom slot, which makes is obviously the "Base" layer as used to be called in the old generator, and other blended layers are stacked on top of that. But when I first started using v1.7, that didn't appear - there were no layers present in the generator (just like when you create a new output generator), and I had to manually create the first layer specifying the Add mode (which is why I then created all the other layers assuming they would follow the first top-down, rather than bottom-up). Weird serialisation/caching issue following upgrade?