Categories
Me Myself&I

Coding: the horror

In my adventures with Unity.

So, I have a game prototype and I want people to try it. For that it needs to be exported as an executable. It’s all done by Unity, two buttons to press like exporting a jpg in Photoshop. But for some reason, no sound in my game build despite the fact that it works nicely in the editor. Very annoying in a game with a big focus on audio.

Everything’s all right, no warning anywhere. I start searching and the solution doesn’t come out straight, no one is really having this problem.

I know I’m using weird stuff (plugged Fmod Ex through Squaretangle .NET wrapper) and I know it’s because of that because when I try to build another game with sound triggered by Unity built-in audio system, it works.

Fuck. And this is where making games is about folder agency, what this file is used for and so on. Dumb work.

In audio and video software we usually have this cool tool that basically says “clean up all the unused files and references and consolidate my project, computer slave”. There’s nothing like that in Unity. It’s SO useful, especially with dozens of folders and files.

I finally found the answer through forums and my knowledge, trying out copy/pasting .dll. Would it be hard to have Unity builds made on the basis of “everything that is used in the editor to run the game is exported, regardless of where it’s at on the machine”?

How come we still need to do that kind of micro-management shit in 2013 with game tools, it’s beyond me.


Real talk. *cries*

Leave a Reply

Your email address will not be published.