And I just finished it, it seems to be working nearly perfectly now.
However I did remake the whole blueprint now I use 1 blueprint for multiple portals instead of a separate blueprints for each portal. It should still work with the new tick it’s just one variable which you will have to change to fit your blueprint or just download my project ( https://drive.google.com/open?id=1kzAUZ4-5F5pUHmfOwLBdcDe8FpQSqyiG )
As for the blueprint logic itself this is how I do the scaling
Event Tick - first it figures out which camera is active (sequence or player) and calls a custom event
SetupCapture - this is the custom event, it sets the location and rotation of the Scene Capture 2D inside the portal that will be the exit, the location is based on the relative location of the player compared to the entrance portal and in the end calls another custom event that finds all the actors that are between the screen capture and the portal and hides them because they’ll get in the way and block the visibility of the portal
The exit portal reference is just a variable of the Portal blueprint type. If you’re trying my project the way the portal connections are setup is you put the portal(s) in the level and in the details panel you select the exit portal and the render target for the current portal (so if portal A goes to portal B exit portal is portal B and the render target is the one for portal A)
P.S. I’m from Bulgaria too 