Make it easier to use WWISE in a project centric approach

[srikappa-amzn]

In order to get audio working for my game, I had to follow a series of steps and hard code project paths in some places. I think those steps are only needed when we use project centric approach. And audio wouldn't work for my teammate because we hardcoded project paths. He had to hardcode his project path again.

For project centric approach, we should make using wwise much easier than this.

[amzn-phist]

I know exactly what you're talking about, we worked through the setup together.

Not sure what the best approach is. The problem that needs to be solved is this:

• The Wwise commandlet is of the form: python <some_script.py> <params...>. With old engine-centric workflow where projects were sub-paths of the engine root, we knew the location of python.cmd and the python script, because they could be reliably located relative to the project.
• With new project-centric workflows where the project is detached from the engine, we need a solution that finds python and the script, but is also not relying upon absolute paths. The commandlet is checked into source control (and attached to the Wwise project), so it needs to work for multiple users with different project & engine paths.

The Wwise commandlets are able to see environment variables, but I don't think that's the best approach here. One potential option could be to have the existing setup script generate and copy the commandlet and script to the project path. Also might be able to call python instead of having to find the engine's python.cmd.

[rainbj]

hi @amzn-phist It sound like UX work on this ticket but I'm unsure based on the description. Can you give a bit more details so we can determine level of effort

[amzn-phist]

@rainbj No UX work is needed on this, it's primarily going to require some scripting solution. I'll remove the sig/ui-ux label.