Sound Manager and the integration of Wwise

     The problem I faced during this week was the integration of the audio library through Wwise. This problem arose because I had never worked in the Wwise SDK before, and had to integrate it within both the CMake lists and the code itself. This would cause a litany of issues related to linker errors if the library and dlls are not imported properly. In addition, the system would then need to initialize the audio library, which requires me to go through the setup code for Wwise's sound engine. This and more required research more than anything, and as a result was time consuming.

    The solution was simply more research. Having time on my side (at least during this time of development) along with documentation that Audiokinetic provided with the Wwise SDK made the integration of that library relatively smooth. The library itself has many features that make it relatively simple to work with the sounds. Loading the banks properly is a relatively simple operation, provided they are in the proper location, and playing a sound through them simply requires that the event name or the event id be known beforehand so that it can be properly called by the engine for each sound. Being able to queue up sounds as well is handy for the engine to be able to focus on other tasks while Wwise actually works with the sounds and plays them for you, including audio mixing for distance.

Comments

Post a Comment

Popular posts from this blog

Adding assets to every enemy -- Owen Meyers

Image
      As with every game, it is very important to have assets to denote which enemy is which. Being able to tell at a glance what enemy you are encountering before receiving a face full of buckshot is incredibly important. The issue for Project [REDACTED] is that we didn't have any artists working full time to deliver assets for the enemies. Thus, it fell upon me, the designer of the asset pipeline, to acquire assets for every enemy. This led to having to fix models and integrate animations, with each problem being subtly different.     Take, for example, the shotgunner model. His original model was designed for an OpenGL renderer, and was flipped 180 degrees for that very reason. In addition to this, he was also placed halfway in the ground, likely due to something required for that game's collision to function. Fixing this model to function for our renderer required that it be re-rigged and most of the animations acquired from Mixamo. With the help of Kris, and several hours
Read more

Sphere to AABB collision

       I had a problem today when trying to detect sphere to AABB collision. For some reason the collision check that I made was never turning true even though I could clearly see the sphere hitting the AABB. This was a big problem as we needed this collision to detect whether any entities are hitting walls.     I discovered that the problem with this bug was that I was improperly getting the closest point in the AABB to the sphere. The way I fixed this problem this problem was by getting the max vertex that the circle center could be and using that to get the closest point on the AABB to then determine the minimum vertex between the sphere's max vertex and the max of the AABB.  Once I found this point, I could properly compare the distance of that point to the center of the sphere. This solution will allow detection between walls and any sphere collider such as the player collider, and enemy collider. This is very important to make sure they both stay within the level bounds.
Read more