วีดีโอ

@@brassbgeek thank you!

I am glad you enjoyed it! I will keep doing these as long as I can :-)

It is really hard! And even what I do in this video doesnt quite cut it. Its good! But not on the level you mention. Keep an eye on this space I plan on starting a new tutorial series using the current renditions of wwise and unreal. Maybe we can get to that point together :-)

haha thanks! I am really glad this video has helped you.

Unfortunately all of my experience has been within the engine. I tried packaging the game once during a game jam and also ended up with no sound. I looked into it a little bit at that time and never found any answers. I have been in school since then and haven't needed to look into it further haha. Sorry about that!

@@brassbgeek 😔

The switches are triggering based on the material that is set on the object in question. In order for a non-default sound to appear (at least the way I have it set up in my tutorials) you need to make sure the surface you are walking on has a material attached, and that material is linked to a surface type in Unreal, as well as a switch in Wwise. If you are using a blank mesh, the default sound will be used because when Unreal is looking at the surface you are walking on, it finds nothing, and so sets the sound to whatever your default is in Wwise. I hope that helps!

Wow you are right, finding C++ info for this is surprisingly difficult. You have probably already seen this but here is tue info to get started from the audiokinetic website: www.audiokinetic.com/library/edge/?source=UE4&id=using_cpp.html Sorry I couldnt find more for you!

@@brassbgeek Thanks for effort, but as we can see even Audiokinetic didn't care that much :D Well, if I can find some tutorial code around, written in C++, I can try to convert it by looking C# variations. I already asked the same question at Audiokinetic's QnA but no answer so far

Thank you!

Hi so that is an "Equal to" node. I think if you search for the nodes and just type "=" or "equals" you will find it. It is essentially comparing the two inputs and if they are equal to each other, than they return true.In the inputs I have the "get surface type" node which is a material based node that gets what type of surface you are referencing, and the other input is a variable that is listing the surface the character is already walking on. The output is going to a branch node (otherwise known as an "if statement"). If TRUE nothing happens, if FALSE (as in the surface types are different) it moves on to SET (surface type).

brassbgeek thank you so much!

Unreal has a few decent tutorials on their website that are good enough to at least get you familiar with the interface. Once you have that part down though, I feel their tutorials are very limited. Personally, I would just pick a VERY simple game type that you are interested in making, picking a project package that fits the bill (so the controls and camera are all set up for you already) and then diving right in. Programming using Unreal blueprints is pretty forgiving, the hardest part is knowing WHICH nodes to use (no need to worry about missing a colon anywhere). Once you run into something you aren't sure how to do, Google is your best friend. I have pretty much entirely put together the project in these tutorials using Google. Because of that, can get by pretty well without having to search for anything anymore because I learned how Unreal works by slowly building a project. Learning how Wwise works with Unreal is a little harder. There are some written tutorials available for it, but it requires a ton of experimentation to figure out everything else. That lack of easily-accessible information is why I put these tutorials together. Let me know if you have any other questions!

You are most welcome! I am glad it has been helpful to you :-)

Heya! This is done using reverb volumes in Unreal! Each volume has an aux bus attached to it, and you can essentially put these volumes right next to each other with different reverb buses attached to each so that when your character moves from one volume to another, the sounds they make will change. I go over this around the 10 minute mark in this video :-)

Hello again Pakiela! Nice to hear from you again. You should be able to use AKVolumes with things like the regular Wwise reverb and whatever other plugins come prebuilt in Wwise. Anything that is an additional plugin (like reflect) requires a special license. For textures I am unsure. Are you talking about acoustic textures? Or some other plugin? Acoustic textures will require the license because they are designed to work with Reflect I am pretty certain. If it is a plugin then you will need to check what the Audiokinetic website states about it.

@@brassbgeek Hi Tim Thanks for your reply :) Yes I am talking about acoustic textures and I just found out that yes I would need a licence since this are absorbtion reflection values used by the Early reflections generated when using Reflct.... so I am going to try now with blueprints and spline occlusion to workaround it :) thanks again and i hope you are fine-patrycja

I am glad you enjoyed the video. Thanks for watching!

I remember running into this problem before and it had to do with which switch node I used in Unreal! Took me forever to diagnose. Unreal has 2 different switchnodes you can use and you need to use the correct one (it should be telling you the switch name, not an array number whem the switch occurrs). I cant remember, but I believe one of my more recent videos covers this issue. If you co tinue to run into issues let me know and I will go through my videos to see what I did.

@@brassbgeek Thanks for the quick reply! I just tried the 3 different 'Get Switch' nodes but none of them are working. I'll look at the tutorial again to try to spot something wrong. It might be that since I just followed visually maybe I have a wrong node with the same name (similar to what you mentioned about the 'Get Switch' node) although, it's weird because it's printing the numbers as if it were actually doing something.

@@DiegoJPinto Here! Try this video here. If what is happening is what I think it is, I talk about it around the 20 minute mark of this video (after I made some mistakes) th-cam.com/video/0WVZPHFev2c/w-d-xo.html

​@@brassbgeek I just had time to get back into this, thanks a lot for your patience with the replies. I finally fixed it. It looks like the problem was the converter that was going from the 'Get Surface Type' into the 'Set Switch' node. (The small node that converts the green into pink :p) To fix it, I created a Print String node and and made a connection from the 'In String' input into the "Get Surface' node (instead of going from the "Get Surface' into the print String node, so I just dragged the connection backwards) This created a converter that looks exactly the same but when inspecting it the one that works it says 'Returns user friendly name of enumerator' instead of 'Convert a value type to string'. Very weird, and hopefully I explained it clearly for anyone who runs into the same issue. Feel free to ask any questions if it 's not clear. The only problem I have now with footsteps is that the first footstep of every switch plays the default sound before going in the the right material. Do you have a video on that? Stay safe during the pandemic and thanks again!

@@DiegoJPinto That last part kind of sounds like you have the switch occurring AFTER the footstep sound is played as opposed to before. But I can't be certain without seeing what is going on.

Thank you! I am glad you enjoyed the video :-)

I am glad this video was helpful for you! :-)

Hmm. I am unsure about why you would not be getting audio in the forst place (setting up switches is a little pain in the butt so it could be a number of things.) But for a radio station you may be able to go a little simpler than that. What you could do if you are so inclined is have an event for each radio station that "stops" each station and then "plays" the current one (along with a cool sound to go along with the dial/button/what have you.) When it comes to switches, if I remember correctly, the switch doesnt take effect until the current sound stops playing (which ia different from how states work). So if you used a switch in the middle of a song, the song would keep playing until it was done. If you are using a dial type thing for the radio you could also use rtpc's and a blend container which also opens up some fun sfx options for you.