In my application I want to read some depth frames over a span of ca. 5 seconds from the kinect v2 to do some volume measurement and reconstruction of moving objects. However, the stream keeps freezing every few seconds rendering the data useless in the worst case.
This behavior can also be observed when running the wpf depth basics example.
Strangely enough - when using kinect studio the issue is not only non existent but when the studio runs even if not connected to the kinect, the problem is fixed for the example application as well.
So obviously there is no problem with the hardware (as it works just fine when running the studio) but perhaps some kind of driver or service issue.
The same is the case when running the c++ version of the sample. The sample alone runs fine and while it is running the c# version runs fine, too.
Do you have any ideas?
If your project's platform target is 'Any CPU' then set it to 'x64'. To do so
Right Click on the project (not the solution) and select properties.
Select 'Build' from the left manu.
Change 'Platform target' to 'x64'.
Press 'Ctrl+S' to save the configuration.
Run the program.
Hope it helps.
Note: My answer is based on Visual Studio 2013.
Related
I deploy my HoloLens 2 in Visual Studio through Release, ARM64, and Device. If I use the Release Machine instead of the Device, I got an error.
My desktop doesn't have the same Wi-Fi as my HoloLens. I can't connect my desktop and HoloLens to the same Wi-Fi.
My deploy is succeeded after I use the Device. My project Icon is shown in the HoloLens 2. But after I open the Icon, I can't see anything.
Please help me to find the solution. I spend a lot of time on this problem.
Maybe my explanation of Remote Machine and Device gave you some misunderstanding. I'm sorry about that. Remote Machine + WIFI and Device + USB are both officially recommended deployment methods. Since you have successfully deployed through Device, please continue to use it. If you are still a little confused about deployment you can publish a new thread.
It seems the main issue here is that when you run the deployed project, you cannot see any object. I recommend you try Remote Debugging(https://learn.microsoft.com/en-ca/windows/mixed-reality/develop/unity/preview-and-debug-your-app?tabs=openxr) in the Unity editor, which allows you to quickly preview and debug your project without deployment, and it can also be connected via USB. You can also use the official sample to Remote Debugging or deploy directly. Also, it's important to note that before you build your project in Unity, you need to add the scene to Build Settings->Scenes in Build.
Finally, I found the solution to my problem. Before I used the unity 2020.3.9. Now I changed the version to 2020.3.4. Now I can deploy and see the game objects in my hololens 2.
I had the same issue before. In the unity editor, I can see my models normally. But the models were not shown in Hololens, or only by one eye. The reason was that the models use the standard shader of Unity. After I applied the Mixed Reality Toolkit/ Standard Shaders, every model was shown.
I need some help figuring out what the problem is.
I have a brand new installation of VS2017 fully updated
When I run my app in debug mode it works, when I run the app in release mode it would just hung at the splash screen, I tried to check the device log but I can only see IlligalStateException
I changed the Java Heap to 1G, but it did not solve the problem
I am upgraded to Xamarin.Forms 3.0 and I am compiling using Android 8.1, that did not solve the problem (also tried to lower the version)
I set the Linking to None, that only increased the app size and did not solve the problem
When I uncheck the "Bundle assemblies into native code" it then works but I have always been compiling my apps with this. (and it works in debug mode)
I checked the version of the NDK it is currently set to "C:\ProgramData\Microsoft\AndroidNDK64\android-ndk-r15c" Not sure if the version is incorrect that I am using since this is also a new laptop (my other laptop was stolen where everything compiled and worked perfectly)
It also seem that the Device Log is lagging and doesn't want to filter. Device Monitor seems to be crashing aswell.
I just tried to upgrade to nds-16 but that didn't work aswell.
For now I am compiling without it but I would like to compile with it again
Try first uninstall your app:
adb uninstall <your.package.name>
Maybe you use a different keystore for the signing.
You can set the log verbosity to diagnostic in order that you see the problem:
Tools/Options/Xamarin/Xamarin Diagnostic Output verbosity
Tools/Options/Projects and Solutions/Build and Run/ output verbosity
When I open a sample Blinky application in Visual Studio, compile and run it, it gets automatically deployed to the target configured WindowsIoT device. After that, on Windows 10 machine where I compile it, the application binaries are located in the bin sub-folder of the project folder as one would expect.
I would like to automate the deployment, so that I could run deployment code
without Visual Studio, specify target device and the binaries location and it would deploy it. I cannot find any API that allows
to deploy apps to Windows IoT, how do I do that?
This shiny Windows IoT stuff is a new area, and there is not a lot of info available apart from the samples and the getting started page. Any pointers are appreciated.
Update: As noted in comments, once one start thinking of mass production, they will probably need to conciser ICD. This, is not, however the problem I'm trying to solve currently. I would like to figure out how I can provide Over-the-Air updates to my UWP application running on Raspberry Pi and Windows IoT. I also would you like to know how I can automate build / deployment in general, but that may be automatically solved if I have a proper OTA solution.
There is a set of instructions on how to do it, which can be found in the same github repo you are linking in your question, but in a different folder. Note, that you need an appx for these instructions to work, and it's not created by the solution build by default.
This page provide (non IoT specific) instructions on using VS to build the appx. And this blog post talks about the command line tool that can be used for making appx.
Note, that the last two links are also talking about publishing an application to app store, so you'll need to make some mental adjustments around that.
I've encountered a problem where part way through building a solution, VS 2010 becomes locked and never returns. If I build individual projects one by one it works so the building of project is working. The solution contains XNA projects for various platforms and winforms libraries. This did work up until a point but have found no explanation for the sudden freezing.
I've uninstalled all of my plugins to see if that helps but no difference.
In task manager, VS2010 is busy doing something as it's using CPU and consuming memory >1GB.
It took a significant amount of time/removed music to sort it.
I have a program that I built that reads and writes files. I built it in Release mode, then tried to run the exe on Win7. At first, with troubleshooting on, Windows simply told me the application closed and it was looking for a solution. After a few seconds, the dialog would disappear and show nothing more.
So with some significant effort I got the debugger attached to the process, but it was only showing me disassembly, which tells me that the error taking place wasn't in my application code, but in the framework somewhere.
The strange thing is that when I let the debugger attach, then press "stop" in VS, and exit the debugger, the program actually runs at that point!
So now I'm stumped. I have an application that builds, that seems to be having a permission error when I run it, but if I let the debugger attach then close it, it runs, and there's no Exception to really look at.
How I troubleshoot this issue?
Edit: Responding to Merlyn:
It's a custom app written from scratch in c#. The only dependency it has outside of core .NET namespaces is the Ionic.Zip DLL.
Visual Studio 2008 (Writing in C# 3.5)
Windows 7 - Home Premium, v6.1 build 7600
CPU - x64 quad core
CPU are you compiling under: Any CPU
I haven't tried it on another machine or a different version of VS.
Edit: I was able to try the compiled version on another win7 computer, and it worked without issue, so it looks like a security (?) issue on my computer only.
Try it in the debugger with Just My Code disabled and Native Code enabled, then check the call stack.
Also, what happens if you run it directly in Visual Studio?
Uncheck Enable Visual Studio Hosting Process in Project Properties and see whether it still works in VS.
I'd suggest sending the issue to Microsoft support. Especially with the data given here, you will have an easy time convincing them it's their problem. You might need an MSDN subscription for that.