Unreal Engine 4.26 Preview

[VictorLerp]

Locking this thread - please continue the conversation on the 4.26 release thread. Thanks for all of your help getting 4.26 ready for release!

[rascalnumero1]

• You can now leverage Nvidia’s NVLink for multi-GPU systems to use one GPU to render a viewport and to copy the frame to another GPU to display.
• When scaling nDisplay to a large LED Volume, performance can be improved by leveraging the multi-GPU system. For Virtual Production and in-camera VFX scenarios, this means the inner frustum can now be rendered on a second GPU. (Beta)

Sounds very promising... Any info on how much performance is impacted on large nDisplay volumes if using multi-GPU vs single GPU multi-node nDisplays? Also I'm not aware if there is a limit to how many nDisplay nodes can drive a large volume simultaneously...

[Vanreus]

Hey, is anyone having problems with the dropdown menus on 4k monitor? When I click on a dropdown menu the UI goes crazy.

[Syed]

This thread should be locked..

[tensioncore]

Are you using the 4.26 final build or the preview build? This thread is for the previous 4.26 Preview version...and 4.26 has released.

[Rareden]

Anyone else having multiple issues with global shader compiles on ray traced projects on a 4.26 source engine build. Binary build seems to work fine, but with a source build this is the 3rd different shader compile issue that shows.

[Uraner]

[vr_marco]

It's not available yet - the associated posts will be updated once it is!

Thanks VictorLerp! While waiting for it I have released a tutorial about compiling the engine from source with Chaos enabled.

https://www.youtube.com/watch?v=gbgBcvHVyq8

[VictorLerp]

VictorLerp the release notes mention an opt-in way to get a compiled version of 4.26 with Chaos Physics enabled (instead of PhysX). Can you please share how we can opt-in? Thanks!

It's not available yet - the associated posts will be updated once it is!

[dragonlordsd]

Not sure if anyone's reported this yet, but the Substance Plugin seems to be bugged in 4.26

On the marketplace it's says it's supported, but it isn't possible to install it to the engine, and Unreal will just say "You cannot install this plugin as it is already installed on all compatible engines". It doesn't show up if you check the plugins list in the editor either, and doesn't show up in the launcher's list of installed plugins.

[Ghosk]

Hello, just wondering how can I enable chaos cloth? And can it collide with the environment? Thanks.

[DanH71]

at least that's something. will give it a try. thanks for sharing and yes lets hope they fix what got broke!

[moody.by.name]

yes i have...
also getting this error way too much from simple UI interaction to post trying to render a single frame out of Movie Render Queue.

I've had a bit more luck using the render remote option (even though its still just my PC) - I can see in the dialogue window lots of various errors and waiting for GPU to respond after no time at all etc, but it seems to work fairly often compared to render local crashing with no warning every time - I've given up Render Local for now. I hope they can fix the media render though to be as stable as it was in 4.25

[DanH71]

Has anyone found the Movie Render Queue to work as it used to? I have used it so much on 4.25 with great results - but now it crashes out before rendering one frame on large scenes (that previously on 4.25 could render still frames) without even giving an error message. If I choose render remote instead of render local, I can see it now compiles thousands and thousands of shaders in the dialogue box before it can even render one frame (so takes 3 mins or longer for one 4K image). And exposure has been removed from the Camera setting, so I can't set a manual exposure from there any more. I thought Movie Render Queue was meant to be improved? Has anyone else had these issues?

yes i have...
also getting this error way too much from simple UI interaction to post trying to render a single frame out of Movie Render Queue.

[ArasKARM]

If you don't report all this, it's not going to be fixed, ever..

Thanks but first I'm asking if this is just me, am I doing something wrong or misunderstanding something. I might try it out on a new level see if it's the fact that the project was created in a previous UE4 version has to do anything with it and then file the report. Does it work as intended for you guys?