4.15 Released!

[Waves]

What do the new C++ header changes mean for my existing C++ project?

[plipson]

might be nice to also include a summary of what’s new in the documentation. I have in mind whether the GameplayAbility section is documented - but 's comment made me realize there are other areas that probably have been extended or added. Maybe I’m in a small minority, but I’ve gone through most of the docs. It would be helpful to be given some idea about where to look for new information.

[Stephen_Ellis]

@plipson;666739

might be nice to also include a summary of what’s new in the documentation. I have in mind whether the GameplayActivity section is documented - but 's comment made me realize there are other areas that probably have been extended or added. Maybe I’m in a small minority, but I’ve gone through most of the docs. It would be helpful to be given some idea about where to look for new information.

On the Documentation page, clicking the green “New and Updated” button on the right takes you to: https://docs.unrealengine.com/latest/INT/Updates/index.html

Cheers

[Luos (Luos_83)]

hey , any idea what “Now exporting Particle Module, Particle Module Color Base and Particle Module Color to allow users to inherit from them and create their own modules.” means?
Nobody seems to have a clue

[BoredEngineer]

“see our Blueprint Nativization documentation.” look like link is broken

[Stephen_Ellis]

@BoredEngineer;666773

“see our Blueprint Nativization documentation.” look like link is broken

It’s fixed now. Thanks

[Calibanul]

my project exploded from 4.14 to 4.15. I can’t even open it.
“Try rebuilding from source manually”. When I enter VS 2015 update 3 there is a full list of compile errors.
Should I install VS2017?

Thanks

[Stephen_Ellis]

@Luos;666769

hey , any idea what “Now exporting Particle Module, Particle Module Color Base and Particle Module Color to allow users to inherit from them and create their own modules.” means?
Nobody seems to have a clue

It’s so C++ users can inherit new particle module classes from the base particle module classes. I believe it stems from this pull request (Github account needed) https://github.com/EpicGames/UnrealEngine/pull/1968

Creating Visual Effects

Cheers

[Stephen_Ellis]

@Calibanul;666797

my project exploded from 4.14 to 4.15. I can’t even open it.
“Try rebuilding from source manually”. When I enter VS 2015 update 3 there is a full list of compile errors.
Should I install VS2017?

Visual Studio 2015 is still the supported IDE for UE 4.15. It sounds like you will need to work through the list of compile errors and address them individually (it’s possible there is just one root cause that triggers others). I recommend reviewing the Upgrade Notes section of the Release Notes for any changes to be aware of.

Edit for clarity: VS2017 is also supported as of UE 4.14, but there is no requirement to update

Cheers

[Luoshuang]

Dynamic Indirect Shadows for static meshes using distance fields.

Individual Static Mesh assets can enable Generate Mesh Distance Field to compute a distance field, without the memory cost of enabling for the whole project.
New Static Mesh Component properties Cast Dynamic Indirect Shadow and Dynamic Indirect Shadow Min Visibility.
New World Settings property Dynamic Indirect Shadows Self Shadowing Intensity which replaces the cvar.
Added Shadow Resolution Scale to Light Component.

Hooray! Distance Field Indirect Shadows is finally out!

[MaximeDupart]

This can’t be real, too good to be true

[DamirH]

Awesome work guys, congrats on a new release!

That being said, there is one functionality which seems to be increasingly moving toward deprecation with the new GameplayTags, and I’d like some clarification on that. Namely, I’m talking about UDamageType subclasses. Your GameplayTags example uses tags to determine whether damage is fire, physical etc. while in the past we used to subclass UDamageType to achieve that effect. Can we get some info on how those two systems will work together and will there be gameplaytags propagated through the various TakeDamage functions?

[anonymous_user_a21bc35f1 (anonymous_user_a21bc35f)]

Great release, thank you!

Just a question regarding the bloom changes, I found these two quotes in the release notes:

Bloom settings have been updated to provide a more physically correct result by default.

Bloom defaults have also been tweaked to match the new look.

Are the mentioned defaults and settings generally accessible, and where? I am only aware of bloom settings in a post-processing volume, is this what it means?

My underlying question is this: What is the best way to replicate the bloom behavior of 4.14 materials, is there a general setting I can tweak to a certain value or do I have to tweak the materials individually?

[BRF]

Thanks Epic!

Best Regards
MC

[Inferno630]

@necspenecmetu;666846

Great release, thank you!

Just a question regarding the bloom changes, I found these two quotes in the release notes:

Are the mentioned defaults and settings generally accessible, and where? I am only aware of bloom settings in a post-processing volume, is this what it means?

My underlying question is this: What is the best way to replicate the bloom behavior of 4.14 materials, is there a general setting I can tweak to a certain value or do I have to tweak the materials individually?

I’ve been trying to figure this out as well, so I changed the bloom settings in the Post Processing Volume to match the ones in 4.14. If you do r.TonemapperFilm = 0 in the console, it looks at least close to how it used to.

http://i63.tinypic.com/2qdoehi.jpg

Really hoping they reconsider removing that r.TonemapperFilm = 0 option in the future, it looks so much better with the old tonemapping for my project, at least. I understand the importance of realism in many projects, and appreciate that they’re trying to make the defaults that way, but that doesn’t mean other methods need to be completely tossed out (although there’s probably a way to remake it from scratch if someone has sufficient understanding). I guess if they do get rid of it, hopefully someone finds a way to fake it with the new settings or something and posts how they did it publicly.

[Luos (Luos_83)]

@Ellis;666801

It’s so C++ users can inherit new particle module classes from the base particle module classes. I believe it stems from this pull request (Github account needed) https://github.com/EpicGames/UnrealEngine/pull/1968

Creating Visual Effects in Niagara for Unreal Engine | Unreal Engine 5.3 Documentation

Cheers

I know exactly who to make happy now.
thanks

[Sadaleus]

@Devero;666665

Awesome work guys.

I have a question. There was a stream a few weeks ago about the new audio engine and some new features were going to be available in 4.15. I didn’t seen any mention of these new experimental features in the release notes. Did they make it in or did I miss reading it somewhere.

Thanks!

bump this one

[anonymous_user_a21bc35f1 (anonymous_user_a21bc35f)]

@Inferno630;666858

I’ve been trying to figure this out as well, so I changed the bloom settings in the Post Processing Volume to match the ones in 4.14. If you do r.TonemapperFilm = 0 in the console, it looks at least close to how it used to.

Thank you! And I second your opinion of making many different looks/art styles available as painless as possible.

[TriNityGER]

@Ellis;666808

Visual Studio 2015 is still the supported IDE for UE 4.15. It sounds like you will need to work through the list of compile errors and address them individually (it’s possible there is just one root cause that triggers others). I recommend reviewing the Upgrade Notes section of the Release Notes for any changes to be aware of.

Cheers

Is VS2017 fully supported in 4.15? Official VS17 Release is very soon so I’d like to upgrade as fast as possible

[Dan3DIM]

Have lighting in Orthographic issue had been fixed?
(Too long to read all of bug-fix for just one I am looking for)

The Unreal Engine Issues and Bug Tracker