Open damianperera opened 8 years ago
The Arial24.xml has a build action "ToolkitFont" that generates a .tkb file in the output folder. Do you have a Arial24.tkb file in the debug/Content or release/Content folder after building?
The output folder (HolographicStudio\bin\Debug) does not have a Content folder in it, and a Arial24.tkb file is not generated as well.
Hmm, are there any .tkb files generated in the obj/Debug/Content or object/Release/Content folders?
There isn't a Content folder inside obj/Debug. Please find attached a screenshot of the respective folder.
Ok, looks like the Custom Build Actions are not functioning. These build actions are defined in the SharpDX.Toolkit.targets file that is referenced in the HolographicStudio.csproj project file. Is your project file modified?
It seems so. Might I ask what version of Visual Studio are you using? And how exactly is this project configured to build? It is missing a VS solution file.
I am using Visual Studio 2015. Yes, I noticed that I did not add a solution. Probably because it also includes my version of the ProCamEnsembleCalibrationLib project (which basically contains is in the PR for RoomAliveTk) I just added the solution. :) You will have to manually refer it to the ProCamEnsembleCalibrationLib assembly it needs to use. To build that I am using my fork of the RoomAlive TK.
On Mon, Oct 31, 2016 at 12:59 PM, Damian Perera notifications@github.com wrote:
It seems so. Might I ask what version of Visual Studio are you using? And how exactly is this project configured to build? It is missing a VS solution file.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rolandsmeenk/HolographicStudio/issues/1#issuecomment-257276228, or mute the thread https://github.com/notifications/unsubscribe-auth/AAdUPFwZ9NY-7gVZCQo1bgI-3JhZsH_8ks5q5dgYgaJpZM4KjDvC .
An AssetNotFoundExecption is thrown by the SharpDX.Toolkit.dll for the Arial24 font that is loaded in the TweakableManager (line 167).
The Content folder and the Arial24.xml file is present in the Project Structure, however a Arial24.bmp file is not created during the build process, which might be the reason the Toolkit throws the exception.
Find below the output from the Debug process.