Unreal Engine 4.24 Released!

[frostic]

@Konflict

@fangchampaign As far as i recall the fps had always been limited at 120fps, so the 60hz update rate you saw earlier was probably the monitor vsync locking it for you. You can type in t.maxfps 60 to reduce the gpu load. Or, by changing the editor’s baseengine.ini (SmoothedFrameRateRange) allows you to set the limit to 60 fps of all recent and new projects.
Students try run the project on low quality settings (either change the inis to enforce it upon launch), maybe disable advanced (eg raytrace, blur, taa, etc) effects too on maps/inis, that should provide some improvements running it on outdated / low end equipments. FXAA is a viable alternative for TAA, and it happens to work out better for editing purposes anyways.

I wouldn’t use smoothedframerate. This is not going to help…In vr where everything has to be optimal we have to disable the smooth because it causes hitches a bit. as that feature is a bit costly

I suggest turning that off and investigate a little more into the actual cause being either GPU bound or CPU bound.
and go from there. there are alot of things to cause frame drop ATM the main one is casting dynamic shadows.

There is a huge regression In dynamic lighting and dynamic shadows atm from 4.23 to 4.24.3 each version has got worse on handling these.
I’m hoping they will fix this issue soon.

@fangchampaign

I do see some noticeable FPS downgrade for dynamic lighting. I am a professor teaching architecture and I build some Unreal games for students to study architectural forms. My scenes are typically very simple but feature a dynamic directional light for simulating daylighting (like the one shown in this demo: https://www.youtube.com/watch?v=2t5BA6t0is8&t=62s). From 4.22 to 4.24. The average FPS of packaged games drops for about 2 to 5. For some students, that means their laptop with integrated GPU cannot handle the game very well.

I tested packaged games performance with MSI Afterburner. One interesting thing I found was that for 4.24 games, there was no FPS limit and your GPU load would soon go up to 99%. But 4.22 and older games would cap FPS at 60 FPS to lower GPU load. I am not sure if that has anything to do with the FPS downgrade in 4.24.

best thing to do there would be to go into developer>device profiles, and set some cvars to lower overall scalability settings so once packaged for
your students it will lower the quality a bit. setting scalability options in there is project wide settings that compile. in editor changing them in the sliders in settings is only in editor.
need to set cvars for it to build the settings. this could help reduce the lag so their pc wont lag out