Closed timforever closed 7 years ago
Hi Tim,
Dissonance doesn't currently support dedicated server mode - the server must also be a client. The null reference here is the server system looking for the local client and failing to find it.
Someone else actually requested this feature just a couple of days ago and we have it implemented (it won't be in the next release, but it should be in the one after that). If you send me your invoice number (martin@placeholder-software.co.uk) I can send you a patched version of Dissonance including the dedicated server support.
Hi Tim. I've just sent out the version which includes dedicated server support to the testing group (which I believe you're included in).
For anyone else coming across this issue feel free to contact me with your invoice number to get that version, or just wait for the release on the Unity store (planned for 1 week from now).
Dissonance 1.0.6 just went live on the asset store. That includes the dedicated server support requested (currently HLAPI/LLAPI only) so I'll close this issue - of course feel free to re-open it if things aren't satisfactory.
Context
Error(s) occur when using the HLAPI in Server Only mode.
Expected Behavior
A user should be able to start Dissonance using HLAPI in Server Only mode without seeing error in the Unity Console, and then be able to use voice chat in connecting clients as would be normally expected.
Actual Behavior
After a client connects, a new but similar error appears:
Steps to Reproduce
This can be reproduced by running the DissonanceHlapiDemo scene from the Dissonance package from the Unity store, and using the Server Only mode.
Your Environment
Dissonance version used: v1.0.4
Unity version: 5.5.2f1 Pro
Editor Operating System and version: Microsoft Windows 10 Pro 10.0.14393 (x64)