Closed ro-anders closed 5 years ago
Follow up: If I change the name of my original project (which mains changing the top level folder name AND changing Product Name in Player Settings) it runs without crashing. I know Unity stores some settings in the Windows registry under the project name. My best guess is that one of those settings (wish I knew what it was) is causing it to crash. But a fresh set of settings is ok.
Would really feel more comfortable if I knew why it was just crashing, but can move forward with workaround of renaming project.
What is the name of the project which breaks things?
If you're interesting in narrowing it down Dissonance does all of it's serialization in one of two ways:
Assets/Plugins/Dissonance/Resources/VoiceSettings.asset
). This is pretty standard unity asset serialization.PlayerPrefs
, so it can be set in menus by an end user. I think all of these are located in Assets/Plugins/Dissonance/Core/Config/VoiceSettings.cs
(look for the block of constant strings at the top).You could easily copy VoiceSettings.cs
/Preferences.cs
into a new project with the broken name and see if any of that breaks.
Unfortunately I don't think there's anything we can do to fix this, even if we worked out the key that's breaking things we can't change it without breaking settings for every single end user of Dissonance. You should definitely report it to Unity though - submit the repro project you made including Dissonance as a bug report and references this issue. Hopefully they will fix it in 2019.2
.
The name wasn't anything special. "H2HAdventure". I'll look at those files, but those are under the project directory, so would be used regardless of the name. I was thinking of settings Unity stores outside of the project, though on more research, the number of settings they stick in the registry is extremely limited, and mostly to do with window size. So I am back to having no idea why it works when I rename it.
But, I was hoping maybe you'd have a "Oh yeah, we've seen this before" response. It does seem to be a Unity issue, and though I'm terrified it will crop up again, I don't think there's much more you can do.
Feel free to close the issue. Thanks.
I'll have a fiddle with this to see if I can reproduce+narrow it down and report something to Unity. Definitely not something we've seen before though!
Context
Added Dissonance to an existing Unity HLAPI project. Worked great on Mac (both in the editor and as a standalone application) and works on Windows in the editor, but when I run it as a standalone application it crashes a couple seconds after the NetworkManager connects. I created a brand new project from scratch on Windows following the Dissonance Quick Start docs and that worked. Standalone Windows application did not crash. I created a second brand new project again following the Dissonance Quick Start only this one had the same project name as my original project - that was the only difference. This one crashes.
Steps to Reproduce
Provide a detailed set of steps to reproduce the problem
Your Environment
Include as many relevant details about the environment you experienced the bug in
Dissonance version used: 6.3.0
Unity version: 2018.2.16f1
Editor Operating System and version: Windows 10 Home
Build Settings: Windows, x86_64 (everything else left as default)
The PC has no internal microphone, but a USB headset.
The logs are not much help
Those last lines are repeated about twenty times until the log suddenly ends.