[DarkTree]

I've never programmed with Unreal before, but I'm just curious:

What method does one use to wade through such a large list of changes? Do you look for something specific, or read the whole thing, or just assume the changes will bleed flawlessly into your project?

Very impressive update, congrats.

[brandonwamboldt]

They specifically publish upgrade notes at the bottom, so that helps (as many changes won't break your project).

I'm only working on a small hobby project, but I read the bulk of the notes. I mostly look through the subsystems I use most often, and skip over others that aren't super important to me.

As always, the most important notes are at the top. Also, if you follow the live streams, you're aware of some of the bigger changes far in advance (same if you use the preview builds).

[gambiting]

I work in a games studio in the engine team that integrates new versions of our engines and SDKs for PS4/X1 for our projects - basically when an update comes out you look at the section that's relevant to you and see how it integrates with your flow. So graphics programmers are interested how the GPU pipeline is changing, gameplay programmers are interested what are some new improvements in scripting, console programmers want to know if there is anything new we now have to use to remain compliant with Sony/MS requirements....really, very rarely people read the whole thing fully. You read what you need and then try to work from there. Usually a small team integrates a new version of the engine into the project and if there are any problems then relevant people try to help - and if it's deemed stable it's merged into the main branch.