v8.50: Bug and Unannounced Changes Megathread

Explanation: The ingame option to disable RHI thread/allow multithread rendering has no effect, and RHI thread will always be in use no matter what the user sets it to, even if locking the game config files to read-only and changing the variable "bAllowMultithreadedRendering" to "=False", the game will use the rhi thread no matter what, with game config file I mean "GameUserSettings.ini" located in "C:\Users\Alex\AppData\Local\FortniteGame\Saved\Config\WindowsClient"

 

and since I am still experiencing regular 1 minute hitches dropping my fps to ~50 from 120 ever since last few updates post 8.30 patch, it would atleast be nice to be able to disable it and see if that removes the hitching for me, even if it means lower average fps in heavy scenes on my quadcore i5-3470 cpu,

 

Evidence: the gamelogs will always output the following lines whenever the game is shutdown:

 

"[2019.04.26-00.31.40:719][948]LogD3D11RHI: Shutdown
[2019.04.26-00.31.40:719][948]LogD3D11RHI: CleanupD3DDevice
[2019.04.26-00.31.40:720][948]LogRendererCore: FGlobalReadBuffer::ReleaseRHI
[2019.04.26-00.31.40:720][948]LogRendererCore: FGlobalDynamicReadBuffer::Cleanup()
[2019.04.26-00.31.40:720][948]LogRendererCore: FGlobalReadBuffer::ReleaseRHI
[2019.04.26-00.31.40:720][948]LogRendererCore: FGlobalDynamicReadBuffer::Cleanup()
[2019.04.26-00.31.40:720][948]LogRendererCore: FGlobalReadBuffer::ReleaseRHI
[2019.04.26-00.31.40:720][948]LogRendererCore: FGlobalDynamicReadBuffer::Cleanup()
[2019.04.26-00.31.40:804][948]LogD3D11RHI: ~FD3D11DynamicRHI"

 

this, in combination with the fact that enabling/disabling the option has zero impact on cpu usage, average framerate in heavy scenes like overlooking tilted towers, and that the game produces regular hitches in 1 minute intervals dropping my fps to 50 from 120, leads me to the conclusion that we still can not disable RHI thread, even if it is good for me in terms of higher fps in heavy scenes, I would rather not have the hitches and stutters to be honest..

 

video example of ingame option having no effect: https://streamable.com/s0oyn

 

If replicable, how: set allow multithreaded rendering to on or off, either via ingame option menu or via config file, and compare performance impact or difference in heavy scenes such as tilted/retail/pleasant/other heavy scene or scenario in game, and see that there is zero difference between the different options

 

Platform: PC

 

I'll make a separate post about the hitching with logs and video example, but already created a thread a week ago or so with 100+ upvotes by now, with a deep analysis on the hitches and gamelogs included with proof and a lot of other info here: https://old.reddit.com/r/FortniteCompetitive/comments/beyued/a_deeper_lookanalysis_into_the_hitches_and/

 

sadly the situation is identical now to then, for whatever its worth , cheers!

/r/FortNiteBR Thread