VulcanTechnologies
Vague Readme file...
When the readme says "Find the DLLs you just build: Look in the output window" this does not help without the names of the DLL files. There's a LOT in the output window. Are you talking about "Assembly-CSharp.dll"? I see two of those. Kind of weird you'd name them THAT, but OK. I'm not feeling so good about going forward at this point.
"Paste the plugin DLL into Unity" Should I be looking for a "plugin.dll"? I don't see that anywhere. I hope we're still talking about Assembly-CSharp.dll.
"Copy the plugin DLL from the output directory" None of the DLLs are in a directory named \output. Should they be? I've got one in \Release\ and one in \Release\Unprocessed. Is this normal?
I hope I don't set my laptop on fire, but I'll try going forward with "Assembly-CSharp.dll" and see how far I get.
By "two paths" do you mean "UnityWSAPlayerDir" (\MetroSupport\ in the Unity editor files) and "UnityProjectDir" (The folder where I saved the project)? Why don't you say that in the readme? MetroSupport only has one DLL in it called UnityEditor.WSA.Extensions.dll. Is that what I'm looking for? I don't see what I'm supposed to do with that one. Is it the plugin or the placeholder?
The UnityProjectDir has no DLLs in it, just an SLN and a CSPROJ file. It's also got 8 folders. If I search for DLLs in those folders, I find 301 DLLs. I trust you can see my confusion here. THREE of them are named "HoloLensCameraStream.dll". If I search for "plugin", two of those DLLs come up.
Anyone who could let me know whether HoloLensCameraStream.dll or HoloLensCameraStream.dll or Assembly-CSharp.dll is the right dll for the plugin, and which of the 301 dlls are the placeholder, any help would be appreciated.
open the sln and build then HoloLensCameraStream\Dummy Project\bin\Debug\HoloLensCameraStream.dll goes in assets/plugins D:_Active Projects\Hololens\HoloLensCameraStream-master\HoloLensCameraStream\Plugin Project\bin\Debug goes in assets/plugins/wsa
I haven't gotten much farther than that myself but after getting those in there there are some settings to change for each, the dummy you pasted into assets/plugins is the placeholder and should be the only thing that shows up once you've applied the right settings to it.
Somehow, Visual Studio may have put the right DLLs into the right folders for me? Or are there placeholders in the Unity package by default that I need to overwrite? The Readme should say these kinds of things... Or maybe there are gnomes helping me while my back is turned. Either way, I think I should now be able to code against the HoloLensCameraStream plugin... After I figure out how to import said namespace into my Unity scripts... Another thing the Readme file could get into in a bit more depth. Or at least provide a link to a helpful resource. Come on, Readme file. I know you can do better!
See, the scripts in the unity project already include the line "using HoloLensCameraStream;" which is what I imagine "import said namespace into your unity scripts" implies, yet Unity comes back with "The type or namespace name `HoloLensCameraStream' could not be found. Are you missing an assembly reference?" ... So I'm sure there's something more I have to do. Something that involves importing namespaces, or making assembly references or... I don't know. I'm not a mad scientist. I'm a JavaScript programmer. Working with Unity is just a project I'm doing for my day job. I'm sure they won't fire me... I hope... Well... :/
Thanks for the input. I plan on doing some version bumping and critical bug fixing, then I'll update the Readme and take your suggestions into account.
