Unreal Engine 4.23 Preview

Tim_Hobson · August 1, 2019, 4:16am

Good that you brought this up and I want to clarify the importance of submitting bugs (any Epic member can also come up and enforce what I am about to say [USER=“4894”] Hobson[/USER])

When the dev team decides to put a release on preview, lets use the 4.23 as example, a separate branch for 4.24 is already created where they continue to develop while the preview is out (not to mention several experimental branches for specific modules and plugins!), so whenever a bug is submitted via form, it is compared with the branch for the specific preview number, against any other that might be released after and also with the one in development, in this case and example 4.24!

This is fairly normal for development and it is also important, because even between previews, something can break! There is no painless path, otherwise test against all. If you say it was working on 4.22.3, then they will add that too, so they can pin-point when the deviation happened!

So, report is a must, with repro steps highly desirable, crash reports while connected with launcher helps identify the user submitting the report, so they can contact the person about the circumstances aswel.

Do not get discouraged with playing with the previews, since there are separate teams working with Chaos, Niagara and Raytracing. The previews exist in order to quickly map hot spots where the users are playing with, and also the Raytracing was told would take many release iterations until it can be considered “released” as feature for once, mainly because it traverses several other features.

Spot on!

The one thing I should also note in here, is that if something is reported in Preview X, it’s not guaranteed to be fixed immediately in the next preview release, or even the major release. It may get lumped into a hotfix, if possible.

Also, keep in mind that SIGGRAPH is happening this week so a lot of our rendering team is there giving talks and learning some cool things along the way.

@Daffrendo

“It’s still the same with the Translucent shadows being fully opaque”

I’ve previously mentioned this, I believe. This will not be solved in this release. I don’t know about 4.24 at the moment since that’s months down the road from now and a lot of development time still ahead to see.

While there are bugs with Ray Tracing, more often than not, because it’s a Beta feature still in active development, things like this are just a limitation of the current implementation.