How to set Actor Location from editor script and update visually

I’ve tried two different types of blueprints now but neither are behaving like I’d expect. This is currently from an editor script and I’m trying to adjust the position of the actor (have tried both teleport and set actor location with same results) and while the data updates, it does not visually update in the view. If I go to the details panel and choose that modified field and press enter there - then it visually updates. I’ve been assuming I need to trigger some king of refresh/reload but unaware what the correct process is.

Oddly if I call Set Actor Label afterwards with a unique label, it will update. Something to do with the transform specifically where it won’t update. Even in other viewports its outdated - so its something to do with elements that rely on an event that is never delivered (when edit mode) for functions that upate the transform. If anyone knows a better work around for this, please let me know.

Are you inside an undo transaction?
If not, try starting a transaction before moving the object, and then commit the transaction.


I was not in an undo op as far as I’m aware. The BP attached is what fails to visually update (but does change the location). The begin/end transaction didn’t have any effect - assuming I did that right.

Realized I messed that up, here is try #2. It does create an undo for it, that does indeed undo the set location as expected (in details) but still has no effect visually:

Ah, the specific actor you’re working with is the Landscape actor.
That one may have special rules, because it does a bunch of special things for rendering and occlusion and terrain texture and so on …
You’d have to read the C++ code to find out exactly what the rules are for the Landscape; I don’t think this level of detail is documented in the web docs.

I did suspect that might be the case. Its interesting though that changing the label is a work around. It might actually be just fine for us as having a unique label generated by us for each landscape imported would actually be beneficial. I appreciate your feedback.