Unreal Engine 4.7 Released!

You know how it works: New features = new bugs :stuck_out_tongue:

yeap :smiley: downloading now :rolleyes:

I was able to move forward in 4.7.1 - my packaging turned out me referencing my UMG widgets from deep within my actor - by brokering my calls through functions instead of getting an instance to my controller and going into my widgets and calling methods from my actors - also did cause my editor to crash when loading at 93%

if your editor crashes on project load it should tell you in the what crashed it - its probably a suspect uasset, if you remove it, or things calling it - your project will eventually load, you can re-add your widget and relink the nodes (its a pain but the only way I could move forward)

[=BPANDREW;232543]
I was able to move forward in 4.7.1 - my packaging turned out me referencing my UMG widgets from deep within my actor - by brokering my calls through functions instead of getting an instance to my controller and going into my widgets and calling methods from my actors - also did cause my editor to crash when loading at 93%

if your editor crashes on project load it should tell you in the what crashed it - its probably a suspect uasset, if you remove it, or things calling it - your project will eventually load, you can re-add your widget and relink the nodes (its a pain but the only way I could move forward)
[/]

worked for me. Interestingly, didn’t work in 4.7.0, but I tried again in 4.7.1 and by removing the broken asset, loading the project, replacing the asset, then fixing up references, everything loads fine :slight_smile:

Thanks for the advice!

[=Kenomica;232192]
I’m using baked lighting, so I will definitely give it a go. Thanks for the tip.

That did it! THANK YOU!

EDIT : Though it is VERY unstable. After building lighting, there is till a 50/50 of a hard crash whenever I open a map or compile a blueprint.

Also, rotated landscapes still have terrible splotches everywhere, despite the patch note stating it was fixed. Back to 4.6 for me.
[/]

I’m afraid you’re right :frowning: If I restore static lighting to the project it immediately re-exhibits the crash-while-opening syndrome again. So means my workaround just allows us to salvage a 4.6 project by opening it without lightmass.

I’m now trying to tweak as many static lighting related settings/map actors as I can to deduce the root cause, will post any news of success. Might just have to submit a project to Epic on the answer hub as there’s no useful info in the crash either apart from the notorious Access violation writing location <>

UPDATE:
Believe I’ve narrowed it down: Loading crashes for my map if any blueprints in it contain an Instanced Static Mesh component to which instances are added right from the BP’s Construction Script (eg: think static procedural foliage decorations around your actor that you might have created in the construction script for ease of creation or for applying specific visual patterns/etc).

For whatever reason, if you use static lighting and have any such actors in your map then the editor crashes while trying to load that map if its lighting has already been built. The workaround I’m currently testing is to generate all such foliage through a proxy object or a blutility so you don’t have to rely on construction scripts for populating any ā€œstaticā€ instanced meshes.

FWIW, used to work in 4.6.1, 4.5, etc without issues.

[=;232709]
I’m afraid you’re right :frowning: If I restore static lighting to the project it immediately re-exhibits the crash-while-opening syndrome again. So means my workaround just allows us to salvage a 4.6 project by opening it without lightmass.

I’m now trying to tweak as many static lighting related settings/map actors as I can to deduce the root cause, will post any news of success. Might just have to submit a project to Epic on the answer hub as there’s no useful info in the crash either apart from the notorious Access violation writing location <>

UPDATE:
Believe I’ve narrowed it down: Loading crashes for my map if any blueprints in it contain an Instanced Static Mesh component to which instances are added right from the BP’s Construction Script (eg: think static procedural foliage decorations around your actor that you might have created in the construction script for ease of creation or for applying specific visual patterns/etc).

For whatever reason, if you use static lighting and have any such actors in your map then the editor crashes while trying to load that map if its lighting has already been built. The workaround I’m currently testing is to generate all such foliage through a proxy object or a blutility so you don’t have to rely on construction scripts for populating any ā€œstaticā€ instanced meshes.

FWIW, used to work in 4.6.1, 4.5, etc without issues.
[/]

My entire game is based around the populating of instanced static meshes from construction…so yes, I do haha. I’ll certainly give it a try, thank you.

I also have some spawning of instances from the construction script in my project… :rolleyes:

In 4.7 AAIController::MoveToActor() doesn’t really automatically updating its target position like it use to.

I’ve tested using AAIController::GetImmediateMoveDestination() and it seems to be updating once it reach the first target in its path.
Wierd yet, after that my AI running back and forth between its original position and next points along its path.

Hey guys,

just two things that caught my eye with the new 4.7.1 version.

  • When I start with the 3rd person template, the (blueman) character has awful aliasing. A lot worse than in 4.6.1 as far as I can tell
  • The car in the vehicle template has problems with smoothing groups (?)

Anybody else seeing ?
Best regards,
Oli

[=ForGobbler;233143]

  • When I start with the 3rd person template, the (blueman) character has awful aliasing. A lot worse than in 4.6.1 as far as I can tell
    [/]

Could it be your Engine Scalability Settings set to lowest?

Ah, stupid me didn“t know there were these settings :-/ . I just started a new project with the template (quality high). When I“m back from work I“ll have a look at those settings, thanks a lot for pointing them out!

Hello there! I’m trying to get the hand of HTML5, each time I build the project (the FPS template with no starter pack) I get a 75 mb total size of it using the mobile settings, I see a UE4Game-HTML5-Shipping.js file about 47 mb and a nameoftheproject.data of 21 mb, which of these files will the download? The data one? the JS file is a server only info of the Unreal Engine? Will that be downloaded too?

Very basic question, how do we grab the 4.7.1 hotfix from github?

I found there the ā€˜release/promoted//4.7’ branches but no 4.7.1 so im confused if the hotfix is in one of them or something separate

Thanks

[=redphoenix2k;234647]
Very basic question, how do we grab the 4.7.1 hotfix from github?

I found there the ā€˜release/promoted//4.7’ branches but no 4.7.1 so im confused if the hotfix is in one of them or something separate

Thanks
[/]

The latest Release is 4.7.1

UPDATE!

The 4.7.2 Hotfix is now live! It contains a number of fixes for our latest release, all listed below.

If you experience a bug with the 4.7.2 Hotfix, please remember to log a bug report for the on the UE4 AnswerHub to the Bug Reports section.

Fixed in 4.7.2

UE-11207 ios launch fail after upgrading to 4.7.1, provision not found, signing key not found
UE-11202 Horizontal navigation in Notify timelines is super-frustrating
UE-11130 Cannot build code projects for ios
UE-11102 Mac editor sometimes crashes in FMacWindow::IsMaximized when creating a new window
UE-11046 Crash in FLandscapeComponentSceneProxy::GetStaticBatchElementVisibility with tiny component size
UE-11023 Opening the engine crashes: Assert failed: GConfig->GetInt
UE-11018 Synced BlackBoard keys don’t work
UE-8589 MatineeFightScene has no sound on mac
UE-8550 Audio cuts out during scene transitions in the Particle cinematic

Any news on bug:

[]
UE-6988 Game does not gain focus when launching
[/]

It was reported for the very first 4.7 preview. It’s very annoying when launching VR games because you can’t see that focus is on the monitor, and it looks like the game is just unresponsive.

Besides that, I really love 4.7. It has been the most stable version for me so far.

[= ;236968]
UPDATE!

The 4.7.2 Hotfix is now live! It contains a number of fixes for our latest release, all listed below.

If you experience a bug with the 4.7.2 Hotfix, please remember to log a bug report for the on the UE4 AnswerHub to the Bug Reports section.

Fixed in 4.7.2

UE-11207 ios launch fail after upgrading to 4.7.1, provision not found, signing key not found
UE-11202 Horizontal navigation in Notify timelines is super-frustrating
UE-11130 Cannot build code projects for ios
UE-11102 Mac editor sometimes crashes in FMacWindow::IsMaximized when creating a new window
UE-11046 Crash in FLandscapeComponentSceneProxy::GetStaticBatchElementVisibility with tiny component size
UE-11023 Opening the engine crashes: Assert failed: GConfig->GetInt
UE-11018 Synced BlackBoard keys don’t work
UE-8589 MatineeFightScene has no sound on mac
UE-8550 Audio cuts out during scene transitions in the Particle cinematic
[/]

Thank you for release note

[=;236991]
Any news on bug:

It was reported for the very first 4.7 preview. It’s very annoying when launching VR games because you can’t see that focus is on the monitor, and it looks like the game is just unresponsive.

Besides that, I really love 4.7. It has been the most stable version for me so far.
[/]

bug is still under assessment by the development staff. Unfortunately I do not have a timeframe of when it will be fixed and implemented into the engine.

Please fix thatanswers.unrealengine/questions/177571/47-f11-fullscreen-editor-border-black-1.html because is annoying…

[= ;236968]
UPDATE!

The 4.7.2 Hotfix is now live! It contains a number of fixes for our latest release, all listed below.

If you experience a bug with the 4.7.2 Hotfix, please remember to log a bug report for the on the UE4 AnswerHub to the Bug Reports section.

Fixed in 4.7.2

UE-11207 ios launch fail after upgrading to 4.7.1, provision not found, signing key not found
UE-11202 Horizontal navigation in Notify timelines is super-frustrating
UE-11130 Cannot build code projects for ios
UE-11102 Mac editor sometimes crashes in FMacWindow::IsMaximized when creating a new window
UE-11046 Crash in FLandscapeComponentSceneProxy::GetStaticBatchElementVisibility with tiny component size
UE-11023 Opening the engine crashes: Assert failed: GConfig->GetInt
UE-11018 Synced BlackBoard keys don’t work
UE-8589 MatineeFightScene has no sound on mac
UE-8550 Audio cuts out during scene transitions in the Particle cinematic
[/]

Hi, when I click ā€œupdateā€ in the Epic Launcher, it just says ā€œplease waitā€:


I have been waiting for over 5 minutes, something doesn’t seem right?

EDIT: never mind, it started downloading now