Is it possible to activate the passthrough cameras from within a software (UE4)?
Hey guys! I want to know if I can activate the passthrough cameras manually from my software. I want to be able to let the user see through the cameras, while doing some setup for the software. Is there a way to activate the cameras, except the double press on the oculus button?936Views0likes1CommentPCVR SDK Does not have PCSDK_Logging.lib
I am trying to run the OculusWorldDemo in Visual Studio 2017. I set the mode to release and I run the program. However I says I am missing PCSDK_Logging.lib; I read some where that I need to run the PCSDK_Logging Visual Studio project to create this file. However, I cannot even open this because I receive an error that says that it cannot import the common.props file into the common.props file as it results in circular dependency. I want to manipulate the code in the OculusWorldDemo but I cannot run it from Visual Studio. How do I fix this?994Views1like2CommentsThe Windows SDK version 10.0.10586.0 was not found
I was following the PC SDK getting started guide, and progressed relatively smoothly until I tried to run the demos in the samples file Samples/Projects/Windows/VS2015/Samples.sln in Visual studio 2015. I encountered the error "The windows sdk version 10.0.10586.0 was not found." I followed the steps to correct it in the guide as well: I followed the instructions: edit Project Properties → General → Target Platform Version and changed the version to 10.0.15063.0, which was the windows 10 SDK on my computer. However, with this, the same exact error remained, "The windows sdk version 10.0.10586.0 was not found." So I went even farther, going into the Windows10SDKPaths.props file, and changed all 6 instances of 10.0.10586 to 10.0.15063. However, the same exact error popped up once again. I've tried closing Visual studio and restarting my laptop between steps, however, the result is still the same. Can you please advise on how to fix this? Thanks in advance.24KViews0likes8CommentsException thrown when calling ovr_CreateTextureSwapChainDX
Hello, My name is Johann and I've been using the OVR SDK with DX11 for 4 months now with an Oculus Rift CV1 and everything worked fine (TrackingState OK, rendering in textures OK). Until I switched to a new computer. Both are on Windows10 (the new one is Professional, the old one is Family). The samples (downloaded on the 02/02/2018) compile just fine. However when I launch OculusRoomTiny (DX11) in Debug Win32, Visual Studio (14 2015) breaks on the function ovr_CreateTextureSwapChainDX(). The error is : Exception thrown at 0x74E65F5D in OculusRoomTiny (DX11).exe: 0xC0000005: Access violation reading location 0x00000000. However when I click on "continue", the program runs just fine on the Oculus. Here is the call stack when the violation occurs : > ntdll.dll!_NtProtectVirtualMemory@20() Unknown KernelBase.dll!VirtualProtect() Unknown LibOVRRT32_1.dll!0f63b5a4() Unknown [Frames below may be incorrect and/or missing, no symbols loaded for LibOVRRT32_1.dll] LibOVRRT32_1.dll!0f63a3bb() Unknown LibOVRRT32_1.dll!0f64f371() Unknown LibOVRRT32_1.dll!ovr_ReleaseHapticsClip() + 2832 bytes Unknown d3d11.dll!NDXGI::CResource::QISurface(void *,struct _GUID const &,void * *,unsigned long) Unknown d3d11.dll!NOutermost::CDevice::CreateLayeredChild() Unknown Here is the full output of the program : 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Users\jnovak\Downloads\OculusSDK\Samples\OculusRoomTiny\OculusRoomTiny (DX11)\Bin\Windows\Win32\Debug\VS2015\OculusRoomTiny (DX11).exe'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\user32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\win32u.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32full.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcp_win.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\ucrtbase.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\dxgi.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\d3d11.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\D3DCompiler_47.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\sspicli.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptbase.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\bcryptprimitives.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\sechost.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptsp.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\imm32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\combase.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\wintrust.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\msasn1.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\crypt32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\rsaenh.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\bcrypt.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\imagehlp.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\gpapi.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRT32_1.dll'. Cannot find or open the PDB file. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\shell32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\cfgmgr32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\SHCore.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\windows.storage.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\shlwapi.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel.appcore.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\powrprof.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\profapi.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\opengl32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\winmm.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\glu32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\winmmbase.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\winmmbase.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Unloaded 'C:\Windows\SysWOW64\winmmbase.dll' 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\dbghelp.dll'. Symbols loaded. 09/02 18:21:47.226 {INFO} [Kernel:Default] [CAPI] LibOVR module is located at C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRT32_1.dll 09/02 18:21:47.232 {DEBUG} [Client] Connected to the server running version (prod = 1).1.23.0(build = 528114) feature version = 0. Client runs version (prod = 1).1.23.0(build = 0) feature version = 0 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\uxtheme.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\msctf.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\oleaut32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\dwmapi.dll'. Symbols loaded. 09/02 18:21:47.245 {DEBUG} [Kernel:Default] [HMDState] Using default profile default 09/02 18:21:47.246 {INFO} [Kernel:Default] IAD changed to 58.3mm 09/02 18:21:47.246 {DEBUG} [SharedMemory] Creating factory 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\TextInputFramework.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\CoreMessaging.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\CoreUIComponents.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntmarta.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\WinTypes.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\WinTypes.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Unloaded 'C:\Windows\SysWOW64\WinTypes.dll' 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\ResourcePolicyClient.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Unloaded 'C:\Windows\SysWOW64\ResourcePolicyClient.dll' 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\System32\DriverStore\FileRepository\nvddui.inf_amd64_e422766d00046e2b\nvwgf2um.dll'. Cannot find or open the PDB file. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\version.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\nvspcap.dll'. Cannot find or open the PDB file. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\setupapi.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\psapi.dll'. Symbols loaded. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\winhttp.dll'. Symbols loaded. The thread 0x174c has exited with code 0 (0x0). 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\nvapi.dll'. Cannot find or open the PDB file. Exception thrown at 0x74E65F5D in OculusRoomTiny (DX11).exe: 0xC0000005: Access violation reading location 0x00000000. 'OculusRoomTiny (DX11).exe' (Win32): Loaded 'C:\Windows\SysWOW64\devobj.dll'. Symbols loaded. 09/02 18:22:00.504 {INFO} [Kernel:Default] [HMDState] Detected the active window handle changed to 1031d2ll The thread 0x36a8 has exited with code 0 (0x0). The thread 0x3e60 has exited with code 0 (0x0). The thread 0x1e98 has exited with code 0 (0x0). The thread 0x10c4 has exited with code 0 (0x0). The thread 0x2488 has exited with code 0 (0x0). The thread 0x1ff0 has exited with code 0 (0x0). The thread 0x21c4 has exited with code 0 (0x0). The thread 0x2b84 has exited with code 0 (0x0). 'OculusRoomTiny (DX11).exe' (Win32): Unloaded 'C:\Windows\System32\DriverStore\FileRepository\nvddui.inf_amd64_e422766d00046e2b\nvwgf2um.dll' 09/02 18:22:12.801 {INFO} [Kernel:System] Graceful shutdown: OnThreadDestroy 09/02 18:22:12.801 {INFO} [Kernel:System] Graceful shutdown: OnSystemDestroy 09/02 18:22:12.801 {DEBUG} [SharedMemory] Destroying factory 09/02 18:22:12.801 {DEBUG} [Kernel:Default] [Client] Disconnected 09/02 18:22:12.801 {INFO} [Kernel:System] Graceful shutdown: Stopping logger The thread 0x39fc has exited with code 0 (0x0). The thread 0x3d9c has exited with code 0 (0x0). The thread 0x1568 has exited with code 0 (0x0). The thread 0x24f4 has exited with code 0 (0x0). The thread 0x18b4 has exited with code 0 (0x0). The thread 0x81c has exited with code 0 (0x0). The thread 0x32c8 has exited with code 0 (0x0). The thread 0x34dc has exited with code 0 (0x0). The program '[6992] OculusRoomTiny (DX11).exe' has exited with code 0 (0x0). I have tried to uninstall/reinstall the OculusRift application several times (I was thinking maybe there was a corrupted dll or something) but nothing has changed. I really don't know what I can do to solve this issue. Have one of you ever encountered such a problem ? Thank you, Kind regards, Johann NOVAK2.6KViews1like11CommentsVisualising medical image data
I'm interested in visualising medical image data with my Rift, but unsure of the best way to do this. Ideally, I would like to be able to rotate, translate and zoom with the game pad or touch controllers, or otherwise just watch a pre-recorded fly-through as a demo. The first thought I had was that some of the software I use (in particular Amira on Windows 10) has support for 3D visualisation, such as raw stereo (OpenGL) and split screen horizontal/vertical. Could any of these be easily hacked to be sent to the Rift? For example if the scene for each eye was rendered on a separate area of the screen, could this be captured and used by the Rift? I've had a quick look through the SDK, but couldn't find any quick solutions... Otherwise, are there any apps that will take 3D data (some sort of surface file perhaps?) and allow you to interact with it? Any suggestions very welcome!Solved1.1KViews0likes2CommentsDK2 not being recognised
I purchased a DK2 a while back, when they first became available. Due to other commitments I never got a chance to get started with it. Anyway, I'm now looking to start on a project. I can't seem to get either of the systems I've tried it on to recognise the DK2 though. Both systems pass the compatibility test okay. On both of them I get to the "Connect your rift headset" step in the wizard, and the Sensor USB is recognised okay, but Headset HDMI and Headset USB are both stuck spinning the searching circle. The headset is powered up and displaying the "continue setup on PC" message. On both systems the DK2 is plugged into an HDMI port on a GTX970, and USB 3 ports. Both systems are windows 10, 64 bit, fully patched (including the anniversary update). In device manage I have a "Rift DK2 Sensor" under "Oculus VR Devices". Under Other devices I have two unknown devices. It looks like a driver issue, but apart from the main oculus setup I can't see any individual driver downloads. Any suggestions?1.8KViews2likes6CommentsDK1 development targeting CV1
Hello guys, I am developing a project using my DK1, using the SDK 0.0.8.0 beta. I am not sure tough if this will work for CV1, I doesn`t own CV1 to test, so I need to know if the build will work smoothly when using CV1. Can someone tell me if it is ok this approach or maybe I should change de SDK even if it doesn`t work in DK1 but works fine in CV1?420Views0likes0CommentsGame built in Unity 4 for DK2, updated to Windows 10, HMD not detected
Dear all, any help you could provide me with with be much appreciated. Please bear with me, but I haven't found answers online and I'd like to try to walk you through our situation. My wife and I built a VR art installation using Unity 4 with DK2 in fall 2014 - spring 2015. At this time she was using Windows 8. After an epic journey we were able to get her file to run for her thesis exhibition and it looked great. After her graduation we didn't use the Rift for a long time. Took a bit of a break. In the meantime Microsoft rolled out Windows 10, auto-updating without our permission. Unity upgraded to version 5, and we decided not to update. Oculus Rift has shifted focus away from DK2 to the consumer version, and there's been multiple versions of the Runtime/SDK software and it is super freaking confusing. I wanted to show off our VR experience, but now a year later, nothing seems to work. The closest I have been able to get is with the following setup: I installed 0.8 runtime on the Windows 10 machine. The software recognizes the DK2 and I can play the demo scene from the config utility no problemo. I go to my wife's unity exe file (there are two, file1 and file1 direct to rift). When I open either of these files the visuals show up successfully on the monitor-- but not in the rift. In addition, the message "no HMD detected" appears on the screen. I need to know how to get the visuals to show up inside the rift itself, and for it to detect head movement. Is there anyone who has had a similar situation and has been able to find a fix? Thanks for your help. Tagged: DK2 windows 10 no hmd detected unity 4841Views0likes2Comments