Audiokinetic의 커뮤니티 Q&A는 사용자가 Wwise와 Strata 커뮤니티 내에서 서로 질문과 답변을 하는 포럼입니다. Audiokinetic의 기술 지원팀에게 문의하고 싶으신 경우 지원 티켓 페이지를 사용해주세요.

Unity Integration process feedback/problems

+1 투표
Hi, I'm a new user who wants to try out Wwise, but I'm left bewildered right away by the integration process:

- Every single file in my project needs to be made writable? What exactly is the integration process doing to all of them? The documentation does not explain this. Why not selectively target files that it needs to alter, and tell us which of those are read-only and need to be changed?

- After making every single file writable and successfully integrating, my project is riddled with compilation errors. For some reason, several DLL files and/or scripts in my project were broken, I think by Unity's API Updater during or right after integration, and I have to reimport them to fix them. After that, I think everything works, but I can't understand why this would happen?

- After successful integration, I open Unity and find that my editor layout has been reset to default. Fortunately I can restore it, but this is obnoxious. Just open the Picker window please and don't reset my whole layout.

- If it "fails" for some reason, it simply errors in the Wwise Launcher, saying you must revert to a backup? But then I discovered all I have to do is delete the temp file it creates in the project root, and I can tell it to try again. This is frustrating, the documentation's "Changes made to your unity project" section doesn't seem to suggest the integration process would need to be so fragile.

I can tell this really aims to be a professional product, but I'm left confused by how poor the current automatic integration is. I hope this was somewhat constructive... Are others experiencing these issues too and/or is AudioKinetic still working on improving the integration process? (I guess this new system isn't very mature yet?)

Thanks.
문의 2017 3월 8 General Discussion Kyle W. (290 포인트) 로 부터

Please sign-in or register to answer this question.

...