Download

Unreal Engine 4.16 Preview

Will there be Auto-LOD for skeletal meshes as well? :slight_smile:

Hello Dan, thanks for the info, very useful! I’m very happy to see the new audio engine and the steam audio SDK in this release, I’ve been waiting eagerly for them :wink:

A couple of questions:

  • How can I double-check if the new Audio Engine is correctly enabled? I set the AudioDeviceModuleName parameter in WindowsEngine.ini the editor’s config folder (not the project one). Is this sufficient or shall I also use the command line parameter?
  • How do you tag the static meshes? Is it sufficient to add a component tag with the text “Phonon Geometry Component” in the details panel?
  • When I exported the scene the first time there was a dialog asking if I want to import the .obj file generate. Is this necessary? (I didn’t…)
  • How can I double-check if occlusion are working properly? In my case either the effect is too subtle (even using 100 as Occlusion Volume Attenuation I cannot tell any difference) or not working at all…
  • When I exit from the VR preview with the plugin enabled the editor crashes (only after tagging and exporting the scene as above, before it didn’t)
  • I cannot package a win64 executable with Steam Audio enabled, when I try I get the linking error below. Any idea how to fix this?

UnrealBuildTool: UELinkerFixups.cpp.obj : error LNK2019: unresolved external symbol “void __cdecl EmptyLinkFunctionForStaticInitializationPhonon(void)” (?EmptyLinkFunctionForStaticInitializationPhonon@@YAXXZ) referenced in function “void __cdecl UELinkerFixups(void)” (?UELinkerFixups@@YAXXZ)

Hello Dan, thanks for the info, very useful! I’m very happy to see the new audio engine and the steam audio SDK in this release, I’ve been waiting eagerly for them :wink:

A couple of questions:

  • How can I double-check if the new Audio Engine is correctly enabled? I set the AudioDeviceModuleName parameter in WindowsEngine.ini the editor’s config folder (not the project one). Is this sufficient or shall I also use the command line parameter?
  • How do you tag the static meshes? Is it sufficient to add a component tag with the text “Phonon Geometry Component” in the details panel?
  • When I exported the scene the first time there was a dialog asking if I want to import the .obj file generate. Is this necessary? (I didn’t…)
  • How can I double-check if occlusion are working properly? In my case either the effect is too subtle (even using 100 as Occlusion Volume Attenuation I cannot tell any difference) or not working at all…
  • When I exit from the VR preview with the plugin enabled the editor crashes (only after tagging and exporting the scene as above, before it didn’t)
  • I cannot package a win64 executable with Steam Audio enabled, when I try I get the linking error below. Any idea how to fix this?

UnrealBuildTool: UELinkerFixups.cpp.obj : error LNK2019: unresolved external symbol “void __cdecl EmptyLinkFunctionForStaticInitializationPhonon(void)” (?EmptyLinkFunctionForStaticInitializationPhonon@@YAXXZ) referenced in function “void __cdecl UELinkerFixups(void)” (?UELinkerFixups@@YAXXZ)

Is this going to have any mixed reality related improvements?

I mean, maybe not a full complete mixed reality solution, but a way to extract different cameras from the game to stream them…

Cheers and thanks!

I created a simple volumetric clouds from new material domain.
https://www.youtube.com/watch?v=hxyIvPdO9zQ&feature=youtu.be
I think that there is someway to make it better.

Niiiiice norulex :slight_smile:

We do want to do this, but we have not had a chance to tackle it yet I’m afraid.

As for the new Audio Engine, I noticed in Aaron’s demo at GDC he was using an envelope to drive materials.

Are there new Material Nodes available for this or is this purely a Blueprint/C++ implementation? I made a frequency spectrum analyzer in 4.15 with C++, but it relies on storing compressed bulk data of the original .wav as an asset. Being able to read from sound-cues in real time would be nice!

EDIT: Totally gonna abuse the volumetric particle feature… Can these special particles also be driven with textures?

What happens with simulated bones on skeletal mesh and translation? it seems to be completely crazy… (like in the very first version of the engine)

@dan.reynolds Im also quite interested in this. Hopefully there’s now an easy way to affect materials and other things using audio.

How do you take the full sound mix you hear and plug that into a light or material for effects?

Volumetric Fog is now supported.

Wohaa!

So am I understanding correctly that you need to tag meshes after they’ve been placed in the scene if you want them to occlude sound? Is there no way to have this be an automatic effect, or to assign the phonon geometry component tag to a mesh in the content browser instead of needing to apply it after they’ve been placed in the map?

This does seem like something that could be improved.
I had a bunch of crashes playing around with it yesterday which is understandable at this stage but there seemed to be a lot of extra setup compared to the oculus audio plugin.

I wonder what main differences are and why we should use one vs the other?

I’m afraid it’s hard to know without more details. Could you post a repro on Answer Hub? Thanks!

Sorry if i missed a post or something, but where can i see the new Synthesizer demonstrated and how to use it? Did it get covered on some stream?

There is a post earlier in this thread that is a starting point for now:

New volumetric lighting looks amazing. This is default project, default post-processing, and I switched the lights to fully dynamic. Can’t wait to see what experts do.

And here’s one with the lights in motion

Unfortunately i’m not able to reproduce it on the mannequin mesh, it seems to only appears with complex bones like hairs or chain…

Thanks for the info and fingers crossed you can get it working at least on the high end mobile VR devices for GearVR and Daydream support this version already (or perhaps a hotfix?) :slight_smile:

Great question! At the moment, the Phonon Plugin uses a component approach to tagging meshes, which means you would either have to add it to the mash once in the scene OR create a special BP actor of that mesh.

An optimization I found was to create a BP Actor with an invisible cube mesh and a Geometry Component, and then I was able to add this to a complex scene like a blocking volume–but for reflections.