DH, that will cause my Blueprints to swell up to ridiculous sizes. is why Macros exist.
Jamish, again, surely the point of a Macro is to perform lots of logic on a stream of data.
, your idea is precisely what I’m trying to avoid (but using as a work around for now). I don’t want to spread Blueprint logic checking out across time, during which framerates will vary in different parts of the game and from machine to machine, but spread them evenly across Ticks.
There are always going to be a few cases where you can do something already within BP but an all encompassing hard coded node is better. Epic could ditch the Delay node and let everyone work out timings for themselves using the Delta Seconds output from the Event Recieve Tick. They could ditch the Vector Length node and let you handle that yourself.
Considering the amount of times I and others have used a simple command to end a frame or tick before progressing with logic, mainly for optimisation purposes, I feel that it would be a valuable command.