material nodes are a pleasure to work with, I can’t believe blueprint nodes come from the same app, they are so unintuitive
for a fog effect I want a stack of planes in front of the camera, I can make the stack but it won’t rotate with the camera, this is as far as I’ve got
I have tried to attach it to the camera but run in to various issues like static mesh component and static mesh reference not being compatible, really quite fed up with this now, I like learning things myself but there’s no chance of that happening here
material nodes are a pleasure to work with, I can’t believe blueprint nodes come from the same app, they are so unintuitive
[/QUOTE]
For me as a programmer I experienced the same opposite 
More details about what you’re trying to create and an image of your actor’s component hierarchy as well as one for how the ingame result looks like would be useful for me to understand what’s going on. What is the Plane Variable? In general attaching meshes to the camera (as child components I guess?) sounds counter-intuitive for me.
plane variable is a static mesh reference containing the plane I want to duplicate
this is how the blueprint from the first post looks, but that will not follow the camera when I pitch up and down, I understand why this is, but I don’t know how to attach it directly to the camera
This wouldn’t be the approach I would try to create a fog effect but you could create a new array variable of StaticMeshComponent and add the return value of your AddStaticMeshComponent node to that array. Now in EventTick you can iterate over each element of that array and set the rotation of the element to the rotation of your camera.
it’s for volumetric fog, the end result looks pretty good, I don’t know of another way to get real volumetrics
I figured it out, if I add an attachtocomponent node on its own I couldn’t attach what I want, but if I pick it with a scene component target it adds a different attachtocomponent node or something? it seems to be working anyway
this is all highly confusing