NetworkingHololens in the application name and I'm trying to use the SharingService to manipulate a cube over the network.
When I run other apps(without the networking capability), it runs fine on the HoloLens emulator, but when I run this or any other networking app, the following error shows up after the "Made with Unity", and just becomes black.
Updated Logs
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: Microsoft RemoteFX Graphics Device - WDDM (ID=0x2c1)
Vendor: Microsoft
VRAM: 639 MB
Initialize engine version: 2017.1.1f1 (5d30cf096e79)
'Cube HoloLens Networking.exe' (CoreCLR: CoreCLR_UWP_Domain): Loaded 'C:\Data\Users\DefaultAccount\AppData\Local\DevelopmentFiles\CubeHoloLensNetworkingVS.Debug_x86.Abhijit\UnityEngineProxy.dll'. Cannot find or open the PDB file.
'Cube HoloLens Networking.exe' (CoreCLR: CoreCLR_UWP_Domain): Loaded 'C:\Data\Users\DefaultAccount\AppData\Local\DevelopmentFiles\CubeHoloLensNetworkingVS.Debug_x86.Abhijit\System.Linq.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Cube HoloLens Networking.exe' (CoreCLR: CoreCLR_UWP_Domain): Loaded 'C:\Data\Users\DefaultAccount\AppData\Local\DevelopmentFiles\CubeHoloLensNetworkingVS.Debug_x86.Abhijit\System.Reflection.Extensions.dll'. Module was built without symbols.
The following GlobalManagers were stripped from the build (Either because they're not used or not supported on this platform):
NetworkManager
MasterServerInterface
ClusterInputManager
CrashReportManager
If your machine has multiple graphics adapters, Unity may have created a WindowContext on the wrong adapter. If you experience a black screen when playing, please restart the Editor.
(Filename: C:/buildslave/unity/build/Runtime/VR/VRDevice.cpp Line: 219)
d3d11: failed to create buffer (target 0x1 mode 2 size 4194304) [0x887A0005]
d3d11: attempt to lock null buffer
Assertion failed on expression: 'm_Buffer != NULL'
(Filename: C:\buildslave\unity\build\Runtime/GfxDevice/d3d11/BufferD3D11.cpp Line: 174)
The program '[740] Cube HoloLens Networking.exe' has exited with code -1073741819 (0xc0000005) 'Access violation'.
I was hoping anyone could help me out with this.
Related
during initialisation of my D3D stuff, I call the following function:
hr = D3D11CreateDevice(nullptr,gDriverTypes[DriverTypeIndex],nullptr,
#ifdef _DEBUG
D3D11_CREATE_DEVICE_DEBUG,
#else
0,
#endif
gFeatureLevels,gNumFeatureLevels,D3D11_SDK_VERSION,&lDevice,&lFeatureLevel,&lImmediateContext);
In debug build, to get additional information about possible D3D errors, I set the flag D3D11_CREATE_DEVICE_DEBUG. Without any further actions this lets my application terminate immediately.
So according to Use D3D11 debug layer with VS2013 on Windows 10 I tried to install the required D3D-debug stuff by calling
Dism /online /add-capability /capabilityname:Tools.Graphics.DirectX~~~~0.0.1.0
within a admin-console on latest windows 10. Unfortunately this fails with
Deployment Image Servicing and Management tool
Version: 10.0.18362.1316
Image Version: 10.0.18363.1316
[==========================100.0%==========================]
Error: 0x8024500c
DISM failed. No operation was performed.
The log file is also not very helpful, it contains loads of error messages and error codes one can't understand easily.
So...are there alternative ways to get the D3D debug stuff that is required to work with D3D11_CREATE_DEVICE_DEBUG enabled?
Thanks :-)
For Windows 10, support for the Direct3D 11 and Direct3D 12 "Debug Device" is only available with the "Graphics Tools" Windows optional feature enabled.
The HRESULT of 0x8024500c indicates you have some problem with Windows Update on your system. It's WU_E_REDIRECTOR_CONNECT_POLICY.
Most likely your PC is on a corporate network using WSUS. You need to ask the IT admins to allow this Windows optional feature.
I am a newbie to ARCore development with Sceneform using Android Studio. As I don't have any compatible device, I am trying to test the development using the built-in emulator but the rear camera (set to Virtualscene) seems to be buggy as the scene will frequently distorted.
Tried with several different ARCore sample programs, and emulated different android devices (Pixel 2 XL API 28, Pixel 2 XL API 27 & Pixel API 27), but still facing the same problem. OpenGL has been set to renderer maximum (Up to 3.1).
I suspect it is due to hardware limitation, but is there any way that I can solve this problem? Thanks.
My laptop specs:
OS: Windows 10 Home
CPU: Intel Core i5-7200U # 2.5GHz
RAM: 8.0GB DDR4
GPU: Intel HD Graphics 620
Sample of the emulator bug:
Logcat snippet:
08-09 03:22:28.521 5289-5289/com.google.ar.sceneform.samples.solarsystem E/eglCodecCommon: glUtilsParamSize: unknow param 0x00008919
08-09 03:22:28.593 5289-5289/com.google.ar.sceneform.samples.solarsystem W/native: cameras.cc:526 Metadata for GL texture didn't arrive. camera_id=0 status=generic::deadline_exceeded: Timed out waiting for metadata.
08-09 03:22:28.596 5289-5335/com.google.ar.sceneform.samples.solarsystem E/native: camera_image_stream.cc:115 Failed to extract the metadata or correct the timestamp, status=generic::deadline_exceeded: Timed out waiting for metadata.
08-09 03:22:28.600 5289-5289/com.google.ar.sceneform.samples.solarsystem E/eglCodecCommon: glUtilsParamSize: unknow param 0x00008919
08-09 03:22:28.602 5289-5289/com.google.ar.sceneform.samples.solarsystem E/eglCodecCommon: glUtilsParamSize: unknow param 0x00008919
08-09 03:22:28.630 5289-5335/com.google.ar.sceneform.samples.solarsystem E/native: camera_image_stream.cc:115 Failed to extract the metadata or correct the timestamp, status=generic::deadline_exceeded: Timed out waiting for metadata.
08-09 03:22:28.657 5289-5289/com.google.ar.sceneform.samples.solarsystem W/native: cameras.cc:526 Metadata for GL texture didn't arrive. camera_id=0 status=generic::deadline_exceeded: Timed out waiting for metadata.
08-09 03:22:28.662 5289-5289/com.google.ar.sceneform.samples.solarsystem E/eglCodecCommon: glUtilsParamSize: unknow param 0x00008919
For your CPU you can see here that need a support for Intel VT-x, maybe is disable. You can see on this post how to enable.
Other option is maybe let the emulator use more RAM.
Tools > Android > AVD Manager
Click in a pen to edit your AVD and in the new dialog click on Show Advanced Settings
I am trying to deploy a Windows 10 app to a Lumia 635 running 10.0.10586.11 and I get this error:
Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device 'DEVICE GUID'.': SEHException - External component has thrown an exception.
Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found. The data necessary to complete this operation is not yet available.
Unlike most, I am capable of deploying to an Emulator, just not the physical device. Based on this question: Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found
I verified that Windows Phone 8.1 is installed, and ensured that the latest SDK is installed, so neither of those were solutions. I am able to deploy to physical hardware for desktop/tablet mode, but no go on the Lumia 635.
Installing the latest mobile emulator preview fixed the deployment issue for me.
https://dev.windows.com/en-us/downloads/windows-10-developer-preview
As it turns out, it was an issue with the installation of Windows 10 Mobile on my device. After a reset the deployment works great, and I have deployed dozens of apps to the device.
1/3 Try registry patch
How to develop windows 10 uwp on real device (mobile)?
2/3 Update your UWP Tools. Latest one is '1.2', included at VS2015 Update1 RC. It's go-live. (But RTM ver will be released at 30 Nov.)
https://www.visualstudio.com/en-us/news/vs2015-update1-vs.aspx
3/3 This is just a workaround ... you can use "DevicePortal" to deploy your .appx package to your mobile device directly without Visual Studio.
Following blog is written in Japanese but the screenshots may helps you.
http://ddlgjp.blogspot.jp/2015/10/deviceportal-uwp-app-win10-mobile.html
I am running Redhawk 1.10.2 on a CentOS 6.6 (2.6.32-504) machine. I am getting the following error.
Failed to create application: test_051_103150756 Unable to make connection DDC0 in waveform 'test_051_103150756_1'; error occurred near line:2995 in file:ApplicationFactory_impl.cpp;
IDL:CF/ApplicationFactory/CreateApplicationError:1.0
This waveform was running on a CentOS 6.5 (2.6.32-71) machine with Redhawk 1.10.0. The waveform only has a DataConverter in it.
As pwolfram suggested, it looks as though you had a connection named DDC0. Check your SAD.xml file to see how this connection is defined and it may shed light on the solution. You can also increase the debug level of the domain and device manager to view how the waveform is being brought up and connections made. If you are using the IDE to launch the domain & device manager, use the log level combo boxes to increase the log level. If you are launching via the command line, use the -debug command line option. In the IDE, these debug statements show up in the IDE's console view for the domain and device manager processes.
I have an issue with a few Windows CE 5.0 devices which are crashing virtually as soon as they resume from standby (suspend). I have condensed the issue down to about 15 lines of C++ to simply get wxWidgets to display a message box, and the problem will hit if I:
Start the app
Suspend the device (by this I mean pressing the red power button briefly)
Resume the device
Pressing the OK button in the message box title.
BOOM
This problem manifested itself in many other ways before I condensed it down - on loading a bitmap, on scanning a barcode, all once it has been suspended, then resumed.
I am using the following:
Windows CE 5.0 Professional (Motorola MC3090 device)
(also WM 6.5 (MC55), CE 6.0 (MC3190))
Visual Studio 2005 SP2
wxWidgets 2.8.10
Microsoft Windows CE 5.0 Standard SDK
The actual error that is displayed is sporadic and wide ranging, but mostly an access violation, typically near the start address of a function call (discovered this by suspending the device, resuming then attaching VS debugger on the device). Having done extensive homework on this, I've read some suggestions it may be some kind of heap corruption occurring. As long as the app doesn't suspend, it always works correctly across all correct combinations of SDKs and devices.
I have also tried the following SDKs:
MS Pocket PC 2003 SDK
Symbol Platform SDK for MC3000c50a
Symbol Platform SDK for MC3000c50b
Windows Mobile 5.0 SDK
Windows Mobile 6.0 SDK
I have tested the following devices:
MC3090 (Windows CE 5.0) - Same Problem
MC55 (Windows Mobile 6.5) - Same Problem
MC3190 (Windows CE 6.0) - Problem does not occur on this device with StandardSDK build
I have played excessively with the setup of wxWidgets, always making sure that I link the app with the correct corresponding SDK.
Here is the code that causes this problem:
#include "wx/wxprec.h"
class Application : public wxApp {
public:
virtual bool OnInit();
};
bool Application::OnInit() {
wxMessageBox(L"Test");
return true;
}
IMPLEMENT_APP(Application)
Anyone with some advice out there, I would be eternally grateful! Please also let me know if I have left out any important details.
Are you running the application from an SD card? The MC3090, at least, and I think also the MC55, conform by default to the Windows CE standard for add-on buses (defined originally for PCMCIA cards): that when you suspend and resume the device, all buses are reset. This causes the card to momentarily disappear, and all handles to files opened on the card to be invalidated. This is actually so that the device can deal with the user changing the card while the device is suspended.
Windows CE is a demand-paged operating system. Your program is not all loaded into RAM when started: instead, pages are only loaded from the executable and DLLs as they are referenced by the program. Any read-only or unmodified pages can be discarded by the OS at any time, because it can re-read them from the original program file (this is why your program file can't be overwritten if the program is running). If the handle to the EXE or DLL is invalidated, and you reference a page that hasn't been loaded (or has been discarded), the OS page fault handler can't read the page and it generates an Access Violation exception.
For the MC3090, you can configure the SD card driver not to 'remove' the card on resuming from sleep. See Symbol's KB article MC30xx CE5.0 - Application aborting randomly when using SD Card for details. I can't find details of how to do this on the MC55. On the MC70, there was an 'SDSwitch' applet in the System control panel, whose main function was to switch between memory card and SDIO mode, but which also had a checkbox to control this option. Some other devices have had a 'sealed SD slot' CAB file in the \Windows folder - I seem to recall this on the MC65 or ES400.