If its the same issue everyone is talking about MRG will just handle it under the hood.
Lol, I should but I have no idea. I’m just some dude who pops in here when I have a spare moment to try and help people and find bugs. If you find out let me know.
1 Like
Does Epic plan to fix this or no?
1 Like
Just an update on this. Switching to movie render graph renders the full sequence. I do however get some random render artifacts like small blue dots (First image,fixed by insanely rising the spatial and temporal samples, second image) and also just some random horizontal lines which appear or disappear randomly after restarting the engine, third image.
I do mention that these appeared only after switching to mrg. Do you guys have an idea why this might be?
There is no technical reason that we are aware of that would cause this. Normally when I see this sort of thing its a drivers issue.
Thank you Shaun, will try to update.
我已解决,方法是勾选摄像机下的运动模糊,不知道你们这样操作能不能解决
1 Like
Doesn’t work for me.
I tried to go back to 30 FPS and add the motion blur but nothing works. During render shot 2, no more files are created.
**
BUT, I found a solution. It was my console variables.. I disabled it and now all the frames are written on SSD**
On my sequence at 25 fps, the tick rate was already set to 24000fps and it was not working with 9 temporal samples… but it’s working fine with 8, 10, 12 even 16 samples!
Try to set the temporal samples to 10 instead of 8 and keep your sequence at 24 fps. I have tested successfuly on my side.
Can confirm, changing from 8 to 10 temporal samples, changing anti aliasing mode to none fixed it for me.