4.13 Released!

Hello,

I tried importing an Alembic file but it resulted in a crash. I have posted the details on AnswerHub:

Any ideas how to resolve this? What format are you expecting the Alembic file to be written as? What I mean is how is your loader expecting the vertices, points and uvs named in the alembic file? Is there any structure it expects?

Thanks!

new Preview Scene Settings panel

Hello,

where and how I can get new “Preview Scene Settings panel” to work with?

thanks
regards

Anyone else feel like this is abit in the future ?

[=kestrelm;588904]
Hello,

I tried importing an Alembic file but it resulted in a crash. I have posted the details on AnswerHub:

Any ideas how to resolve this? What format are you expecting the Alembic file to be written as? What I mean is how is your loader expecting the vertices, points and uvs named in the alembic file? Is there any structure it expects?

Thanks!
[/]

I’ve reported and responded to your post with the information you provided and what I found while working with your asset.

[=Bimbachi;588916]
Hello,

where and how I can get new “Preview Scene Settings panel” to work with?

thanks
regards
[/]

You should see a tab in the Static Mesh Editor next to the Details Panel that allows you to set all the scene’s settings. If you don’t see it, you can go to Window > Preview Scene Settings to enable it.

[=DanielW;588843]
Directional light shadowmaps (CSM) are view dependent and require a complex scrolling approach to properly cache them. Plus directional light shadows are often combined with WPO animated foliage which can’t be cached, so it’s lower in priority.

Skylights don’t use shadowmaps.
[/]

Crytek also noticed the view dependency makes caching harder, so they made cascades aligned to light space, at the price of wasting texels:
Playing with Real-Time Shadows, Page 55, CRYENGINE - Crytek"s powerful game development platform

Hi all,

I’ve just released the Plastic SCM plugin 0.8.1 beta release for this new UE 4.13.

Enjoy the shinny 4.13!

Well, they certainly seem to be nested, here’s the worst case scenario of wasted shadowmap / distribution, when the light is directly shining down 90 degrees, looking at the horizon and then using the freeze camera command and show frustums along with visualising the whole scene shadowmap, it has a lot of overlap considering it should be spreading them out further.


Those cascade distributions are totally correct, 90 fov and they are all nested inside (that is froze from when I looked at the horizon while the dir light is 90 degrees pointing down) and it’s wasting so much shadowmap space by nesting them like that, they should barely overlap just so the transition area is covered.


Wasteful, so I hope it’ll be fixed, pretty please :slight_smile:

Changing the maximum distance doesn’t change the distribution either, it just scales the closest cascade up.


It’s pretty bad when you really dig into it, because it doesn’t work how it should at all… Why at 20K units are cascades being clamped? The distribution exponent doesn’t work how it should, at least, I would think that it should affect the cascade distribution in the range, not relative to distance from the camera like it seems to at the moment. When the distance is below the magic number which is around 5000, where the blue cascade stops growing past that distance, the whole distribution is broken.

Those orthographic boxes shouldn’t be nested like they are right now, Crytek said about wasting texel space to afford cached CSM, but this method right now is wasting the most.


was froze with 36 fov, it looks like it’s actually working in that photo how it’s meant to, so basically, someone did something wrong because there’s no reason it shouldn’t spread them further like that at 90 fov, no reason at all really…

Not really a bug. Unable to build 4.13 from the source file as AutomationScripts.Automation are missing references to GUBP.Automation, Localization.Automation and OneSkyLocalization.Automation.
The preview builds have these references in the DotNET folder. I’m going to delete the fold and try again - perhaps the download screwed up?

In the static mesh editor, the highlight material checkbox does not work on Mac OS X (i.e. the part of the mesh with the corresponding material is not highlighted). Shall I enter a answer hub, or this has been already reported?
Thanks!

sketchup fbx import to UE 4.13 not make auto Generate lightmap UVs are Issues or only me?

thank you

[= ;588961]
You should see a tab in the Static Mesh Editor next to the Details Panel that allows you to set all the scene’s settings. If you don’t see it, you can go to Window > Preview Scene Settings to enable it.
[/]

thank you …

[=rranon;589109]
In the static mesh editor, the highlight material checkbox does not work on Mac OS X (i.e. the part of the mesh with the corresponding material is not highlighted). Shall I enter a answer hub, or this has been already reported?
Thanks!
[/]

It’s also not working for me, windows 10, laptop gpu though - gtx 765m.

Please take a look at this issue:ios metal rendering issue in 4.13 - Rendering - Epic Developer Community Forums [MENTION=9] Ellis[/MENTION]
Thanks a lot!

Hello. Thank you for the new version.
Why don’t you do compatibility OnlineSubsystemNull with OnlineSubsystemGooglePlay?

Procedural Mesh lost his collision in packaged project if manually added into the level, it not happen if you spawn it in the level, i will make a bug report as soon as possible.

Good Job guys :slight_smile: :o

[= Flint;588770]
Hey ,

I have reproduced the issue and have entered a bug report, which you can track here: Unreal Engine Issues and Bug Tracker (UE-35512)

Thank you for your report.
[/]

Well thank you very much for that! I fav’ed the Jira just in case I come across other things :slight_smile:

The 4.13 looks really stable, I had lots of blueprint compilation crashes in 4.12.5 (because of how I coded, circular dependencies and stuff) and none of them occur in 4.13. I’m looking forward modifying a core Structure used in different places of the code to see if it reacts as bad as it was reacting before.

Anyone else notice an increase in ShadowDepth processing in UE4.13? I’ve shared my findings hereanswers.unrealengine.com/questions/481832/ue-413-shadow-maps-regression.html

[=ZioYuri78;589247]
Procedural Mesh lost his collision in packaged project if manually added into the level, it not happen if you spawn it in the level, i will make a bug report as soon as possible.
[/]

Bug report done.