I don’t know what they did but Scene Capture Component 2D is really broken in 4.24 in VR packaged projects as described here Unreal Engine Issues and Bug Tracker (UE-86191) and here Unreal Engine 4.25 Preview - Announcements and Releases - Unreal Engine Forums I was using this for scopes on my guns but I’m getting an even bigger hit on packaged games down from 90 fps to about 20 fps. Is there any other way to create a scope without using a Scene Capture Component 2D?
1 Like
Try setting these console vars to recover performance until they fix it.
r.SceneRenderTargetResizeMethod=2
r.SceneRenderTargetResizeMethodForceOverride=True
Thanks I’ll try that out.
Ok so just had a chance to try it on a packaged project and it has no effect on performance. Unfortunately, FPS still dives down below 20 fps. Is there any other way to do a scope without using a Scene Capture Component 2D? Waiting until 4.25 may or may not fix this isn’t an option, unfortunately.
Try this in 4.25 yet? I’m using a Scene Capture Component 2D, and I had to add r.SceneRenderTargetResizeMethod 2, or perf fell through the floor.
Try adding this to DefaultEngine.ini if you are still having problems.
Setting via console vars may not work properly.
[/Script/Engine.RendererSettings]
r.SceneRenderTargetResizeMethod=2
r.SceneRenderTargetResizeMethodForceOverride=True
1 Like
I’m having issues with this as well, serious performance cost from Scene Capture - I tried these settings in DefaultEngine.ini but I can’t see much of a difference. Any advice? Is this a new bug, has Scene Capture been fast in the past?
Similarly if anyone knows a way to get the framebuffer without using a Scene Capture, any advice would be welcome. I’ve tried using the FFrameGrabber class in C++ but it seems impossible to package the game with it, otherwise it works pretty well in the editor.
The console vars made no difference for me (4.25) Has anybody had any success with this yet?
Any progress on this?
Sill broken with UE 5.4.4
SceneCaptures are not very performant - they are another whole render pass. If there’s a way to make them fast I’d be interested as well. 
We use them fairly extensively for inset camera / magnify windows and remote cameras, the usual.
Afaik the main ways to optimize them currently are: render at lower resolution and turn them off aggressively when not being used.
How come they work for me in 4.24?
Oh because forward rendering?
Anyway, as far as ways to optimize them - yes there are.
They involve re-writing them from the ground up so that they work properly without levaraging the same settings of the default scene. I seriously doubt anyone wants to spend the time doing this for Unreal/Epic.
On the other hand, most other engines out there do not include any real time capture stuff built in as a default anyway, so it’s a give and take/tradeoff if you will.
Generally speaking, with a 2k RT set to real render you get about half the performance if you normally render youur scene at 2k.
It’s more than (because a monitor inst square) your resolution.
That’s why turning down the resolution allows some performance gain (and also consider the fact that you dont need to render 2k and shrink the result down to fit inside 2k, its just really bad pracrice to do so / should be logically obvious even if I bet it escapes most people).
Last but not least, at the very least you got to make sure that the scene captures aren’t rendering/computing height fog, athmosphere, extra light bounces. And probably just disable any option you can do without in them.
When used properly, they work, they are fairly quick.
Quick enough for VR? Maybe not.
You are already rendering 2 screens with an engine that can barely support a single 1080p screen - to the point the main answer to critics about how s*it the rendering is has become “oh you just have to upscale with AI”.
The problem is everyone that accepts this and says nothing about it to Epic.
The problem, in a nutshell, is you.
If you don’t want to be the problem, you use a different engine, and you stop supporting sub par things 
/ horrible practices / exploitatory behaviours.
Since the masses are just interested in being epic fanbois, i doubt you willever see any improvement on engine performance.
Unless somehow people playing fortnite realize they lost 20fps on the same gfx overnight.
Then maybe you get some improvement, but this exact scenario has already happened at least twice (.24 to .25, and again .25 to .26), and no one gave 2 s*its aside from mentioning it in passing… so…