You will not be able to achieve what you want because of how actors calculate which camera component is Active. Set View node just queries the actor and gets the first active camera (a bit of a mystery how this is calculated, I need to find it in c++, perhaps it’s small fix).
So no, you can’t do it, not in pure blueprints. Especially that you need the rear cam active at all times.
By the way, I skipped this and worked
it around by using a separate Camera
Actor attached to the actor, instead
of using a Camera Component. This
works, but not so convenience as using
a component.
If you mean a Child Actor Component, then that’d be the bast way to go about it as they spawn and destroy actors automatically. That would be elegant enough for most cases.