Hi, great tutorial but I am facing an issue where my sounds work for static meshes but are not working for my landscape material, I changed the phys material in layer info but it still doesn't work. I am using open land landscape material.
One step i missed was going into the physical material and make sure you put the surface type to what it needs to be. Not sure if it was in the video but i didn't see it.
I was curious, is there any specific advantage in putting the notify's code in the character's ABP, over creating a notify bp that houses the code within itself?
the character ABP inherits the animations, so you can call the notifies easily in this ABP... Also the line trace is easy to access from there, because you usually cast to the character from there anyway. An unique BP for this just isn't necessary. :)
none of this should be done in the ABP. the notify should just pass the message along. probably better off making a notifier interface or something. it's pretty bad design to start throwing physics and audio into the animation blueprint. besides, imagine if you want to change the footstep sounds based on the kind of footwear your character is wearing, how fast they're moving, crouched vs running etc etc etc. better to do that on the character BP rather than in the ABP
Well this is not really good tutorial bacouse this system wont funtion with meshes that got more than one material (and probably there are begginers here that cant create only one texture per mesh) and also wont funtion with landscapes. I invented system that I have never seen online and it is based on mesh tags. Basicaly when I add mesh to my world and it can be even landscape or spline i add tag of sound I want to play and my linetrace then checks for the tag and change the sound. It also changes sounds while running.
@@N090UGY didnt say not to use the Raycast. In this case the surfacetype switch branching off into so many calls for sound cues is terrible. set the surfacetype as an integer parameter and call the change in the sound cue file itself. you could set many different parameters, all in one sound cue, instead of making so much extra work and different sound cue files and so many calls for no reason. Experienced users know, I tend to forget this video is aimed at beginners.
@@Digital33Studios wow, condescending comment and all. Using an int is a terrible idea. A pro would use a map, mapping the EPhysicalSurface to a Sound Cue.